Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wim Van Sebroeck <wim@iguana.be>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2] watchdog: intel-mid_wdt: Keep watchdog running
Date: Fri, 10 Mar 2017 19:05:49 +0200	[thread overview]
Message-ID: <1489165549.20145.197.camel@linux.intel.com> (raw)
In-Reply-To: <20170310165138.53825-1-andriy.shevchenko@linux.intel.com>

On Fri, 2017-03-10 at 18:51 +0200, Andy Shevchenko wrote:
> Firmware followed by bootloader leaves watchdog running.
> 
> Keep it running in the driver.
> 
> User will not need any additional options to reboot in case of panic
> during boot.

> -	/* Make sure the watchdog is not running */
> -	wdt_stop(wdt_dev);
> +	/*
> +	 * Make sure the watchdog is serviced.
> +	 *
> +	 * The firmware followed by U-Boot leaves the watchdog
> running
> +	 * with the default threshold 60 seconds. Our default timeout
> is
> +	 * 90 seconds, but internal worker divides it by two, which
> is
> +	 * 45 seconds and should be enough (less by 15 seconds than
> +	 * threshold).
> +	 */
> +	set_bit(WDOG_HW_RUNNING, &wdt_dev->status);

Giving one more thought here perhaps more robust will be to start
watchdog unconditionally here?

In that case it will be no matter how it's configured in firmware and/or
boot loader.

>  
>  	ret = devm_watchdog_register_device(&pdev->dev, wdt_dev);
>  	if (ret) {

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-03-10 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 16:51 [PATCH v2] watchdog: intel-mid_wdt: Keep watchdog running Andy Shevchenko
2017-03-10 17:05 ` Andy Shevchenko [this message]
2017-03-10 17:16   ` Guenter Roeck
2017-03-10 17:26     ` Andy Shevchenko
2017-03-10 17:35       ` 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=1489165549.20145.197.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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