This is just a walkaround for deeper sleep testing. Yes, a better solution is to create the RTC in a user testing application.
Sonic -----Original Message----- From: Mike Frysinger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 22, 2008 5:09 PM To: Zhang, Sonic Cc: Hennerich, Michael; [EMAIL PROTECTED]; [email protected] Subject: Re: [Linux-kernel-commits] [4111] trunk: Fix bug[#3820] Only RTC interrupt can wake up deeper sleep core. On Jan 22, 2008 1:35 AM, Zhang, Sonic <[EMAIL PROTECTED]> wrote: > It is not safe to use rtc without reset. But, maybe still works. i think the current code in there will just be completely tossed once Michael implements the irq wakeup pieces. if you want to talk about problems with the code as it is now though ... how is the rtc not usable without reset ? all of the RTC registers (except for RTC_ISTAT) are externally powered, so their state is maintained automatically. there is no need to save/restore them. upon resume, the RTC_ISTAT register should get cleared completely. why is SWCNT forced to 10 and forced on ? both of those should be determined by the user. if the user wants to wake up from sleep using the RTC event, then they would open the RTC, use one of the RTC_XXX_ON ioctls, and then put the board to sleep. -mike _______________________________________________ Linux-kernel-commits mailing list [email protected] http://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
