linux-kernel - Re: RTC: add RTC class interface to m41t00 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060806.012924.96685417.anemo@mba.ocn.ne.jp>
Date:	Sun, 06 Aug 2006 01:29:24 +0900 (JST)
From:	Atsushi Nemoto <anemo@....ocn.ne.jp>
To:	david-b@...bell.net
Cc:	ab@...able.de, mgreer@...sta.com, a.zummo@...ertech.it,
	linux-kernel@...r.kernel.org
Subject: Re: RTC: add RTC class interface to m41t00 driver

On Fri, 4 Aug 2006 19:33:39 -0700, David Brownell <david-b@...bell.net> wrote:
> Actually, it'd be worth trying drivers/rtc/rtc-ds1307.c ... the M41T00 is
> one of a family of mostly-compatible RTC chips, and the ds1307 driver
> should be pretty much the least-common-denominator there.  They all use
> the same I2C address, and the same register layout for the calendar/time
> function.
> 
> I'd expect rtc-ds1307 to handle the m41t00 already, or with at most minor
> tweaks to recognize whatever's different.  It should already be ignoring
> the bits in the clock/calendar registers that vary, as well as the SRAM
> and (for some other chips) the alarm.  (Not that I2C has ways to tell us
> what IRQ the alarm would use, but that's a different tale!)

Thanks for your suggestion.  I have looked rtc-ds1307 too before I
tried to modify m41t00 driver.

It seems some works are still needed to support M41Txx chips by the
driver.

1. The driver contains ds_1340 (or st m41t00) definition, but it seems
   no way to select the ds_type.

2. As m41t00_chip_info_tbl[] in m41t00 driver shows, M41T81 and M41T85
   have different register layout.

3. It lacks some features (ST bit, HT bit, SQW freq.) in m41t00
   driver, though I personally does not need these features.

I choose changing m41t00 driver by (1) and (2).

If we really need a super generic driver, I suppose adding ds13xx
support to new m41txx driver is less hard.  I think having separate
drivers are good enough for now.

---
Atsushi Nemoto
-
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/