mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v3 2/4] Documentation: reset-reason: document new BROWNOUT reason
Date: Mon, 17 Jun 2019 16:34:16 +0200	[thread overview]
Message-ID: <20190617143418.32207-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20190617143418.32207-1-a.fatoum@pengutronix.de>

Now that enum reset_src_type has been extended by BROWNOUT as a reason,
add it to the user documentation.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/user/reset-reason.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/user/reset-reason.rst b/Documentation/user/reset-reason.rst
index 26d37f86dd3e..e46f2ca684ab 100644
--- a/Documentation/user/reset-reason.rst
+++ b/Documentation/user/reset-reason.rst
@@ -41,6 +41,10 @@ The following values can help to detect the reason why the bootloader runs:
 * ``EXT`` (EXTernal): some SoCs have special device pins for external reset
   signals other than the ``RST`` one. Application specific how to handle this
   state.
+* ``BROWNOUT``: some SoCs detect undervoltage conditions and stay in reset
+  till the supply voltage crosses a predefined threshold voltage. This avoids
+  erratic behavior that may occur when running out-of-spec. Application specific
+  how to handle this state.
 
 It depends on your board/SoC and its features if the hardware is able to detect
 these reset reasons. Most of the time only ``POR`` and ``RST`` are supported
-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-06-17 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 14:34 [PATCH v3 0/4] ARM: stm32mp: implement watchdog/reset handling Ahmad Fatoum
2019-06-17 14:34 ` [PATCH v3 1/4] ARM: stm32mp1: rerun savedefconfig on stm32mp_defconfig Ahmad Fatoum
2019-06-17 15:08   ` Ahmad Fatoum
2019-06-17 14:34 ` Ahmad Fatoum [this message]
2019-06-17 14:34 ` [PATCH v3 3/4] watchdog: add stm32 watchdog and reset driver Ahmad Fatoum
2019-06-17 14:34 ` [PATCH v3 4/4] ARM: stm32mp: enable watchdog in defconfig Ahmad Fatoum
2019-06-19  9:02 ` [PATCH v3 0/4] ARM: stm32mp: implement watchdog/reset handling Sascha Hauer

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=20190617143418.32207-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