[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200608071655.50946.ab@mycable.de>
Date: Mon, 7 Aug 2006 16:55:50 +0200
From: Alexander Bigga <ab@...able.de>
To: Atsushi Nemoto <anemo@....ocn.ne.jp>
Cc: david-b@...bell.net, mgreer@...sta.com, a.zummo@...ertech.it,
linux-kernel@...r.kernel.org
Subject: Re: RTC: add RTC class interface to m41t00 driver
On Sunday 06 August 2006 19:09, Atsushi Nemoto wrote:
> > It would have made more sense to me to have the M41T81 and M41T85 be
> > in a different driver, because of the incompatible register layout.
> > That's the more traditional approach.
>
> Now I'm thinking this way. Still thinking...
Yes, but on the other side: except of this single shift in the registers, it
works in the m41txx (or what the name will be) and won't do any extra work to
the driver.
Even the m41t80 and m41t81 differs in their features. So you always have to
distinguish inside the driver.
> My real target is M41T80, which seems a subset of M41T81.
> (Sorry for not writing this before.)
My target is a M41ST85.
> So the next theme would be how we support M41T8x chips. I think
> Alexander's rtc-m41txx is good candidate for them.
There are also M41st9x chips and M41t6x chips and a M41t11... But ok, most
difference is watchdog/alarm or not.
> Then M41T00 users can choose rtc-ds1307 or rtc-m41t00. Not so bad, I
> think.
As long, as the user will be pointed out this possibilties in the Kconfig - I
agree.
Alexander
--
Alexander Bigga Tel: +49 4873 90 10 866
mycable GmbH Fax: +49 4873 901 976
Boeker Stieg 43
D-24613 Aukrug eMail: ab@...able.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists