From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Alan" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, info-linux@ldcmail.amd.com
Subject: Re: char: Add MFGPT driver for the CS5535/CS5536
Date: Mon, 27 Nov 2006 13:04:21 -0700 [thread overview]
Message-ID: <20061127200421.GB4495@cosmic.amd.com> (raw)
In-Reply-To: <LYRIS-4270-95737-2006.11.22-15.19.56--jordan.crouse#amd.com@whitestar.amd.com>
On 22/11/06 22:17 +0000, Alan wrote:
> > The attached driver provides a low-level interface to the block, and
> > allows for other kernel drivers to use the timers.
>
> Three comments
>
> 2. There is an RTC timer interface - could you use that interface
> for some of this so its compatible and consistent ?
Do you mean, use the RTC interface itself (i.e. - turn the mfgpt driver
into an RTC driver), or just emulate parts of the RTC interface in the
MFGPT driver. I would be fine with the second option - the first doesn't
really fit, since the only functionality the RTC and the MFGPT share is
the periodic interrupt feature (which is sub-optimal on RTC anyway).
If the "timer interrupt" feature feels tacked on, thats because it is.
The best use for the MFGPT block is to drive a duty cycle on the
output pin suitable for LEDs and such. Most Geode customers would use
it for that purpose. Running a close second on the usefulness scale is
the watchdog timer - its always nice to have that sort of functionality
available at the hardware level (and its a double bonus that the watchdog
can be set up to continue running while in suspend).
The interrupt/NMI functionality was added to the hardware for the BIOS to
use, and we added it to the kernel driver for a sense of completeness.
I personally can't fathom anybody using the timers, and I would gladly
remove them if nobody else can come up with a realistic usage model.
> 3. Ditto for a watchdog use - although that would be a separate
> driver using the kernel hooks anyway.
That was the plan - I do have a watchdog driver that I had when I first
wrote the MFGPT driver for a now defunct project. I should dust it off
and add it in.
Thanks,
Jordan
--
Jordan Crouse
Senior Linux Engineer
Advanced Micro Devices, Inc.
<www.amd.com/embeddedprocessors>
prev parent reply other threads:[~2006-11-27 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 20:57 [RFC] " Jordan Crouse
2006-11-22 22:17 ` Alan
[not found] ` <LYRIS-4270-95737-2006.11.22-15.19.56--jordan.crouse#amd.com@whitestar.amd.com>
2006-11-27 20:04 ` Jordan Crouse [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=20061127200421.GB4495@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=info-linux@ldcmail.amd.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®