From: olof@lixom•net (Olof Johansson)
To: David Brownell <david-b@pacbell•net>
Cc: linuxppc-dev@ozlabs•org, i2c@lm-sensors•org,
rtc-linux@googlegroups•com, James Chapman <jchapman@katalix•com>
Subject: Re: [patch/rft 4/4] rtc-ds1307 platform update, powerpc mpc834x_itx and mpc8313_rdb
Date: Mon, 14 May 2007 14:30:12 -0500 [thread overview]
Message-ID: <20070514193012.GA1693@lixom.net> (raw)
In-Reply-To: <200705141137.39961.david-b@pacbell.net>
On Mon, May 14, 2007 at 11:37:39AM -0700, David Brownell wrote:
> 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).
Sounds good.
> > > 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.
Ah yes, good point.
> > (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. ;)
Yep, I asked on IRC and got a similar answer. I had forgotten about them.
> 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.
Which is why I said "long term", as in "after this is done". :)
-Olof
prev parent reply other threads:[~2007-05-14 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 16:46 [patch/rft 4/4] rtc-ds1307 platform update, powerpc mpc834x_itx and mpc8313_rdb David Brownell
2007-05-14 17:44 ` Grant Likely
2007-05-14 18:25 ` David Brownell
2007-05-14 18:49 ` David Brownell
2007-05-14 19:02 ` Grant Likely
2007-05-15 13:24 ` [i2c] " Jean Delvare
2007-05-14 18:05 ` Olof Johansson
2007-05-14 18:37 ` David Brownell
2007-05-14 18:52 ` [rtc-linux] " Alessandro Zummo
2007-05-14 19:30 ` Olof Johansson [this message]
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=20070514193012.GA1693@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=david-b@pacbell$(echo .)net \
--cc=i2c@lm-sensors$(echo .)org \
--cc=jchapman@katalix$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=rtc-linux@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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