From: Guenter Roeck <linux@roeck-us.net>
To: 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: [RFC PATCH 10/13] watchdog: mtk_wdt: use core restart handler
Date: Mon, 2 Nov 2015 18:35:08 -0800 [thread overview]
Message-ID: <56381D5C.8030503@roeck-us.net> (raw)
In-Reply-To: <1446514586-31455-11-git-send-email-damien.riegel@savoirfairelinux.com>
On 11/02/2015 05:36 PM, Damien Riegel wrote:
> Get rid of the custom restart handler by using the one provided by the
> watchdog core.
>
> Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> ---
> drivers/watchdog/mtk_wdt.c | 19 ++++---------------
> 1 file changed, 4 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
> index 6ad9df9..277f588 100644
> --- a/drivers/watchdog/mtk_wdt.c
> +++ b/drivers/watchdog/mtk_wdt.c
> @@ -29,7 +29,6 @@
> #include <linux/types.h>
> #include <linux/watchdog.h>
> #include <linux/notifier.h>
> -#include <linux/reboot.h>
> #include <linux/delay.h>
>
> #define WDT_MAX_TIMEOUT 31
> @@ -64,16 +63,13 @@ static unsigned int timeout = WDT_MAX_TIMEOUT;
> struct mtk_wdt_dev {
> struct watchdog_device wdt_dev;
> void __iomem *wdt_base;
> - struct notifier_block restart_handler;
> };
>
> -static int mtk_reset_handler(struct notifier_block *this, unsigned long mode,
> - void *cmd)
> +static int mtk_wdt_restart(struct watchdog_device *wdt_dev)
> {
> - struct mtk_wdt_dev *mtk_wdt;
> + struct mtk_wdt_dev *mtk_wdt = watchdog_get_drvdata(wdt_dev);
> void __iomem *wdt_base;
>
> - mtk_wdt = container_of(this, struct mtk_wdt_dev, restart_handler);
> wdt_base = mtk_wdt->wdt_base;
>
> while (1) {
Changed return value missing here ? Sure, it won't return, but still.
Ah, that reminds me - "#include <linux/notifier.h>" can probably be dropped
from most of the files. Can you look into that for all patches (including the
ones I already reviewed) ?
Thanks,
Guenter
> @@ -160,6 +156,7 @@ static const struct watchdog_ops mtk_wdt_ops = {
> .stop = mtk_wdt_stop,
> .ping = mtk_wdt_ping,
> .set_timeout = mtk_wdt_set_timeout,
> + .restart = mtk_wdt_restart,
> };
>
> static int mtk_wdt_probe(struct platform_device *pdev)
> @@ -188,6 +185,7 @@ static int mtk_wdt_probe(struct platform_device *pdev)
>
> watchdog_init_timeout(&mtk_wdt->wdt_dev, timeout, &pdev->dev);
> watchdog_set_nowayout(&mtk_wdt->wdt_dev, nowayout);
> + watchdog_set_restart_priority(&mtk_wdt->wdt_dev, 128);
>
> watchdog_set_drvdata(&mtk_wdt->wdt_dev, mtk_wdt);
>
> @@ -197,13 +195,6 @@ static int mtk_wdt_probe(struct platform_device *pdev)
> if (unlikely(err))
> return err;
>
> - mtk_wdt->restart_handler.notifier_call = mtk_reset_handler;
> - mtk_wdt->restart_handler.priority = 128;
> - err = register_restart_handler(&mtk_wdt->restart_handler);
> - if (err)
> - dev_warn(&pdev->dev,
> - "cannot register restart handler (err=%d)\n", err);
> -
> dev_info(&pdev->dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> mtk_wdt->wdt_dev.timeout, nowayout);
>
> @@ -222,8 +213,6 @@ static int mtk_wdt_remove(struct platform_device *pdev)
> {
> struct mtk_wdt_dev *mtk_wdt = platform_get_drvdata(pdev);
>
> - unregister_restart_handler(&mtk_wdt->restart_handler);
> -
> watchdog_unregister_device(&mtk_wdt->wdt_dev);
>
> return 0;
>
next prev parent reply other threads:[~2015-11-03 2:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 1:36 [RFC PATCH 00/13] watchdog: factorize restart handler registration Damien Riegel
2015-11-03 1:36 ` [RFC PATCH 01/13] watchdog: core: add restart handler support Damien Riegel
2015-11-03 2:25 ` Guenter Roeck
2015-11-03 2:51 ` Vivien Didelot
2015-11-03 3:14 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 02/13] watchdog: bcm47xx_wdt: use core restart handler Damien Riegel
2015-11-03 2:26 ` Guenter Roeck
2015-11-03 14:21 ` Vivien Didelot
2015-11-03 14:46 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 03/13] watchdog: da9063_wdt: " Damien Riegel
2015-11-03 2:26 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 04/13] watchdog: digicolor_wdt: " Damien Riegel
2015-11-03 2:27 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 05/13] watchdog: imgpdc_wdt: " Damien Riegel
2015-11-03 2:28 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 06/13] watchdog: imx2_wdt: " Damien Riegel
2015-11-03 2:29 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 07/13] watchdog: lpc18xx_wdt: " Damien Riegel
2015-11-03 2:30 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 08/13] watchdog: meson_wdt: " Damien Riegel
2015-11-03 2:31 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 09/13] watchdog: moxart_wdt: " Damien Riegel
2015-11-03 2:32 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 10/13] watchdog: mtk_wdt: " Damien Riegel
2015-11-03 2:35 ` Guenter Roeck [this message]
2015-11-03 1:36 ` [RFC PATCH 11/13] watchdog: qcom-wdt: " Damien Riegel
2015-11-03 2:37 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 12/13] watchdog: s3c2410_wdt: " Damien Riegel
2015-11-03 2:38 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 13/13] watchdog: sunxi_wdt: " Damien Riegel
2015-11-03 2:41 ` 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=56381D5C.8030503@roeck-us.net \
--to=linux@roeck-us.net \
--cc=damien.riegel@savoirfairelinux.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-watchdog@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.