public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Igor Stoppa <igor.stoppa@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/3] CBUS: Make retu watchdog behave like a standard Linux watchdog
Date: Thu, 15 May 2008 14:46:41 -0700	[thread overview]
Message-ID: <20080515214640.GV8928@atomide.com> (raw)
In-Reply-To: <20080513011736.GH28999@atomide.com>

* Tony Lindgren <tony@atomide.com> [080512 18:17]:
> * Igor Stoppa <igor.stoppa@nokia.com> [080512 17:56]:
> > Hi Tony,
> > On Mon, 2008-05-12 at 17:35 -0700, ext Tony Lindgren wrote:
> > > Make retu watchdog behave like a standard Linux watchdog.
> > > 
> > > Let the kernel do the kicking until the watchdog device is opened.
> > 
> > This is not always the desidered behavior: the powerdown wd is used to
> > ensure that the whole sw stack is healty: doing the kicking in
> > kernelspace for free introduces the case where userspace can get stuck
> > and the device does not powerdown.
> 
> That's why there's CONFIG_WATCHDOG_NOWAYOUT where the ping timer is
> not enabled at all, and the watchdog is just set to max until userspace
> watchdog software kicking starts.
> 
> > Also the unconditional loading of the maximum value during probe is not
> > aligned with the original reset logic, which was to have the powerdown
> > wd to allow for 2 boot attempts:
> > 
> > -cold boot -> load max value in retu wd (63s)
> >            -> load 30s in omap wd
> > -try to kick both wds
> 
> Well you can set those values via /dev/watchdog too, right?
> And then use CONFIG_WATCHDOG_NOWAYOUT.
> 
> And ff CONFIG_WATCHDOG_NOWAYOUT is not set, the kernel ping timer only
> happens when /dev/watchdog is not open.
> 
> > if fail, then omap reboots, but retu keeps counting down
> > 
> > -warm boot -> let the retu wd untouched
> >            -> load 30s in omap wd
> > -try to kick both wds
> > 
> > if fail, retu powers down
> > 
> > That was the original idea in 770 times and i still like it.
> > 
> > To conclude, i'd see inkernel kicking more as a debugging feature while
> > one is hacking at the kernel than a desirable quality of a stable
> > kernel.
> 
> Considering that the /dev/watchdog interface is the standard, I see this
> patch as the only way we can get this code ever merged upstream. And it's
> easy to patch back the non-standard if you want to.

I'll push the first two patches today, third one still needs to be
checked.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-05-15 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  0:35 [PATCH 0/3] Retu watchdog clean-up and fix to make it behave Tony Lindgren
2008-05-13  0:35 ` [PATCH 1/3] CBUS: Fix retu mutex handling Tony Lindgren
2008-05-13  0:35   ` [PATCH 2/3] CBUS: Checkpatch.pl fixes for retu-wdt.c Tony Lindgren
2008-05-13  0:35     ` [PATCH 3/3] CBUS: Make retu watchdog behave like a standard Linux watchdog Tony Lindgren
2008-05-13  0:46       ` Igor Stoppa
2008-05-13  1:17         ` Tony Lindgren
2008-05-15 21:46           ` Tony Lindgren [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=20080515214640.GV8928@atomide.com \
    --to=tony@atomide.com \
    --cc=igor.stoppa@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    /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