From: Damien Riegel <damien.riegel@savoirfairelinux.com>
To: Harald Geyer <harald@ccbib.org>,
wim@iguana.be, linux-watchdog@vger.kernel.org,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
linux@roeck-us.net
Subject: Re: In-reply-to: <1448056496-2335-1-git-send-email-damien.riegel@savoirfairelinux.com>
Date: Mon, 23 Nov 2015 18:31:37 -0500 [thread overview]
Message-ID: <20151123233136.GA18839@localhost> (raw)
In-Reply-To: <E1a0vjV-0000O4-QX@stardust.g4.wien.funkfeuer.at>
On Mon, Nov 23, 2015 at 07:20:57PM +0100, Harald Geyer wrote:
> Damien Riegel writes:
> > > + if (code == SYS_DOWN || code == SYS_HALT) {
> > >
> > > I think you want this to be (code == SYS_POWER_OFF || code == SYS_HALT)
> > > AFAIK SYS_DOWN is the code for a reboot, where the system should come
> > > back up immediatly, so probably we shouldn't disable the watchdog in
> > > this case, for the system might crash during going down.
> >
> > Well, most of the drivers (all of them but gpio) that I changed stopped
> > on SYS_HALT and SYS_DOWN, so they explicitely wanted to stop the
> > watchdog on reboot. I just factorized that in watchdog core.
>
> If they wanted to do so, or the code just got copied around, is
> unclear. SYS_DOWN isn't the most helpful name after all, but ...
>
> > Maybe they should not stop on reboot in the first place, but this serie
> > does not introduce a new behaviour.
>
> okay. I can always send a follow up patch, if I care enough.
>
I don't understand why you assume this is not the desired behaviour and
that the code was just copied around.
> > > More importantly however we should stop the watchdog on SYS_POWER_OFF
> > > I think.
> > >
> > My understanding here is that if the system is powered off, the watchdog
> > will be powered off too, so there is no need to stop it.
>
> This is true for many platforms, but I'm pretty sure that not all
> platforms have a real power off. So unless you can think of a reason not
> to stop the watchdog on power off, I think the core should do it.
> Actually if this can't be the default, we probably need to extend
> your code so that drivers can select the behaviour they want.
> (Of course we would hate to do that, as power management and watchdogs
> are pretty orthogonal subsystems and having one depend on the behaviour
> of the other is very unfortunate.)
We have to assume that power-off means that the system will be powered
off (...). If a platform has no real power-off, then it should be
halted, and in that case the core would stop the watchdog to prevent a
spurious reboot.
But maybe you're right and we should not make such distinction between
power-off and halt, but I don't really want to make changes in drivers I
don't know the context in which they are used.
Damien.
next prev parent reply other threads:[~2015-11-23 23:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 21:54 [PATCH v2 0/6] watchdog: factorize reboot notifier registration Damien Riegel
2015-11-20 21:54 ` [PATCH v2 1/6] watchdog: core: add reboot notifier support Damien Riegel
2015-11-21 1:10 ` Guenter Roeck
2015-11-23 15:02 ` In-reply-to: <1448056496-2335-1-git-send-email-damien.riegel@savoirfairelinux.com> Harald Geyer
2015-11-23 15:37 ` Damien Riegel
2015-11-23 18:20 ` Harald Geyer
2015-11-23 23:31 ` Damien Riegel [this message]
2015-11-25 17:04 ` Harald Geyer
2015-11-25 18:37 ` Guenter Roeck
2015-11-25 21:56 ` Harald Geyer
2015-11-25 22:10 ` Guenter Roeck
2015-11-23 15:57 ` Guenter Roeck
2015-11-20 21:54 ` [PATCH v2 2/6] watchdog: bcm47xx_wdt: use core reboot notifier Damien Riegel
2015-11-20 21:54 ` [PATCH v2 3/6] watchdog: cadence_wdt: " Damien Riegel
2015-11-20 21:54 ` [PATCH v2 4/6] watchdog: gpio_wdt: " Damien Riegel
2015-11-21 1:11 ` Guenter Roeck
2015-11-20 21:54 ` [PATCH v2 5/6] watchdog: softdog: " Damien Riegel
2015-11-20 21:54 ` [PATCH v2 6/6] watchdog: w83627hf_wdt: " Damien Riegel
2015-11-21 1:10 ` Guenter Roeck
2015-12-27 16:50 ` [PATCH v2 0/6] watchdog: factorize reboot notifier registration Wim Van Sebroeck
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=20151123233136.GA18839@localhost \
--to=damien.riegel@savoirfairelinux.com \
--cc=harald@ccbib.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=wim@iguana.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.