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: Sat, 05 Aug 2006 19:43:12 +0200 [thread overview]
Message-ID: <44D4D8B0.5010103@mycable.de> (raw)
In-Reply-To: <20060806.012924.96685417.anemo@mba.ocn.ne.jp>
Hi Atsushi,
Hi David,
I've seen very late that the rtc-ds1307.c driver supports the quite
simple m41t00 as well. As Mark's m41t00.c claimed to support even the
m41t81 and the m41st85, I startet at this point.
First, I sent my approach to Mark (m41t00.c), Alessandro (rtc-subsytem)
and Jean (i2c-subsystem) to discuss the strategy. And if I understood
them right, they found the idea good, to move the i2c/chips/m41t00.h to
an rtc/rtc-m41txx.c driver, as this should be the general place for such
rtc-drivers.
As Atsushi has done almost the same work, I postet my version on friday
to pretend the next person to do this job and to start the discussion,
how to get to a suitable version for all - including Mark with his
arch/ppc/platforms/katana.c boards.
I confirm, that the rtc-ds1307.c driver works with m41t00. But the
m41t8x or m41st8x differs a lot from the m41t00 (HT bit, ST bit, SQW
freq - like Atsushi wrote it already).
Atsushi Nemoto wrote:
> 2. As m41t00_chip_info_tbl[] in m41t00 driver shows, M41T81 and M41T85
> have different register layout.
>
The register layout seems to depend on the watchdog and alarm
functionality.
The features differs from chip to chip, that's why I intodruced a
"features"-field in struct m41txx_chip_info.
> 3. It lacks some features (ST bit, HT bit, SQW freq.) in m41t00
> driver, though I personally does not need these features.
>
You need at least to clear the Stop Bit (ST) and the Halt Update Bit
(HT) unless your m41t8x will always report the time of the last power
fail and not the current time.
For me there is still the open question, if the workqueue-part and the
exported symbols (m41t00_get_rtc_time, ) should stay or not. I don't
need it and Atsushi seems to share my opinion. But...?
On monday, I can continue work on it.
Alexander
--
Alexander Bigga Tel: +49 4873 90 10 866
mycable GmbH Fax: +49 4873 90 19 76
Boeker Stieg 43
D-24613 Aukrug eMail: ab@mycable.de
next prev parent reply other threads:[~2006-08-05 17:43 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 [this message]
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
-- 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=44D4D8B0.5010103@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