public inbox for linux-watchdog@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
	Felipe Balbi <balbi@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
	unknown author <unknown.author@example.com>,
	kernel@pengutronix.de
Subject: Re: [PATCH v2 6/4] watchdog: omap: allow to keep timer running at probe time
Date: Tue, 5 May 2015 15:53:29 +0200	[thread overview]
Message-ID: <20150505135329.GJ25193@pengutronix.de> (raw)
In-Reply-To: <55430683.2030102@roeck-us.net>

Hello Guenter,

On Thu, Apr 30, 2015 at 09:52:19PM -0700, Guenter Roeck wrote:
> On 04/29/2015 11:38 AM, Uwe Kleine-König wrote:
> >From: unknown author <unknown.author@example.com>
> >
> >On some machines it might be desirable to keep the watchdog that is
> >started in the boot ROM running until userspace starts stroking it to be
> >able to handle boot failures.
> >
> >To not introduce regressions for users not caring about the watchdog
> >keep the previous behaviour of disabling the watchdog in the probe
> >function unless a module parameter stop_at_probe is set to false.
> >
> >Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> Uwe,
> 
> would this address the problem you are tryng to solve ?
> 
> http://www.spinics.net/lists/arm-kernel/msg413658.html
yeah, it would. It just doesn't solve my problem now as the series isn't
ready for merging yet :-) I will keep my patch locally for the project
I'm working on and already provided feedback to this thread.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-05-05 13:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  9:22 [PATCH v2 0/4] watchdog: omap: several cleanups Uwe Kleine-König
2015-04-27  9:22 ` [PATCH v2 1/4] watchdog: omap: clearify device tree documentation Uwe Kleine-König
2015-04-27  9:22 ` [PATCH v2 2/4] watchdog: omap: use watchdog_init_timeout instead of open coding it Uwe Kleine-König
2015-04-27  9:23 ` [PATCH v2 3/4] watchdog: omap: put struct watchdog_device into driver data Uwe Kleine-König
2015-04-27  9:23 ` [PATCH v2 4/4] watchdog: omap: simplify assignment of bootstatus Uwe Kleine-König
2015-04-29 18:38 ` [PATCH v2 5/4] watchdog: omap: assert the counter being stopped before reprogramming Uwe Kleine-König
2015-05-01  4:53   ` Guenter Roeck
2015-04-29 18:38 ` [PATCH v2 6/4] watchdog: omap: allow to keep timer running at probe time Uwe Kleine-König
2015-04-29 18:47   ` Uwe Kleine-König
2015-05-01  4:52   ` Guenter Roeck
2015-05-05 13:53     ` Uwe Kleine-König [this message]
2015-05-08  7:35 ` [PATCH v2 0/4] watchdog: omap: several cleanups Uwe Kleine-König
2015-05-22 17:59   ` Uwe Kleine-König
2015-05-22 19:18     ` Guenter Roeck
2015-07-31  9:33       ` Uwe Kleine-König
2015-07-31 10:04         ` Guenter Roeck
2015-07-31 14:52           ` Uwe Kleine-König
2015-07-31 16:03             ` 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=20150505135329.GJ25193@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=balbi@ti.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lokeshvutla@ti.com \
    --cc=unknown.author@example.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