From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/5] Documentation: reboot-mode: fix headings
Date: Thu, 1 Apr 2021 08:46:14 +0200 [thread overview]
Message-ID: <20210401064616.29913-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20210401064616.29913-1-a.fatoum@pengutronix.de>
From: Ahmad Fatoum <ahmad@a3f.at>
What was supposed to be subheadings of the Disambiguation headings
weren't by mistake. Bump up the other headings to restore the balance.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/user/reboot-mode.rst | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Documentation/user/reboot-mode.rst b/Documentation/user/reboot-mode.rst
index 9321d928f41a..8717e3934206 100644
--- a/Documentation/user/reboot-mode.rst
+++ b/Documentation/user/reboot-mode.rst
@@ -1,7 +1,8 @@
.. _reboot_mode:
+###########
Reboot Mode
------------
+###########
To simplify debugging, many BootROMs sample registers that survive
a warm reset to customize the boot. These registers can e.g. indicate
@@ -23,7 +24,7 @@ modes in the device tree. If a match is found the associated magic
is written to the location referenced in the device tree node.
User API
-~~~~~~~~
+========
Devices registered with the reboot mode API gain two parameters:
@@ -46,7 +47,7 @@ priority has its parameters aliased as ``$global.system.reboot_mode.prev``
and ``$global.system.reboot_mode.next``.
Reset
-~~~~~
+=====
Reboot modes can be stored on a syscon wrapping general purpose registers
that survives warm resets. If the system instead did reset via an external
@@ -57,7 +58,7 @@ reset provider. In barebox, multiple reset providers may co-exist. They
``reset`` command allows listing and choosing a specific reboot mode.
Disambiguation
-~~~~~~~~~~~~~~
+==============
Some uses of reboot modes partially overlap with other barebox
functionality. They all ultimately serve different purposes, however.
--
2.29.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-04-01 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 6:46 [PATCH 1/5] fixup! input: add virtio input driver Ahmad Fatoum
2021-04-01 6:46 ` [PATCH 2/5] Documentation: virtio: Fix virtio reference Ahmad Fatoum
2021-04-01 6:46 ` Ahmad Fatoum [this message]
2021-04-01 6:46 ` [PATCH 4/5] Documentation: reference reboot-mode Documentation Ahmad Fatoum
2021-04-01 6:46 ` [PATCH 5/5] Documentation: add barebox porter's guide 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=20210401064616.29913-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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