On Wednesday 28 March 2007 2:27 pm, Maxim wrote: > On Wednesday 28 March 2007 22:59:26 David Brownell wrote: > When HPET is active it eats RTC IRQ, Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode". In the more sensible "Standard Mode", they have their own IRQs. > So the only way out is to emulate RTC using HPET, > It is done this way in old rtc driver, rtc-cmos should do the same. No. Patches like http://marc.info/?l=linux-kernel&m=117219531503973&w=2 should be merged (I hope they're in the 2.6.22 queue!), making HPET run in "Standard Mode" so that HPET can stop sticking its fingers in code where they don't belong. > I am also planning to add support of HPET and suspend/resume > for rtc-cmos, but I didn't start this yet. It's already got suspend/resume support, and in the 2.6.22 queue are RTC framework updates which will let the RTC framework replace a lot more platform-specific RTC support. (Platform changes can come later, where they're needed. ARM for example doesn't need any.) Once HPET stops using "Legacy Replacement Mode" you won't need to touch anything in the RTC stack (except maybe the legacy char/rtc.c driver, removing HPET stuff). The open issue with suspend/resume support in rtc-cmos relates to how ACPI wakeup alarms should trigger. I've not made time to test those patches. - Dave - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
