public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Jordan Crouse" <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org, info-linux@ldcmail.amd.com
Subject: Re: [RFC] char: Add MFGPT driver for the CS5535/CS5536
Date: Wed, 22 Nov 2006 22:17:31 +0000	[thread overview]
Message-ID: <20061122221731.356939cb@localhost.localdomain> (raw)
In-Reply-To: <20061122205736.GA588@cosmic.amd.com>

On Wed, 22 Nov 2006 13:57:36 -0700
"Jordan Crouse" <jordan.crouse@amd.com> wrote:

> The Geode CS5535 and CS5536 companion chips contain a block of timers
> known as the Multi Function General Purpose Timers.  The primary use
> for these timers is to control an output pin nominally connected to a
> LED or other visual indicator.  They also can be configured to reset the
> system, which is handy as a watchdog timer.  they _can_ be used to
> fire software interrupts on timeout too, but this is less useful since the
> timers are fairly low resolution and there are much better options available.
> 
> The attached driver provides a low-level interface to the block, and 
> allows for other kernel drivers to use the timers. 

Three comments

1.	Use inlines not defines when you can - it means we get type
checking
2.	There is an RTC timer interface - could you use that interface
for some of this so its compatible and consistent ?
3.	Ditto for a watchdog use - although that would be a separate
driver using the kernel hooks anyway.

Kernel side looks fairly sane

  reply	other threads:[~2006-11-22 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 20:57 [RFC] char: Add MFGPT driver for the CS5535/CS5536 Jordan Crouse
2006-11-22 22:17 ` Alan [this message]
     [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

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=20061122221731.356939cb@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=info-linux@ldcmail.amd.com \
    --cc=jordan.crouse@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