From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp109.sbc.mail.mud.yahoo.com (smtp109.sbc.mail.mud.yahoo.com [68.142.198.208]) by ozlabs.org (Postfix) with SMTP id 1BCF5DDE1A for ; Tue, 15 May 2007 04:37:43 +1000 (EST) From: David Brownell To: Olof Johansson Subject: Re: [patch/rft 4/4] rtc-ds1307 platform update, powerpc mpc834x_itx and mpc8313_rdb Date: Mon, 14 May 2007 11:37:39 -0700 References: <200705140946.41993.david-b@pacbell.net> <20070514180545.GA1437@lixom.net> In-Reply-To: <20070514180545.GA1437@lixom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <200705141137.39961.david-b@pacbell.net> Cc: linuxppc-dev@ozlabs.org, i2c@lm-sensors.org, rtc-linux@googlegroups.com, James Chapman List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Monday 14 May 2007, Olof Johansson wrote: > On Mon, May 14, 2007 at 09:46:41AM -0700, David Brownell wrote: > > Didn't update the pasemi reference board; public info doesn't say > > which chip it uses. > > ds1338. OK. The relevant updates should be evident from this patch. Mr Grep tells me that if those powerpc platforms update along with csb337, all current rtc-ds1307 users will be upgraded. Then there's a separate issue of removing the old SENSORS_DS1337 driver. Simpler IMO for those drivers to have one transition, to new-style rtc-ds1307, not two (to old-style, then new-style). > > NOTE: cc'd the relevant powerpc maintainers lists; patches 1-3 > > will be archived in the rtc and i2c lists. I'd like to see these > > get tested/fixed so that the rtc-ds1307 driver can switch completely > > to use the new-style I2c driver model. > > Specific URLs can sometimes be useful, so we don't have to go digging > through the archives. But thanks for the heads up, I'll make the > corresponding changes to my code and test it out. The URLS don't exist until after the email's gotten to the list servers ... sort of a chicken/egg issue. > (I'm guessing long-term, we will want to pull the chip info out of the > device tree instad of have it in a table in the board code, but that's > extra credit at the moment.) For some definition of "long term". ISTR seeing patches from Scott Wood doing exactly that ... on the I2C list last November or so. ;) Right now my concern is how to migrate the rtc-ds1307 driver. I'd prefer to avoid needing to have a period where the legacy mode must co-exist with the new-style driver support, or needing to entangle with such tree conversions. - Dave