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: kernel@pengutronix.de,
Fabio Estevam <fabio.estevam@freescale.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] watchdog: imx2_wdt: restore previous timeout after suspend+resume
Date: Sun, 31 Dec 2017 06:43:55 -0800 [thread overview]
Message-ID: <765527e5-a6d3-e75e-a3ad-8b800e7bcc1e@roeck-us.net> (raw)
In-Reply-To: <1514719023-5916-1-git-send-email-martin@kaiser.cx>
Hi Martin,
On 12/31/2017 03:17 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 adding a new function __imx2_wdt_set_timeout() which
> only updates the hardware settings. imx2_wdt_set_timeout() now calls
> __imx2_wdt_set_timeout() and then saves the new timeout to
> wdog->timeout.
>
> During suspend, we call __imx2_wdt_set_timeout() directly so that
> wdog->timeout won't be updated and we can restore the previous value
> during resume. This approach makes wdog->timeout different from the
> actual setting in the hardware which is usually not a good thing.
> However, the two differ only while we're suspended and no kernel code is
> running, so it should be ok in this case.
>
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> Cc: stable@vger.kernel.org
> ---
> changes in v2:
> helper function that updates the hw settings, as per Guenter's proposal
>
> drivers/watchdog/imx2_wdt.c | 23 +++++++++++++++++++----
> 1 file changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
> index 4874b0f..b0c2bca 100644
> --- a/drivers/watchdog/imx2_wdt.c
> +++ b/drivers/watchdog/imx2_wdt.c
> @@ -169,18 +169,29 @@ static int imx2_wdt_ping(struct watchdog_device *wdog)
> return 0;
> }
>
> -static int imx2_wdt_set_timeout(struct watchdog_device *wdog,
> +static int __imx2_wdt_set_timeout(struct watchdog_device *wdog,
> unsigned int new_timeout)
Please align the continuation line with '('.
Also, the function type should be void (always returning 0 and checking
that return value does not add any value).
Thanks,
Guenter
> {
> struct imx2_wdt_device *wdev = watchdog_get_drvdata(wdog);
>
> - wdog->timeout = new_timeout;
> -
> regmap_update_bits(wdev->regmap, IMX2_WDT_WCR, IMX2_WDT_WCR_WT,
> WDOG_SEC_TO_COUNT(new_timeout));
> return 0;
> }
>
> +static int imx2_wdt_set_timeout(struct watchdog_device *wdog,
> + unsigned int new_timeout)
> +{
> + int ret;
> +
> + ret = __imx2_wdt_set_timeout(wdog, new_timeout);
> + if (ret < 0)
> + return ret;
> +
> + wdog->timeout = new_timeout;
> + return 0;
> +}
> +
> static int imx2_wdt_set_pretimeout(struct watchdog_device *wdog,
> unsigned int new_pretimeout)
> {
> @@ -371,7 +382,11 @@ static int imx2_wdt_suspend(struct device *dev)
>
> /* The watchdog IP block is running */
> if (imx2_wdt_is_running(wdev)) {
> - imx2_wdt_set_timeout(wdog, IMX2_WDT_MAX_TIME);
> + /*
> + * Don't update wdog->timeout, we'll restore the current value
> + * during resume.
> + */
> + __imx2_wdt_set_timeout(wdog, IMX2_WDT_MAX_TIME);
> imx2_wdt_ping(wdog);
> }
>
>
next prev parent reply other threads:[~2017-12-31 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 13:59 [PATCH] " Martin Kaiser
2017-12-29 16:10 ` Guenter Roeck
2017-12-31 11:17 ` [PATCH v2] " Martin Kaiser
2017-12-31 14:43 ` Guenter Roeck [this message]
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=765527e5-a6d3-e75e-a3ad-8b800e7bcc1e@roeck-us.net \
--to=linux@roeck-us.net \
--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®