From: Lars Schmidt <l.schmidt@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Lars Schmidt <l.schmidt@pengutronix.de>
Subject: [PATCH 3/4] Documentation: bootchooser: add information about slots_locked
Date: Fri, 13 Jun 2025 16:08:04 +0200 [thread overview]
Message-ID: <20250613140805.1229525-4-l.schmidt@pengutronix.de> (raw)
In-Reply-To: <20250613140805.1229525-1-l.schmidt@pengutronix.de>
The new slots_locked variable does have influence on
remaining_attempt counter.
Signed-off-by: Lars Schmidt <l.schmidt@pengutronix.de>
---
Documentation/user/bootchooser.rst | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index 351e1d14e1..306443270a 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -77,6 +77,16 @@ no remaining attempts left.
To prevent ending up in an unbootable system after a number of failed boot
attempts, there is also a built-in mechanism to reset the counters to their defaults,
controlled by the ``global.bootchooser.reset_attempts`` variable.
+Alternatively, counting down the remaining attempts can be disabled by
+locking the bootchooser slots.
+This is done by defining a (32-bit) ``slots_locked`` variable in the
+bootstate and setting its value to ``1`` (usually from userspace).
+
+The variable affects all slots, is optional and its absence is
+interpreted as ``0``, meaning that attempts are decremented normally.
+
+The ``slots_locked`` value does not influence the decision on which slot
+to boot if any, only whether to decrement the attempts when booting.
If ``global.bootchooser.retry`` is enabled (set to ``1``), the bootchooser
algorithm will iterate through all valid boot targets (and decrease their
@@ -107,6 +117,19 @@ on the :ref:`reset reason <reset_reason>` (i.e. != WDG) using the
This will reset the ``remaining_attempts`` counter of the *last chosen* slot to
its default value (``reset_attempts``).
+Another option is to use ``slots_locked``.
+Normally this should be controlled from Linux userspace using the *barebox-state* tool, i.e.::
+
+ barebox-state -s bootstate.slots_locked=1
+
+It can also be locked via the :ref:`bootchooser command <command_bootchooser>`::
+
+ bootchooser -l
+
+or unlocked::
+
+ bootchooser -L
+
.. _dt-utils: https://git.pengutronix.de/cgit/tools/dt-utils
--
2.39.5
next prev parent reply other threads:[~2025-06-13 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 14:08 [PATCH 0/4] Add boot slot locking to bootchooser Lars Schmidt
2025-06-13 14:08 ` [PATCH 1/4] bootchooser: implement locking of boot slots Lars Schmidt
2025-06-16 10:44 ` Ahmad Fatoum
2025-06-13 14:08 ` [PATCH 2/4] bootchooser: extend cmd tool by option to set slot locking Lars Schmidt
2025-06-16 10:49 ` Ahmad Fatoum
2025-06-13 14:08 ` Lars Schmidt [this message]
2025-06-16 10:50 ` [PATCH 3/4] Documentation: bootchooser: add information about slots_locked Ahmad Fatoum
2025-06-13 14:08 ` [PATCH 4/4] Documentation: migration-2025.07.0: " Lars Schmidt
2025-06-16 10:51 ` 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=20250613140805.1229525-4-l.schmidt@pengutronix.de \
--to=l.schmidt@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