From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Guenter Roeck" <linux@roeck-us.net>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
kernel@pengutronix.de, Wim Van Sebroeck <wim@linux-watchdog.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [RFC] Using a watchdog as system reset
Date: Wed, 7 Oct 2020 09:32:11 +0200 [thread overview]
Message-ID: <bf467000-2c5c-6fa5-ff31-f27179dc6763@pengutronix.de> (raw)
In-Reply-To: <04e33d49-4210-9dcd-040c-35059e0619ba@pengutronix.de>
Hello,
On 10/7/20 9:25 AM, Ahmad Fatoum wrote:
>>> into the watchdog core.
>>
>> OK, will try to come up with a patch.
>
> Instead of having a `provide-system-reset' property, how about providing
> it unconditionally, but with a very low priority?
>
> This can be coupled with Guenther's suggestion of having a dynamic
> way to set the priority, e.g. a `watchdog-priority' property in the device
> tree that's common to all watchdogs? That's the way barebox is handling
> multiple watchdogs (default value in driver overridable in DT and at runtime).
>
> What's the DT folks opinion on that?
Correction: s/watchdog-priority/reset-priority/
>
> Cheers,
> Ahmad
>
>>
>> Best regards
>> Uwe
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2020-10-07 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 10:29 [RFC] Using a watchdog as system reset Uwe Kleine-König
2020-10-06 11:56 ` Guenter Roeck
2020-10-06 14:29 ` Guenter Roeck
2020-10-06 18:41 ` Uwe Kleine-König
2020-10-06 21:04 ` Guenter Roeck
2020-10-07 7:12 ` Uwe Kleine-König
2020-10-07 7:25 ` Ahmad Fatoum
2020-10-07 7:32 ` Ahmad Fatoum [this message]
2020-10-07 10:18 ` dt-binding to define default watchdog and machine reset (Was: Re: [RFC] Using a watchdog as system reset) Uwe Kleine-König
2020-10-07 11:04 ` Guenter Roeck
2020-10-07 11:35 ` 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=bf467000-2c5c-6fa5-ff31-f27179dc6763@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).