Re: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

On Wed, Nov 25, 2015 at 6:25 AM, Thomas Gleixner wrote: > On Fri, 20 Nov 2015, John Stultz wrote: > >> On Tue, Nov 17, 2015 at 4:08 AM, wrote: >> > From: zhuo-hao >> > >> > Before the system go to suspend (S3), if user create a timer with clockid >> > CLOCK_REALTIME_ALARM/CLOCK_BOOTTIME_ALARM a

Re: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

On Fri, 20 Nov 2015, John Stultz wrote: > On Tue, Nov 17, 2015 at 4:08 AM, wrote: > > From: zhuo-hao > > > > Before the system go to suspend (S3), if user create a timer with clockid > > CLOCK_REALTIME_ALARM/CLOCK_BOOTTIME_ALARM and set a "large" timeout value > > to this timer. The function al

RE: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

>Although from the earlier discussion it still isn't quite clear to me: >Why must the HPET RTC emulation need to fire the alarm every 16ms? Is that not >something that can be fixed? This is hpet driver's behavior. Please check the following comment which is copied from the file hpet.c /* HPET i

Re: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

On Tue, Nov 17, 2015 at 4:08 AM, wrote: > From: zhuo-hao > > Before the system go to suspend (S3), if user create a timer with clockid > CLOCK_REALTIME_ALARM/CLOCK_BOOTTIME_ALARM and set a "large" timeout value > to this timer. The function alarmtimer_suspend will be called to setup > a timeout

[PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

From: zhuo-hao Before the system go to suspend (S3), if user create a timer with clockid CLOCK_REALTIME_ALARM/CLOCK_BOOTTIME_ALARM and set a "large" timeout value to this timer. The function alarmtimer_suspend will be called to setup a timeout value to RTC timer to avoid the system sleep over tim