From: Guenter Roeck <linux@roeck-us.net>
To: Meng Li <Meng.Li@windriver.com>
Cc: wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v2][PATCH] watchdog: core: stop watchdog when executing poweroff command
Date: Mon, 14 Aug 2023 06:52:01 -0700 [thread overview]
Message-ID: <ac5d44be-0f87-4f13-ba07-fe274ed773fd@roeck-us.net> (raw)
In-Reply-To: <20230814090616.1853263-1-Meng.Li@windriver.com>
On Mon, Aug 14, 2023 at 05:06:16PM +0800, Meng Li wrote:
> From: Meng Li <meng.li@windriver.com>
>
> On some platforms, for example, Intel SoC FPGA platform, the watchdog
> is started in u-boot, and so kernel will create a timer and work to
> keep watchdog alive. But when user executes commands "poweroff" or
> "shutdown -h", the system is reset when watchdog triggers timeout even
> if WDOG_STOP_ON_REBOOT is set in watchdog driver. The root cause is
> that the watchdog is not stopped properly because the SYS_POWER_OFF case
> is not supported in notify callback function. So, add this case to stop
> watchdog when executing poweroff command.
>
> Signed-off-by: Meng Li <Meng.Li@windriver.com>
Makes sense.
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Guenter
> ---
>
> v2:
> - fix typos in commit log
>
> ---
> drivers/watchdog/watchdog_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/watchdog_core.c b/drivers/watchdog/watchdog_core.c
> index d4c5a736fdcb..5b55ccae06d4 100644
> --- a/drivers/watchdog/watchdog_core.c
> +++ b/drivers/watchdog/watchdog_core.c
> @@ -161,7 +161,7 @@ static int watchdog_reboot_notifier(struct notifier_block *nb,
> struct watchdog_device *wdd;
>
> wdd = container_of(nb, struct watchdog_device, reboot_nb);
> - if (code == SYS_DOWN || code == SYS_HALT) {
> + if (code == SYS_DOWN || code == SYS_HALT || code == SYS_POWER_OFF) {
> if (watchdog_hw_running(wdd)) {
> int ret;
>
> --
> 2.17.1
>
prev parent reply other threads:[~2023-08-14 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:06 Meng Li
2023-08-14 13:52 ` Guenter Roeck [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=ac5d44be-0f87-4f13-ba07-fe274ed773fd@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Meng.Li@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--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
all inboxes | Powered by JetHome®