From: Kumar Gala <galak@kernel.crashing.org>
To: Jochen Friedrich <jochen@scram.de>
Cc: wim@iguana.be, Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFCv2] wdt: Add support for PowerQUICC watchdog
Date: Thu, 17 Jan 2008 09:11:57 -0600 [thread overview]
Message-ID: <9E91DB29-BBB8-4CC9-8F6D-71306329D7A5@kernel.crashing.org> (raw)
In-Reply-To: <478F6C5F.4010505@scram.de>
On Jan 17, 2008, at 8:55 AM, Jochen Friedrich wrote:
> Hi Kumar,
>
>> Why are you commenting on mpc83xx_wdt with respect to pq1_wdt?
>> Also, is this driver just for PQ1 platforms or PQ1 & PQ2? If its
>> just pq1 we should probably call it pq1_wdt*
>
> It should be for pq1, pq2 and pq2pro. However, i only have the
> possibility
> to test this on pq1.
>
>>> arch/powerpc/platforms/8xx/mpc86xads_setup.c | 5 +
>>> arch/powerpc/platforms/8xx/mpc885ads_setup.c | 5 +
>>> arch/powerpc/sysdev/Makefile | 3 +
>>> arch/powerpc/sysdev/pq_wdt.c | 203 +++++++++++++++
>>> ++++++++
>>> arch/powerpc/sysdev/pq_wdt.h | 28 ++++
>>> drivers/watchdog/Kconfig | 13 ++-
>>> drivers/watchdog/Makefile | 1 +
>>> drivers/watchdog/pq_wdt.c | 225 +++++++++++++++
>>> +++++++++++
>>> 8 files changed, 482 insertions(+), 1 deletions(-)
>>> create mode 100644 arch/powerpc/sysdev/pq_wdt.c
>>> create mode 100644 arch/powerpc/sysdev/pq_wdt.h
>>> create mode 100644 drivers/watchdog/pq_wdt.c
>> What are the bits in sysdev/pq_wdt.{c,h}. Why aren't these just in
>> drivers/watchdog?
>
> These are the parts needed to boot a device with activated watchdog.
> If a bootloader like u-boot activates the watchdog, it can't be
> deactivated again
> and needs to be reset at regular intervals. This is done using a
> kernel timer.
> The driver in drivers/watchdog disables the timer as soon as the wdt
> device
> is opened.
Ok, but is there a need for these bits to be in sysdev vs just being
in the driver and calling into it.
- k
prev parent reply other threads:[~2008-01-17 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 12:47 Jochen Friedrich
2008-01-17 14:31 ` Kumar Gala
2008-01-17 14:55 ` Jochen Friedrich
2008-01-17 15:11 ` Kumar Gala [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=9E91DB29-BBB8-4CC9-8F6D-71306329D7A5@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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
all inboxes | Powered by JetHome®