mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cypher Wu <cypher.w@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Questions about Watch Dog Timer under Linux.
Date: Sat, 12 Dec 2009 11:46:04 +0800	[thread overview]
Message-ID: <f9f38a550912111946w665b267dkc42d184bdc437d02@mail.gmail.com> (raw)
In-Reply-To: <20091211102159.GB18825@rakim.wolfsonmicro.main>

On Fri, Dec 11, 2009 at 6:21 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Fri, Dec 11, 2009 at 04:27:55PM +0800, Cypher Wu wrote:
>
> Please reply in-line to e-mails, it makes the conversation much easier
> to follow.
>
>> It seems WATCHDOG_NOWAYOUT is a software mechanism? If it is defined
>> as 1 then the WDT can't be stopped if it has been started whether bye
>> closing the device file or writing the magic character 'V'.
>
> Yes, it's a kernel build time configurable option to select this
> behaviour.  In effect all you'd be doing is making a driver which turns
> it on all the time.
>

My point is not making a driver which turns WDT on all the time, but
how to work with a WDT hardware which will startup to working just
after power on and the only interface it provides is clearing the
timer. This type of WDT is widely used in our embedded systems and we
usually install a callback in timer interrupt to clearing WD before
BSP starting the RTOS kernel, and then starting a task to clear WD and
uninstall the callback.
I'm wonder when cope with that type of WD, is there any framework
already in the Linux kernel and booter, or I've to modify them by
myself?

  reply	other threads:[~2009-12-12  3:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 14:47 Cypher Wu
2009-12-09 14:59 ` Mark Brown
2009-12-11  8:27   ` Cypher Wu
2009-12-11 10:21     ` Mark Brown
2009-12-12  3:46       ` Cypher Wu [this message]
2009-12-12 13:50         ` Alan Cox
2009-12-09 16:29 ` Alan Cox
2009-12-11  8:33   ` Cypher Wu
2009-12-09 17:26 ` Pádraig Brady
2009-12-11  8:38   ` Cypher Wu

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=f9f38a550912111946w665b267dkc42d184bdc437d02@mail.gmail.com \
    --to=cypher.w@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®