public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Bigga <ab@mycable.de>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: david-b@pacbell.net, mgreer@mvista.com, a.zummo@towertech.it,
	linux-kernel@vger.kernel.org
Subject: Re: RTC: add RTC class interface to m41t00 driver
Date: Mon, 7 Aug 2006 16:55:50 +0200	[thread overview]
Message-ID: <200608071655.50946.ab@mycable.de> (raw)
In-Reply-To: <20060807.020919.15248103.anemo@mba.ocn.ne.jp>

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@mycable.de


  reply	other threads:[~2006-08-07 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  2:33 RTC: add RTC class interface to m41t00 driver David Brownell
2006-08-05 16:29 ` Atsushi Nemoto
2006-08-05 17:43   ` Alexander Bigga
2006-08-05 20:23     ` David Brownell
2006-08-07 15:01       ` Alexander Bigga
2006-08-05 19:13   ` David Brownell
2006-08-06 17:09     ` Atsushi Nemoto
2006-08-07 14:55       ` Alexander Bigga [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 15:21 Atsushi Nemoto
2006-08-03 15:42 ` Atsushi Nemoto
2006-08-04  0:21   ` Mark A. Greer
2006-08-04 14:01     ` Alexander Bigga
2006-08-04 16:03       ` Atsushi Nemoto
2006-08-04 22:57       ` Andrew Morton
2006-08-05 13:28         ` Atsushi Nemoto

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=200608071655.50946.ab@mycable.de \
    --to=ab@mycable.de \
    --cc=a.zummo@towertech.it \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgreer@mvista.com \
    /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