On Sun, Jun 17, 2012 at 11:23 AM, Steven King <sfk...@fdwdc.com> wrote:
> On Sunday 17 June 2012 2:09:51 am Geert Uytterhoeven wrote:
>> On Sun, Jun 17, 2012 at 9:50 AM, Steven King <sfk...@fdwdc.com> wrote:
>> > +config RTC_DRV_M5441x
>> > + tristate "Freescale Coldfire M5441x RTC support"
>> > + depends on M5441x
>> > + help
>> > + This enables support for the RTC on the Freescale Coldfire
>> > 5441x + (54410/54415/54416/54417/54418).
>> > +
>> > + This driver can also be built as a module. If so, the module
>> > + will be called rtc-m5441x.
>>
>> But the platform device is called differently:
>> > +static struct platform_driver m5441x_rtc_driver = {
>> > + .driver.name = "mcfrtc",
>> > + .driver.owner = THIS_MODULE,
>> > + .remove = __devexit_p(m5441x_rtc_remove),
>> > +};
>>
>> Is there a specific reason for that?
>
> You mean the "mcfrtc" bit? Thats the same as what we do for all of the other
That's what I meant.
> Coldfire peripherals, ie "mcfqspi", "mcfuart", etc.
So why not call the driver mcf-rtc?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
