From: David Gibson <david@gibson.dropbear.id.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org,
Alessandro Zummo <alessandro.zummo@towertech.it>,
rtc-linux@googlegroups.com
Subject: Re: rtc-ppc
Date: Thu, 6 Nov 2008 10:08:25 +1100 [thread overview]
Message-ID: <20081105230825.GA28465@yookeroo.seuss> (raw)
In-Reply-To: <1225923526.3882.3.camel@macbook.infradead.org>
On Wed, Nov 05, 2008 at 11:18:46PM +0100, David Woodhouse wrote:
> On Wed, 2008-11-05 at 02:19 +0100, Alessandro Zummo wrote:
> > I was checking a few drivers for compliance and noticed that
> > the rtc-ppc driver registers a platform device instead of
> > a platform driver.
> >
> > Wouldn't be possible to have the ppc arch doing the device
> > thing and cleanup the driver?
>
> It would be possible, yes -- but it would be better to have the various
> PPC platforms just register RTC-class devices _directly_, and ditch the
> RTC bits from ppc_md altogether.
>
> I think we're waiting until the RTC class works with NTP before we can
> contemplate that, though.
Yeah, I tried writing some ppc_md hooks which backended onto the rtc
class drivers as an interim measure, but the hooks are called from
places the rtc class stuff can't safely be called (too early, IIRC,
but it's a while since I checked).
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-11-05 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081105021901.49dffc3e@i1501.lan.towertech.it>
2008-11-05 22:18 ` rtc-ppc David Woodhouse
2008-11-05 22:59 ` rtc-ppc Alessandro Zummo
2008-11-05 23:08 ` David Gibson [this message]
2008-11-05 23:14 ` [rtc-linux] rtc-ppc Alessandro Zummo
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=20081105230825.GA28465@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=alessandro.zummo@towertech.it \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rtc-linux@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.