From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v3 0/4] ARM: stm32mp: implement watchdog/reset handling
Date: Wed, 19 Jun 2019 11:02:27 +0200 [thread overview]
Message-ID: <20190619090227.7tuka7edohcaezge@pengutronix.de> (raw)
In-Reply-To: <20190617143418.32207-1-a.fatoum@pengutronix.de>
On Mon, Jun 17, 2019 at 04:34:14PM +0200, Ahmad Fatoum wrote:
> Originally, I thought about having poller enabled by default if the
> watchdog was active at barebox probe time, but I can't find a way
> to check if the IWDG is active or not, thus the driver probe doesn't
> touch the watchdog hardware anymore.
>
> Changes since v2:
> * Dropped already applied patches from v2
> * reran savedefconfig as prep and added the commit
> * documented BROWNOUT reason in Documentation/
> * removed enabling watchdog by default
> * renamed the file to stm32_wdt.c to stm32_iwdg.c, because there is
> a distinct stm32_wwdg Watchdog as well
> * dropped &iwdg2 { status = "okay"; } because it's now part of the
> upstream device tree
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-06-19 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 14:34 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 ` [PATCH v3 2/4] Documentation: reset-reason: document new BROWNOUT reason Ahmad Fatoum
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 ` Sascha Hauer [this message]
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=20190619090227.7tuka7edohcaezge@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=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