public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Ian Campbell <icampbell@arcom.com>,
	stefan.eletzhofer@eletztrick.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] 2.6 I2C epson 8564 RTC chip
Date: Thu, 29 Apr 2004 23:49:45 +0100	[thread overview]
Message-ID: <20040429234945.M16407@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040429224007.GA15265@smtp.west.cox.net>; from trini@kernel.crashing.org on Thu, Apr 29, 2004 at 03:40:07PM -0700

On Thu, Apr 29, 2004 at 03:40:07PM -0700, Tom Rini wrote:
> A generic one for i2c rtcs or another generic rtc driver?  There's
> already drivers/char/genrtc.c...

genrtc.c lacks several features ARM needs, the big one being wakeup
timers.  It also only provides either (configurable) emulation or no
support of various RTC features, rather than allowing a real RTC to
provide them if it can - and you need to know the details of your RTC
at kernel configuration time.

It provides no support for translating "RTC" time into seconds and
vice versa which is needed for second-counter based RTCs found in
PXA, StrongARM, and other ARM SoC platforms.

IOW, its fairly restrictive in what it provides and what it allows
architectures to provide.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-04-29 22:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 12:02 [PATCH] 2.6 I2C epson 8564 RTC chip stefan.eletzhofer
2004-04-29 12:41 ` Ian Campbell
2004-04-29 12:54   ` Russell King
2004-04-29 13:58     ` stefan.eletzhofer
2004-04-29 14:14       ` Ian Campbell
2004-04-29 14:28         ` stefan.eletzhofer
2004-04-29 22:40     ` Tom Rini
2004-04-29 22:49       ` Russell King [this message]
2004-04-29 22:52         ` Tom Rini
2004-04-29 23:07           ` Russell King
2004-04-29 12:59 ` Ian Campbell
2004-04-29 13:55   ` stefan.eletzhofer
2004-05-01  5:48 ` Greg KH
2004-05-01  9:26   ` stefan.eletzhofer
2004-05-02  5:51     ` Greg KH

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=20040429234945.M16407@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=icampbell@arcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan.eletzhofer@eletztrick.de \
    --cc=trini@kernel.crashing.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