* [PATCH] doc: api: bootcount: correct bootcount description
@ 2026-04-06 9:57 michael.opdenacker
0 siblings, 0 replies; only message in thread
From: michael.opdenacker @ 2026-04-06 9:57 UTC (permalink / raw)
To: trini; +Cc: michael.opdenacker, u-boot
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
The bootcount variable is only incremented
when the upgrade_variable is non-zero,
as implemented in drivers/bootcount/bootcount_env.c
Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
---
doc/api/bootcount.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/api/bootcount.rst b/doc/api/bootcount.rst
index 968c679c3c6..f3c10bbe724 100644
--- a/doc/api/bootcount.rst
+++ b/doc/api/bootcount.rst
@@ -8,7 +8,7 @@ This is enabled by CONFIG_BOOTCOUNT_LIMIT.
This allows to detect multiple failed attempts to boot Linux.
After a power-on reset, the ``bootcount`` variable will be initialized to 1, and
-each reboot will increment the value by 1.
+when ``upgrade_available`` is non-zero, each reboot will increment the value by 1.
If, after a reboot, the new value of ``bootcount`` exceeds the value of
``bootlimit``, then instead of the standard boot action (executing the contents
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-04-06 13:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-06 9:57 [PATCH] doc: api: bootcount: correct bootcount description michael.opdenacker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox