[PATCH v3 2/6] doc: Add a binding for sysinfo

[Heinrich Schuchardt]

On 10/22/20 5:08 AM, Simon Glass wrote:
> Add a simple binding file for this, so that it is clear what this binding
> directory is for.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
>
> (no changes since v1)
>
>  doc/device-tree-bindings/sysinfo/sysinfo.txt | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 doc/device-tree-bindings/sysinfo/sysinfo.txt
>
> diff --git a/doc/device-tree-bindings/sysinfo/sysinfo.txt b/doc/device-tree-bindings/sysinfo/sysinfo.txt
> new file mode 100644
> index 00000000000..ed8830b8284
> --- /dev/null
> +++ b/doc/device-tree-bindings/sysinfo/sysinfo.txt
> @@ -0,0 +1,18 @@
> +Sysinfo
> +=======
> +
> +This provides capabilities to access information about a board/system, for
> +use by drivers.
> +
> +Required properties:
> +
> +  - compatible: any suitable string where the driver is in the UCLASS_SYSINFO
> +      class
> +
> +See also smbios.txt
> +
> +
> +Example
> +
> +sysinfo {
> +	compatible = "sandbox,sysinfo";
>

Most boards use don't use ACPI but device-trees for calling
the operating system.
We try to keep our device-trees in sync with Linux.
The device-tree available under $fdtcontroladdr should be
usable to boot the OS.
We should avoid anything that could lead now or in the future
to a conflict with the the OS usage of the device tree nodes.

Please, use in the example a compatibility string that is
unique to U-Boot.

How about: "uboot,sandbox-sysinfo"?

Best regards

Heinrich