From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>, barebox@lists.infradead.org
Cc: afa@pengutronix.de, jzi@pengutronix.de
Subject: Re: [PATCH] Documentation: devicetree: list automatic boot argument fixups
Date: Fri, 17 Mar 2023 12:15:26 +0100 [thread overview]
Message-ID: <d2afc69c-a775-4538-0416-046d448ad31c@pengutronix.de> (raw)
In-Reply-To: <20230317110748.835678-1-j.zink@pengutronix.de>
Hello Johannes,
Thanks for documenting this. Some minor suggestions below.
On 17.03.23 12:07, Johannes Zink wrote:
> Barebox automatically fixes up several entries to the root and
s/entries/properties/
> chosen-node of the devicetree passed to the booted system.
chosen node, device tree
>
> These entries contain information about the hardware, reset source
> and the barebox version string.
>
> Add documentation on how to query these information from the booted
> linux system.
>
> Signed-off-by: Johannes Zink <j.zink@pengutronix.de>
> ---
> Documentation/devicetree/index.rst | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/Documentation/devicetree/index.rst b/Documentation/devicetree/index.rst
> index 36fa69058d1d..92a91dc35a11 100644
> --- a/Documentation/devicetree/index.rst
> +++ b/Documentation/devicetree/index.rst
> @@ -151,3 +151,24 @@ Contents:
> bindings/regulator/*
> bindings/rtc/*
> bindings/watchdog/*
> +
> +automatic boot argument fixups to the devicetree
Title case or at least a capital letter at the beginning?
> +------------------------------------------------
> +
> +Barebox automatically fixes up some arguments in the devicetree.
s/Barebox/barebox/, s/devicetree/device tree/, s/arguments/properties/
or information.
> +
> +In the devicetree root barebox fixes up
, barebox
> +
> + * serial-number (if available)
> + * machine compatible (if available)
s/available/overridden/
There's nearly always a machine compatible.
> +
> +In the ``chosen``-node barebox fixes up
, barebox
> +
> + * barebox-version
> + * reset-source
> + * reset-source-instance (if available)
> + * reset-source-device (phandle, only if available)
node path, not the numeric phandle, compare
property = &path -> "/path/to/something"
vs.
property = <&path> -> <0x23>, with &path { phandle = <0x23>; }
> + * bootsource
> + * boot-hartid (only on RISCV)
RISC-V
> +
> +These values can be read from the booted linux system in ``/proc/device-tree/`
"or /sys/firmware/devicetree/base".
Thanks,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-03-17 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 11:07 Johannes Zink
2023-03-17 11:15 ` Ahmad Fatoum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2afc69c-a775-4538-0416-046d448ad31c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=afa@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.zink@pengutronix.de \
--cc=jzi@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox