[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170925120742.ja54wu2orgai6fsr@piout.net>
Date: Mon, 25 Sep 2017 14:07:42 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: "winton.liu" <18502523564@....com>
Cc: a.zummo@...ertech.it, linux-rtc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rtc: ds1374: wdt:support suspend/resume for watchdog
Hi,
On 25/09/2017 at 19:58:44 +0800, winton.liu wrote:
> When enable CONFIG_RTC_DRV_DS1374_WDT use as watchdog,
> in suspend mode, watchdog is still working but no daemon
> patting the watchdog. The system will reboot if timeout.
> So disable watchdog in suspend and recover it in resume.
>
That is definitively not what we want. Many people will want to still
have the watchdog running when the platform is suspended. Your options
are to either disable the watchdog before going to suspend or wake up
the platform just in time to ping the watchdog.
> Signed-off-by: winton.liu <18502523564@....com>
> ---
> drivers/rtc/rtc-ds1374.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/rtc/rtc-ds1374.c b/drivers/rtc/rtc-ds1374.c
> index 38a2e9e..e990773 100644
> --- a/drivers/rtc/rtc-ds1374.c
> +++ b/drivers/rtc/rtc-ds1374.c
> @@ -690,6 +690,10 @@ static int ds1374_suspend(struct device *dev)
> {
> struct i2c_client *client = to_i2c_client(dev);
>
> +#ifdef CONFIG_RTC_DRV_DS1374_WDT
> + ds1374_wdt_disable();
> +#endif
> +
> if (client->irq > 0 && device_may_wakeup(&client->dev))
> enable_irq_wake(client->irq);
> return 0;
> @@ -699,6 +703,10 @@ static int ds1374_resume(struct device *dev)
> {
> struct i2c_client *client = to_i2c_client(dev);
>
> +#ifdef CONFIG_RTC_DRV_DS1374_WDT
> + ds1374_wdt_settimeout(131072);
> +#endif
> +
> if (client->irq > 0 && device_may_wakeup(&client->dev))
> disable_irq_wake(client->irq);
> return 0;
> --
> 1.9.1
>
>
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Powered by blists - more mailing lists