mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Martin Kaiser <martin@kaiser.cx>,
	Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Xiubo Li <Li.Xiubo@freescale.com>,
	kernel@pengutronix.de,
	Fabio Estevam <fabio.estevam@freescale.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] watchdog: imx2_wdt: restore previous timeout after suspend+resume
Date: Fri, 29 Dec 2017 08:10:19 -0800	[thread overview]
Message-ID: <080e499c-a31b-e805-f761-6564e02d1be9@roeck-us.net> (raw)
In-Reply-To: <1514555950-28743-1-git-send-email-martin@kaiser.cx>

On 12/29/2017 05:59 AM, Martin Kaiser wrote:
> When the watchdog device is suspended, its timeout is set to the maximum
> value. During resume, the previously set timeout should be restored.
> This does not work at the moment.
> 
> The suspend function calls
> 
> imx2_wdt_set_timeout(wdog, IMX2_WDT_MAX_TIME);
> 
> and resume reverts this by calling
> 
> imx2_wdt_set_timeout(wdog, wdog->timeout);
> 
> However, imx2_wdt_set_timeout() updates wdog->timeout. Therefore,
> wdog->timeout is set to IMX2_WDT_MAX_TIME when we enter the resume
> function.
> 
> Fix this by setting wdog->timeout to the previous value at the end of
> the suspend function. This manual update makes wdog->timeout different
> from the actual setting in the hardware. This should be ok in our case
> as kernel code is not running while we're suspended.
> 
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> Cc: stable@vger.kernel.org

That works, though it is a bit hackish. Better would be to have a function
such as _imx2_wdt_set_timeout() which doesn't actually update wdt->timeout
and could be called from all the other places doing the same.
Separate patch, maybe.

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
>   drivers/watchdog/imx2_wdt.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
> index 4874b0f..66efcc0 100644
> --- a/drivers/watchdog/imx2_wdt.c
> +++ b/drivers/watchdog/imx2_wdt.c
> @@ -368,6 +368,7 @@ static int imx2_wdt_suspend(struct device *dev)
>   {
>   	struct watchdog_device *wdog = dev_get_drvdata(dev);
>   	struct imx2_wdt_device *wdev = watchdog_get_drvdata(wdog);
> +	unsigned int resume_timeout = wdog->timeout;
>   
>   	/* The watchdog IP block is running */
>   	if (imx2_wdt_is_running(wdev)) {
> @@ -377,6 +378,7 @@ static int imx2_wdt_suspend(struct device *dev)
>   
>   	clk_disable_unprepare(wdev->clk);
>   
> +	wdog->timeout = resume_timeout;
>   	return 0;
>   }
>   
> 

  reply	other threads:[~2017-12-29 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 13:59 Martin Kaiser
2017-12-29 16:10 ` Guenter Roeck [this message]
2017-12-31 11:17 ` [PATCH v2] " Martin Kaiser
2017-12-31 14:43   ` Guenter Roeck
2018-01-01 17:26 ` [PATCH v3] " Martin Kaiser
2018-01-01 18:14   ` 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=080e499c-a31b-e805-f761-6564e02d1be9@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Li.Xiubo@freescale.com \
    --cc=fabio.estevam@freescale.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=martin@kaiser.cx \
    --cc=stable@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®