* at91sam9g45 real RTC support
@ 2010-06-03 9:44 Yegor Yefremov
0 siblings, 0 replies; only message in thread
From: Yegor Yefremov @ 2010-06-03 9:44 UTC (permalink / raw)
To: linux-arm-kernel
As far as I understand RTC support for at91sam9g45 is realized via RTT and GPBR, where base time offset is stored. But the board has real RTC with common RTC registers as stated in the documentation. Why is it not supported directly? Is hardware broken?
The other issue is this code part
/* --------------------------------------------------------------------
* RTC
* -------------------------------------------------------------------- */
#if defined(CONFIG_RTC_DRV_AT91RM9200) || defined(CONFIG_RTC_DRV_AT91RM9200_MODULE)
static struct platform_device at91sam9g45_rtc_device = {
.name = "at91_rtc",
.id = -1,
.num_resources = 0,
};
static void __init at91_add_device_rtc(void)
{
platform_device_register(&at91sam9g45_rtc_device);
}
#else
static void __init at91_add_device_rtc(void) {}
#endif
I've tweaked the driver/rtc/Kconfig and could then select the AT91RM9200 RTC driver. I could successfully compile the kernel and the RTC has completed the quick test: hwclock --systohc, poweroff, poweron hwclock. The time was correct.
So what is advantage of the RTT based solution? And why AT91RM9200 RTC driver is not made selectable?
Best regards,
Yegor
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-06-03 9:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-03 9:44 at91sam9g45 real RTC support Yegor Yefremov
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.