From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, mika.westerberg@linux.intel.com
Subject: Re: [PATCH v1 1/1] intel-mid_wdt: make sure watchdog is not running at startup
Date: Sat, 19 Nov 2016 18:10:03 +0200 [thread overview]
Message-ID: <1479571803.22212.47.camel@linux.intel.com> (raw)
In-Reply-To: <265e4708-7658-d45f-7036-f2804e12e585@roeck-us.net>
On Sat, 2016-11-19 at 07:55 -0800, Guenter Roeck wrote:
> On 11/18/2016 06:50 AM, Andy Shevchenko wrote:
> > Make sure that the watchdog is not running after loading
> > and before it is started by opening /dev/watchdog.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Thanks!
>
> I don't really like turning off the watchdog, but I guess it is the
> only
> remedy we have if it doesn't tell us if it is running.
That is my understanding based on current documentation and driver
implementation we have.
>
> Guenter
>
> > ---
> > drivers/watchdog/intel-mid_wdt.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/watchdog/intel-mid_wdt.c
> > b/drivers/watchdog/intel-mid_wdt.c
> > index db36d12..ff099a3 100644
> > --- a/drivers/watchdog/intel-mid_wdt.c
> > +++ b/drivers/watchdog/intel-mid_wdt.c
> > @@ -151,6 +151,9 @@ static int mid_wdt_probe(struct platform_device
> > *pdev)
> > return ret;
> > }
> >
> > + /* Make sure the watchdog is not running */
> > + wdt_stop(wdt_dev);
> > +
> > ret = watchdog_register_device(wdt_dev);
> > if (ret) {
> > dev_err(&pdev->dev, "error registering watchdog
> > device\n");
> >
>
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2016-11-19 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 14:50 [PATCH v1 1/1] intel-mid_wdt: make sure watchdog is not running at startup Andy Shevchenko
2016-11-18 15:50 ` Guenter Roeck
2016-11-18 17:36 ` Andy Shevchenko
2016-11-19 15:55 ` Guenter Roeck
2016-11-19 16:10 ` Andy Shevchenko [this message]
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=1479571803.22212.47.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mika.westerberg@linux.intel.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.