From: Guenter Roeck <linux@roeck-us.net>
To: Jingchang Lu <jingchang.lu@freescale.com>
Cc: wim@iguana.be, shawn.guo@freescale.com, arnd@arndb.de,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] watchdog: imx2_wdt: add restart handler support
Date: Thu, 11 Sep 2014 08:55:22 -0700 [thread overview]
Message-ID: <20140911155522.GB13052@roeck-us.net> (raw)
In-Reply-To: <1410421661-15298-1-git-send-email-jingchang.lu@freescale.com>
On Thu, Sep 11, 2014 at 03:47:41PM +0800, Jingchang Lu wrote:
> Register the watchdog as the system restart function
> to the new introducing kernel restart call chain in the
> driver instead of providing the restart in machine desc.
> This restart handler function is from the mxc_restart()
> in arch/arm/mach-imx/system.c
>
> Signed-off-by: Jingchang Lu <jingchang.lu@freescale.com>
> ---
> drivers/watchdog/imx2_wdt.c | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
> index 68c3d37..fa723e8 100644
> --- a/drivers/watchdog/imx2_wdt.c
> +++ b/drivers/watchdog/imx2_wdt.c
> @@ -22,14 +22,17 @@
> */
>
> #include <linux/clk.h>
> +#include <linux/delay.h>
> #include <linux/init.h>
> #include <linux/io.h>
> #include <linux/jiffies.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/moduleparam.h>
> +#include <linux/notifier.h>
> #include <linux/of_address.h>
> #include <linux/platform_device.h>
> +#include <linux/reboot.h>
> #include <linux/regmap.h>
> #include <linux/timer.h>
> #include <linux/watchdog.h>
> @@ -59,6 +62,7 @@ struct imx2_wdt_device {
> struct regmap *regmap;
> struct timer_list timer; /* Pings the watchdog when closed */
> struct watchdog_device wdog;
> + struct notifier_block restart_handler;
> };
>
> static bool nowayout = WATCHDOG_NOWAYOUT;
> @@ -77,6 +81,31 @@ static const struct watchdog_info imx2_wdt_info = {
> .options = WDIOF_KEEPALIVEPING | WDIOF_SETTIMEOUT | WDIOF_MAGICCLOSE,
> };
>
> +static int imx2_restart_handler(struct notifier_block *this, unsigned long mode,
> + void *cmd)
> +{
> + unsigned int wcr_enable = IMX2_WDT_WCR_WDE;
In the original code this value is conditional depending on cpu_is_mx1().
Are there any implications for this reset mechanism ? Does mx1 have a
different watchdog driver ?
> + struct imx2_wdt_device *wdev = container_of(this,
> + struct imx2_wdt_device,
> + restart_handler);
Please align second lines with '('.
> + /* Assert SRS signal */
> + regmap_write(wdev->regmap, 0, wcr_enable);
> + /*
> + * Due to imx6q errata ERR004346 (WDOG: WDOG SRS bit requires to be
> + * written twice), we add another two writes to ensure there must be at
> + * least two writes happen in the same one 32kHz clock period. We save
> + * the target check here, since the writes shouldn't be a huge burden
> + * for other platforms.
> + */
> + regmap_write(wdev->regmap, 0, wcr_enable);
> + regmap_write(wdev->regmap, 0, wcr_enable);
> +
> + /* wait for reset to assert... */
> + mdelay(500);
> +
> + return NOTIFY_DONE;
> +}
> +
> static inline void imx2_wdt_setup(struct watchdog_device *wdog)
> {
> struct imx2_wdt_device *wdev = watchdog_get_drvdata(wdog);
> @@ -257,6 +286,12 @@ static int __init imx2_wdt_probe(struct platform_device *pdev)
> return ret;
> }
>
> + wdev->restart_handler.notifier_call = imx2_restart_handler;
> + wdev->restart_handler.priority = 128;
> + ret = register_restart_handler(&wdev->restart_handler);
> + if (ret)
> + dev_err(&pdev->dev, "cannot register restart handler\n");
> +
> dev_info(&pdev->dev, "timeout %d sec (nowayout=%d)\n",
> wdog->timeout, nowayout);
>
> @@ -268,6 +303,8 @@ static int __exit imx2_wdt_remove(struct platform_device *pdev)
> struct watchdog_device *wdog = platform_get_drvdata(pdev);
> struct imx2_wdt_device *wdev = watchdog_get_drvdata(wdog);
>
> + unregister_restart_handler(&wdev->restart_handler);
> +
> watchdog_unregister_device(wdog);
>
> if (imx2_wdt_is_running(wdev)) {
> --
> 1.8.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-11 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 7:47 [PATCH] watchdog: imx2_wdt: add restart handler support Jingchang Lu
2014-09-11 15:55 ` Guenter Roeck [this message]
2014-09-12 2:42 ` Jingchang Lu
2014-09-12 2:49 ` Guenter Roeck
2014-09-12 3:12 ` Jingchang Lu
2014-09-12 7:45 ` Shawn Guo
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=20140911155522.GB13052@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=jingchang.lu@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=shawn.guo@freescale.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