mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Johannes Zink <j.zink@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Johannes Zink <j.zink@pengutronix.de>,
	afa@pengutronix.de, jzi@pengutronix.de
Subject: [PATCH] Documentation: devicetree: list automatic boot argument fixups
Date: Fri, 17 Mar 2023 12:07:48 +0100	[thread overview]
Message-ID: <20230317110748.835678-1-j.zink@pengutronix.de> (raw)

Barebox automatically fixes up several entries to the root and
chosen-node of the devicetree passed to the booted system.

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
+------------------------------------------------
+
+Barebox automatically fixes up some arguments in the devicetree.
+
+In the devicetree root barebox fixes up
+
+ * serial-number (if available)
+ * machine compatible (if available)
+
+In the ``chosen``-node barebox fixes up
+
+ * barebox-version
+ * reset-source
+ * reset-source-instance (if available)
+ * reset-source-device (phandle, only if available)
+ * bootsource
+ * boot-hartid (only on RISCV)
+
+These values can be read from the booted linux system in ``/proc/device-tree/``.
-- 
2.30.2




             reply	other threads:[~2023-03-17 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 11:07 Johannes Zink [this message]
2023-03-17 11:15 ` Ahmad Fatoum

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=20230317110748.835678-1-j.zink@pengutronix.de \
    --to=j.zink@pengutronix.de \
    --cc=afa@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --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