From: Guenter Roeck <linux@roeck-us.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: What to set in struct watchdog_device::bootstatus?
Date: Fri, 8 Feb 2019 06:05:43 -0800 [thread overview]
Message-ID: <f9ec94d7-8365-e733-81ff-34c501cce89a@roeck-us.net> (raw)
In-Reply-To: <20190208105230.g33nxiu4r6uqech3@pengutronix.de>
On 2/8/19 2:52 AM, Uwe Kleine-König wrote:
> Hello,
>
> it's unclear to me, which bits I am supposed to set in the bootstatus
> member of struct watchdog_device at probe time.
>
> The i.MX watchdog differentiates the following reset causes:
>
> - Power On
None.
> - external reset
None.
> - watchdog timeout
WDIOF_CARDRESET
> - software reset using a bit in the watchdog register set
>
> (Not all i.MX variants implement all bits according to the respective
> reference manuals.)
>
> Should "Power On" result in setting WDIOF_POWERUNDER?
>
No.
> Should "software reset [...]" result in WDIOF_CARDRESET?
>
That would be the best fit if you want a bit to be set, but it would be
misleading since it would suggest that the watchdog fired.
> Should "external reset" result in WDIOF_EXTERN1? (I guess that no)
>
No.
Overall, the bits are only to be set if the reset was triggered by
the watchdog controller.
Guenter
next prev parent reply other threads:[~2019-02-08 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 10:52 What to set in struct watchdog_device::bootstatus? Uwe Kleine-König
2019-02-08 14:05 ` Guenter Roeck [this message]
2019-02-20 20:14 ` Uwe Kleine-König
2019-05-09 19:25 ` Uwe Kleine-König
2019-05-10 3:53 ` Guenter Roeck
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=f9ec94d7-8365-e733-81ff-34c501cce89a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.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).