[PATCH 0/7] share sa1100 rtc driver to arch-mmp

Haojian Zhuang haojian.zhuang at gmail.com
Thu Feb 23 05:22:23 EST 2012


On Thu, Feb 23, 2012 at 6:00 PM, Russell King - ARM Linux
<linux at arm.linux.org.uk> wrote:
> On Thu, Feb 23, 2012 at 05:45:20PM +0800, Haojian Zhuang wrote:
>> On Thu, Feb 23, 2012 at 4:52 PM, Robert Jarzmik <robert.jarzmik at free.fr> wrote:
>> > The behaviour should be as before, the config should be able to choose between
>> > rtc-pxa and rtc-sa1100 for a pxa27x based board. For sharpsl_pm, I suppose the
>> > rtc-sa1100 will be chosen in the .config, and for mioa701, it will be
>> > rtc-pxa.
>> >
>> > Just to clear, I'm against removing "resources, clock" from pxa27x platform code
>> > which would break rtc-pxa driver on pxa27x. Now I don't care if you're talking
>> > about changing some "defconfigs".
>> >
>>
>> How about to move the rtc-sa1100 or rtc-pxa device register from
>> pxa27x.c to board file? Then we'll be both happy.
>
> How about stopping thinking about "one or other" and start thinking "both" ?
> The RTC library can and does cope with more than one RTC, and each RTC is
> exposed uniquely to userspace.  So there shouldn't be any problem in keeping
> both around, or even registering both together.
>
> You just have to make sure you don't use both of them together as their
> open functions will want to claim the same IRQ.  That's not really a
> problem because that should provide exclusivity between the two.

Resource is bind with platform device. We'll meet resource conflict if
we register them both.

Thanks
Haojian



More information about the linux-arm-kernel mailing list