public inbox for linux-watchdog@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Guenter Roeck <linux@roeck-us.net>,
	Damien Riegel <damien.riegel@savoirfairelinux.com>,
	<linux-watchdog@vger.kernel.org>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	<kernel@savoirfairelinux.com>
Subject: Re: [PATCH 5/7] watchdog: gpio_wdt: use core reboot notifier
Date: Fri, 20 Nov 2015 08:15:33 +0100	[thread overview]
Message-ID: <564EC895.20902@topic.nl> (raw)
In-Reply-To: <564E930C.3000501@roeck-us.net>

On 20-11-15 04:27, Guenter Roeck wrote:
> On 11/18/2015 01:02 PM, Damien Riegel wrote:
>> Get rid of the custom reboot notifier block registration and use the one
>> provided by the watchdog core.
>>
>> Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
>> Reviewed-by: Vivien Didelot <vivien.didelot@savoirlinux.com>
>> ---
>>   drivers/watchdog/gpio_wdt.c | 35 ++---------------------------------
>>   1 file changed, 2 insertions(+), 33 deletions(-)
>>
>> diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpio_wdt.c
>> index 1a3c6e8..035c238 100644
>> --- a/drivers/watchdog/gpio_wdt.c
>> +++ b/drivers/watchdog/gpio_wdt.c
>> @@ -12,10 +12,8 @@
>>   #include <linux/err.h>
>>   #include <linux/delay.h>
>>   #include <linux/module.h>
>> -#include <linux/notifier.h>
>>   #include <linux/of_gpio.h>
>>   #include <linux/platform_device.h>
>> -#include <linux/reboot.h>
>>   #include <linux/watchdog.h>
>>
>>   #define SOFT_TIMEOUT_MIN    1
>> @@ -36,7 +34,6 @@ struct gpio_wdt_priv {
>>       unsigned int        hw_algo;
>>       unsigned int        hw_margin;
>>       unsigned long        last_jiffies;
>> -    struct notifier_block    notifier;
>>       struct timer_list    timer;
>>       struct watchdog_device    wdd;
>>   };
>> @@ -126,26 +123,6 @@ static int gpio_wdt_set_timeout(struct watchdog_device
>> *wdd, unsigned int t)
>>       return gpio_wdt_ping(wdd);
>>   }
>>
>> -static int gpio_wdt_notify_sys(struct notifier_block *nb, unsigned long code,
>> -                   void *unused)
>> -{
>> -    struct gpio_wdt_priv *priv = container_of(nb, struct gpio_wdt_priv,
>> -                          notifier);
>> -
>> -    mod_timer(&priv->timer, 0);
>> -
>> -    switch (code) {
>> -    case SYS_HALT:
>> -    case SYS_DOWN:
>> -        gpio_wdt_disable(priv);
>> -        break;
>> -    default:
>> -        break;
>> -    }
>> -
> Slight difference in semantics here: The stop function only stops the watchdog
> if the 'always_running' flag is not set. The notifier here always stops it,
> or at least tries to stop it. Not really sure what that means, since the
> always_running flag is supposed to mean "the watchdog can not be stopped".
>
> Copying Mike Looijmans, who added the always-running flag, for input.

Okay, I don't know quite what the "core" will do.

If the system wants to reboot, and the watchdog is in "always_running" mode, 
it must NOT stop the watchdog. You have to keep kicking the dog until the 
system reboots and the bootloader can take over. Otherwise, the watchdog may 
turn off the mains power (I developed this for a medical device, which had to 
completely shut down in case of trouble) or do something else that wasn't 
supposed to happen yet.

When shutting down, the assumption is that either the power-down has already 
occured before the watchdog might kick in, or that the watchdog will shut down 
the system because the kernel stopped kicking it. So no special case here, it 
doesn't really matter whether you kick it once more or not.

If the external watchdog reboots the system rather than shuts down power, the 
above scenario won't hurt.

Hope this answers your question, if not, feel free to ask for more information.


Mike.

>
> Thanks,
> Guenter
>
>> -    return NOTIFY_DONE;
>> -}
>> -
>>   static const struct watchdog_info gpio_wdt_ident = {
>>       .options    = WDIOF_MAGICCLOSE | WDIOF_KEEPALIVEPING |
>>                 WDIOF_SETTIMEOUT,
>> @@ -224,23 +201,16 @@ static int gpio_wdt_probe(struct platform_device *pdev)
>>
>>       setup_timer(&priv->timer, gpio_wdt_hwping, (unsigned long)&priv->wdd);
>>
>> +    watchdog_stop_on_reboot(&priv->wdd);
>> +
>>       ret = watchdog_register_device(&priv->wdd);
>>       if (ret)
>>           return ret;
>>
>> -    priv->notifier.notifier_call = gpio_wdt_notify_sys;
>> -    ret = register_reboot_notifier(&priv->notifier);
>> -    if (ret)
>> -        goto error_unregister;
>> -
>>       if (priv->always_running)
>>           gpio_wdt_start_impl(priv);
>>
>>       return 0;
>> -
>> -error_unregister:
>> -    watchdog_unregister_device(&priv->wdd);
>> -    return ret;
>>   }
>>
>>   static int gpio_wdt_remove(struct platform_device *pdev)
>> @@ -248,7 +218,6 @@ static int gpio_wdt_remove(struct platform_device *pdev)
>>       struct gpio_wdt_priv *priv = platform_get_drvdata(pdev);
>>
>>       del_timer_sync(&priv->timer);
>> -    unregister_reboot_notifier(&priv->notifier);
>>       watchdog_unregister_device(&priv->wdd);
>>
>>       return 0;
>>
>



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

Visit us at : Aerospace Electrical Systems Expo Europe which will be held from 17.11.2015 till 19.11.2015, Findorffstrasse 101 Bremen, Germany, Hall 5, stand number C65
http://www.aesexpo.eu

  reply	other threads:[~2015-11-20  7:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 21:02 [PATCH 0/7] watchdog: factorize reboot notifier registration Damien Riegel
2015-11-18 21:02 ` [PATCH 1/7] watchdog: core: add reboot notifier support Damien Riegel
2015-11-20  3:18   ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 2/7] watchdog: bcm47xx_wdt: use core reboot notifier Damien Riegel
2015-11-20  4:13   ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 3/7] watchdog: cadence_wdt: " Damien Riegel
2015-11-20  4:15   ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 4/7] watchdog: gpio_wdt: stop on SYS_DOWN instead of SYS_POWER_OFF Damien Riegel
2015-11-20  4:16   ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 5/7] watchdog: gpio_wdt: use core reboot notifier Damien Riegel
2015-11-20  3:27   ` Guenter Roeck
2015-11-20  7:15     ` Mike Looijmans [this message]
2015-11-20 15:21       ` Damien Riegel
2015-11-20 15:35         ` Guenter Roeck
2015-11-20 15:54           ` Damien Riegel
2015-11-20 16:09             ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 6/7] watchdog: softdog: " Damien Riegel
2015-11-20  4:16   ` Guenter Roeck
2015-11-18 21:02 ` [PATCH 7/7] watchdog: w83627hf_wdt: " Damien Riegel

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=564EC895.20902@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=damien.riegel@savoirfairelinux.com \
    --cc=kernel@savoirfairelinux.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox