From: Tom Rini <trini@kernel.crashing.org>
To: 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 15:40:07 -0700 [thread overview]
Message-ID: <20040429224007.GA15265@smtp.west.cox.net> (raw)
In-Reply-To: <20040429135408.G16407@flint.arm.linux.org.uk>
On Thu, Apr 29, 2004 at 01:54:08PM +0100, Russell King wrote:
> On Thu, Apr 29, 2004 at 01:41:23PM +0100, Ian Campbell wrote:
> > Hi Stefan,
> >
> > > This driver only does the low-level I2C stuff, the rtc misc device
> > > driver is a separate driver module which I will send a patch for soon.
> >
> > I have a patch (attached, it could do with cleaning up) for the Dallas
> > DS1307 I2C RTC which I ported from the 2.4 rmk patch, originally written
> > by Intrinsyc. Currently it includes both the I2C and the RTC bits in the
> > same driver.
>
> Have a look at drivers/acorn/char/{i2c,pcf8583}.[ch]
>
> > Do you think it is realistic/possible to have the same generic RTC
> > driver speak to multiple I2C devices, from what I can see in your driver
> > the two chips seem pretty similar and the differences could probably be
> > abstracted away. Perhaps that is your intention from the start?
> >
> > I guess I will wait until you post the RTC misc driver and try and make
> > the DS1307 one work with that before I submit it.
>
> If you look at the last 2.6-rmk patch, you'll notice that it contains
> an abstracted RTC driver - I got peed off with writing the same code
> to support the user interfaces to the variety of RTCs over and over
> again. (Ones which are simple 32-bit second counters with alarms
> through to ones which return D/M/Y H:M:S.C format.)
A generic one for i2c rtcs or another generic rtc driver? There's
already drivers/char/genrtc.c...
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-04-29 22:40 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 [this message]
2004-04-29 22:49 ` Russell King
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=20040429224007.GA15265@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=icampbell@arcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.eletzhofer@eletztrick.de \
/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