Hi Rob, On Mon, 4 Oct 2021 at 13:30, Rob Herring <robh@xxxxxxxxxx> wrote: > > On Sun, Oct 03, 2021 at 12:51:53PM -0600, Simon Glass wrote: > > U-Boot makes use of the devicetree for its driver model. Devices are bound > > based on the hardware description in the devicetree. > > > > Since U-Boot is not an operating system, it has no command line or user > > space to provide configuration and policy information. This must be made > > available in some other way. > > > > Therefore U-Boot uses devicetree for configuration and run-time control > > and has done for approximately 9 years. This works extremely well in the > > project and is very flexible. However the bindings have never been > > incorporated in the devicetree bindings in the Linux tree. This could be > > a good time to start this work as we try to create standard bindings for > > communicating between firmware components. > > > > Add an initial binding for this node, covering just the config node, which > > is the main requirement. It is similar in concept to the chosen node, but > > used for passing information between firmware components, instead of from > > firmware to operating system. > > > > Signed-off-by: Simon Glass <sjg@xxxxxxxxxxxx> > > --- > > Please be kind in your review. Some words about why this is needed are > > included in the description in config.yaml file. > > > > The last attempt to add just one property needed by U-Boot went into the > > weeds 6 years ago, with what I see as confusion about the role of the > > chosen node in devicetree[1]. > > > > I am trying again in the hope of reaching resolution rather than just > > going around in circles with the 'devicetree is a hardware description' > > argument :-) > > > > Quoting from the introduction to latest devicetree spec[2]: > > > > >>> > > To initialize and boot a computer system, various software components > > interact. Firmware might perform low-level initialization of the system > > hardware before passing control to software such as an operating system, > > bootloader, or hypervisor. Bootloaders and hypervisors can, in turn, > > load and transfer control to operating systems. Standard, consistent > > interfaces and conventions facilitate the interactions between these > > software components. In this document the term boot program is used to > > generically refer to a software component that initializes the system > > state and executes another software component referred to as a client > > program. > > <<< > > > > This clearly envisages multiple software components in the firmware > > domain and in fact that is the case today. They need some way to > > communicate configuration data such as memory setup, runtime-feature > > selection and developer conveniences. Devicetree seems ideal, at least for > > components where the performance / memory requirements of devicetree are > > affordable. > > > > I hope that the Linux community (which owns the devicetree bindings) finds > > this initiative valuable and acceptable. > > Owns? I'm having a sale and can make you a good offer. Buy 1 binding, > get 2000 free. :) Yes, it's the price of that first binding that surely puts everyone off. (sorry for sitting on this for a week, my spam filter doesn't like some mailing lists and I'm working on it) > > > > > [1] https://lists.denx.de/pipermail/u-boot/2015-July/218585.html > > [2] https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3 > > > > .../devicetree/bindings/u-boot/config.yaml | 137 ++++++++++++++++++ > > 1 file changed, 137 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/u-boot/config.yaml > > Might as well put this into dt-schema rather than the kernel. But might > get more review here first. OK, so does that mean a PR to https://github.com/robherring/dt-schema or is there a mailing list for it? I think I am missing some understanding here. > > > diff --git a/Documentation/devicetree/bindings/u-boot/config.yaml b/Documentation/devicetree/bindings/u-boot/config.yaml > > new file mode 100644 > > index 00000000000000..336577a17fdf5a > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/u-boot/config.yaml > > @@ -0,0 +1,137 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/u-boot/config.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: U-Boot configuration node > > + > > +maintainers: > > + - Simon Glass <sjg@xxxxxxxxxxxx> > > + > > +description: | > > + The config node does not represent a real device, but serves as a place > > + for passing data between firmware elements, like memory maps. Data in the > > + config node does not represent the hardware. It is ignored by operating > > + systems. > > + > > + Purpose of config node > > + ---------------------- > > + > > + A common problem with firmware is that many builds are needed to deal with the > > + slight variations between different, related models. For example, one model > > + may have a TPM and another may not. Devicetree provides an excellent solution > > + to this problem, in that the devicetree to actually use on a platform can be > > + injected in the factory based on which model is being manufactured at the time. > > + > > + A related problem causing build proliferation is dealing with the differences > > + between development firmware, developer-friendly firmware (e.g. with all > > + security features present but with the ability to access the command line), > > + test firmware (which runs tests used in the factory), final production > > + firmware (before signing), signed firmware (where the signatures have been > > + inserted) and the like. Ideally all or most of these should use the same > > + U-Boot build, with just some options to determine the features available. For > > + example, being able to control whether the UART console or JTAG are available, > > + on any image, is a great debugging aid. > > + > > + When the firmware consists of multiple parts (various U-Boot phases, TF-A, > > + OP-TEE), it is helpful that all operate the same way at runtime, regardless of > > + how they were built. This can be achieved by passing the runtime configuration > > + (e.g. 'enable UART console', 'here are your public keys') along the chain > > + through each firmware stage. It is frustrating to have to replicate a bug on > > + production firmware which does happen on developer firmware, because they are > > + completely different builds. > > + > > + The config node provides useful functionality for this. It allows the different > > + controls to be 'factored out' of the U-Boot binary, so they can be controlled > > + separately from the initial source-code build. The node can be easily updated > > + by a build or factory tool and can control various features in U-Boot. It is > > + similar in concept to a Kconfig option, except that it can be changed after > > + U-Boot is built. > > + > > + The config node is similar in concept to /chosen (see chosen.txt) except that > > chosen.yaml now (in dt-schema). OK > > > + it is for passing information *into* and *between) firmware components, > > + instead of from firmware to the Operating System. Also, while operating > > + systems typically have a (sometimes extremely long) command line, U-Boot does > > + not support this, except with sandbox. The devicetree provides a more > > + structured approach in any case. > > What about having a /chosen/u-boot/ node instead? What is your rationale for doing that? Should we perhaps have a vendor/ directory for vendor-specific tags? Also, thinking ahead, I am interested in how we can add bindings for firmware-to-firmware communications. There are some settings that could be defined across projects (such as memory layout, security level/settings) and these should ideally be harmless to pass to the kernel (i.e. ignored by the kernel). It is possible that some of these could be used by the kernel but then we can always recreate them using kernel bindings as needed (and cross that bridge when we come to it). So this would be a set of bindings used by firmware components in general. We would not want to use "u-boot,xxx" in that case. > > > + > > +properties: > > + > > + compatible: > > + enum: > > + - "u-boot,config" > > nit: don't need quotes. OK > > > + > > + bootcmd: > > + $ref: /schemas/types.yaml#/definitions/string > > + description: | > > + Allows overwriting of the boot command used by U-Boot on startup. If > > + present, U-Boot uses this command instead. Note that this feature can > > + work even if loading the environment is disabled, e.g. for security > > + reasons. See also bootsecure. > > + > > + bootdelay: > > bootdelay-sec > > > + $ref: /schemas/types.yaml#/definitions/int32 > > And then you don't need a type. > > (Though we've defined '-sec' as unsigned, I think that's safe to change. > In any case, signedness is kind of broken in the dts->dtc->yaml flow > ATM.) OK, I'll update it. We can always deal with this later if validation becomes stricter. > > > + description: | > > + Allows selecting of the U-Boot bootdelay, to control whether U-Boot > > + waits on boot or for how long. This allows this option to be configured > > + by the build system or by a previous-stage binary. For example, if the > > + images is being packed for testing or a user holds down a button, it may > > + allow a delay, but disable it for production. > > + > > + If this property is not present, a default value is used instead. > > + > > + Values: > > + > > + -1: no bootdelay and the user cannot interrupt boot > > + 0: no bootdelay but use user can still interrupt boot by holding down a > > + key, if enabled > > + >= 1: delay for this many seconds > > + > > + > > + bootsecure: > > + $ref: /schemas/types.yaml#/definitions/uint32 > > + description: | > > + Controls the execution of the boot command in U-Boot, e.g. selecting > > + between using a special function to run commands, or the normal CLI. This > > + can be used in production images, to restrict the amount of parsing done > > + or the options available, to cut back on the available surface for > > + security attacks. > > + > > + Values: > > + > > + 0: normal boot using CLI (default if not present) > > + 1: use secure boot mechanism instead to parse and run commands > > + other values are reserved for future use > > + 2: use simplified command line (e.g. avoid hush) > > + 3... reserved > > Add constraints: > > default: 0 > maximum: 2 OK > > > + > > + silent-console: > > + $ref: /schemas/types.yaml#/definitions/uint32 > > + description: | > > + This allows the console to be silenced by default on boot. This can allow > > + easy disabling of console output on a production build, for example. When > > + suppressed, the console is still active. This feature only suppresses the > > + console output itself, on all output devices. > > + > > + Values: > > + > > + 0: console output appears as normal (default) > > + 1: console output is suppressed but console recording still operates (if > > + enabled) > > + 2: console output is suppressed and not recorded > > default: 0 > maximum: 2 OK > > > + > > +required: > > + - compatible > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + u-boot,config { > > + compatible = "u-boot,config"; > > + bootcmd = "vboot go auto"; > > + bootdelay = <(-1)>; > > + bootsecure = <1>; > > + silent-console = <1>; > > + }; > > -- > > 2.33.0.800.g4c38ced690-goog > > > > Regards, Simon
