From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Warp Watchdog
Date: Mon, 21 Jan 2008 08:01:57 -0600 [thread overview]
Message-ID: <20080121080157.0b66c7fc@zod.rchland.ibm.com> (raw)
In-Reply-To: <478FB93A.7040505@pikatech.com>
On Thu, 17 Jan 2008 15:23:22 -0500
Sean MacLennan <smaclennan@pikatech.com> wrote:
> The taco, er warp, has a watchdog timer built into the fpga. The
> watchdog is very trivial and very tied to the warp. I have put it has
> part of the platform code rather than a standalone module.
>
> Two reasons for this: one, once started it can't be stopped. A module
> unload would be fatal ;) Two, it is so closely tied to the taco that it
> really has no use otherwise.
The first isn't much of a reason. The watchdog on the 44x and FSL
Book-E cores have the same behavior.
> The platform always starts the watchdog, assuming you asked for the
> watchdog, but does not enable it until hit from user mode.
>
> What is the general feeling about this implementation? I am not
> submitting this for inclusion in the kernel right now, just feeling out
> what others think.
I'm not thrilled with it being in the platform file itself. It should
really go into drivers/watchdog. It's OK that the watchdog is tied to
Warp, that really isn't an issue. Just make it depend on Warp in the
Kconfig file. And you can select it in your board config so that it's
built in-kernel and not as a module.
The code itself looks pretty clean.
josh
next prev parent reply other threads:[~2008-01-21 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 20:23 Warp Watchdog Sean MacLennan
2008-01-21 14:01 ` Josh Boyer [this message]
2008-01-21 17:50 ` Sean MacLennan
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=20080121080157.0b66c7fc@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
/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;
as well as URLs for NNTP newsgroup(s).