u-boot.git/doc/develop/devicetree, branch v2024.07-rc2

doc: devicetree: Lets avoid short reference link names

2024-03-21T05:48:19+00:00

Short reference link names like "dtspec", "dtrepo", "dttweaks" etc.
interrupt the flow of the document text. Lets avoid them and instead
expand in place for better readability.

Suggested-by: Paul Barker 
Signed-off-by: Sumit Garg 
Reviewed-by: Paul Barker

doc: devicetree: Updates for devicetree-rebasing subtree

2024-03-01T03:24:05+00:00

Encourage SoC/board maintainers to migrate to using devicetree-rebasing
subtree and maintain a regular sync with Linux kernel devicetree files
and bindings.

Along with that add documentation regarding how to run DT bindings
schema checks.

Signed-off-by: Sumit Garg

doc: devicetree: Align documentation to use Kconfig options

2024-03-01T03:24:05+00:00

Since U-Boot switched away from manual CONFIG_* defines to Kconfig
options, align devicetree documentation accordingly.

Signed-off-by: Sumit Garg

fdt: Allow the devicetree to come from a bloblist

2024-01-07T20:45:07+00:00

Standard passage provides for a bloblist to be passed from one firmware
phase to the next. That can be used to pass the devicetree along as well.
Add an option to support this.

Tests for this will be added as part of the Universal Payload work.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini 
Reviewed-by: Ilias Apalodimas

doc: devicetree: fix u-boot.bin filename typo

2023-05-13T09:09:50+00:00

Signed-off-by: Baruch Siach 
Reviewed-by: Simon Glass 
Signed-off-by: Heinrich Schuchardt

doc: devicetree: dt_qemu.rst: Fix the typo and space

2023-02-19T20:15:15+00:00

Fix typo and whitespace in the document.

Signed-off-by: Yu Chien Peter Lin 
Reviewed-by: Heinrich Schuchardt

global: Migrate CONFIG_EXTRA_ENV_SETTINGS to CFG

2022-12-23T15:09:42+00:00

Perform a simple rename of CONFIG_EXTRA_ENV_SETTINGS to CFG_EXTRA_ENV_SETTINGS

Signed-off-by: Tom Rini

introduce CONFIG_DEVICE_TREE_INCLUDES

2022-01-25T19:35:57+00:00

The build system already automatically looks for and includes an
in-tree *-u-boot.dtsi when building the control .dtb. However, there
are some things that are awkward to maintain in such an in-tree file,
most notably the metadata associated to public keys used for verified
boot.

The only "official" API to get that metadata into the .dtb is via
mkimage, as a side effect of building an actual signed image. But
there are multiple problems with that. First of all, the final U-Boot
(be it U-Boot proper or an SPL) image is built based on a binary
image, the .dtb, and possibly some other binary artifacts. So
modifying the .dtb after the build requires the meta-buildsystem
(Yocto, buildroot, whatnot) to know about and repeat some of the steps
that are already known to and handled by U-Boot's build system,
resulting in needless duplication of code. It's also somewhat annoying
and inconsistent to have a .dtb file in the build folder which is not
generated by the command listed in the corresponding .cmd file (that
of course applies to any generated file).

So the contents of the /signature node really needs to be baked into
the .dtb file when it is first created, which means providing the
relevant data in the form of a .dtsi file. One could in theory put
that data into the *-u-boot.dtsi file, but it's more convenient to be
able to provide it externally: For example, when developing for a
customer, it's common to use a set of dummy keys for development,
while the consultants do not (and should not) have access to the
actual keys used in production. For such a setup, it's easier if the
keys used are chosen via the meta-buildsystem and the path(s) patched
in during the configure step. And of course, nothing prevents anybody
from having DEVICE_TREE_INCLUDES point at files maintained in git, or
for that matter from including the public key metadata in the
*-u-boot.dtsi directly and ignore this feature.

There are other uses for this, e.g. in combination with ENV_IMPORT_FDT
it can be used for providing the contents of the /config/environment
node, so I don't want to tie this exclusively to use for verified
boot.

Reviewed-by: Simon Glass 
Signed-off-by: Rasmus Villemoes 
Fix doc formatting error (make htmldocs)
Signed-off-by: Simon Glass

arm: riscv: qemu: Explain how to extract the generated dt

2021-12-23T15:24:39+00:00

QEMU currently generates a devicetree for use with U-Boot. Explain how to
obtain it.

Also explain how to merge it to produce a devicetree with the U-Boot
features included.

Signed-off-by: Simon Glass

sandbox: Remove OF_HOSTFILE

2021-10-27T20:38:26+00:00

OF_HOSTFILE is used on sandbox configs only.  Although it's pretty
unique and not causing any confusions,  we are better of having simpler
config options for the DTB.

So let's replace that with the existing OF_BOARD.  U-Boot would then
have only three config options for the DTB origin.
- OF_SEPARATE, build separately from U-Boot
- OF_BOARD, board specific way of providing the DTB
- OF_EMBED embedded in the u-boot binary(should not be used in production

Signed-off-by: Ilias Apalodimas 
Reviewed-by: Simon Glass