From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp109.sbc.mail.re2.yahoo.com (smtp109.sbc.mail.re2.yahoo.com [68.142.229.96]) by ozlabs.org (Postfix) with SMTP id 655A8DDEED for ; Thu, 22 Mar 2007 09:07:52 +1100 (EST) From: David Brownell To: Guennadi Liakhovetski Subject: Re: [PATCH 1/5] powerpc: generic time suspend/resume code Date: Wed, 21 Mar 2007 13:47:49 -0700 References: <20070319105352.771599000@sipsolutions.net> <1174315651.5044.4.camel@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <200703211347.50221.david-b@pacbell.net> Cc: Johannes Berg , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Monday 19 March 2007 2:51 pm, Guennadi Liakhovetski wrote: > David, what's the status of that your patch? Those RTC framework changes are now in the MM tree, and I expect they will merge soon after the 2.6.22 merge window opens. One related topic to consider: the I2C stack is also getting updated to (finally!!) leverage about the driver model. If those changes aren't in the MM tree yet, they will be soonish. This means that the RTCs based on I2C will be converted to use a different config scheme(*) ... and that board init code will need updates to support it. Boards using RTCs that hook up without I2C could convert to the generic RTC framework at any time after those RTC core changes merge. But when I2C is involved, some other conversions will be in the mix too. Me, I have no idea what PPC platforms combine PM, RTC, and I2C. :) - Dave (*) Most of the I2C based RTCs rely on kernel command line parameters, because of the vagaries of I2C. "New style" I2C drivers will replace command line declarations ("rv5c386 RTC on bus 0 at address 0x32") with ones in the board specific init logic.