diff options
author | John Stultz <john.stultz@linaro.org> | 2011-06-16 18:47:37 -0700 |
---|---|---|
committer | John Stultz <john.stultz@linaro.org> | 2011-06-21 16:32:28 -0700 |
commit | 1c6b39ad3f01514fd8dd84b5b412bafb75c19388 (patch) | |
tree | bd31cf5d3e67acc9ef23c97ddd92c961b73f40c7 /lib/libcrc32c.c | |
parent | c008ba58af24dc5d0d8e9fe6e59d876910254761 (diff) | |
download | kernel_samsung_smdk4412-1c6b39ad3f01514fd8dd84b5b412bafb75c19388.zip kernel_samsung_smdk4412-1c6b39ad3f01514fd8dd84b5b412bafb75c19388.tar.gz kernel_samsung_smdk4412-1c6b39ad3f01514fd8dd84b5b412bafb75c19388.tar.bz2 |
alarmtimers: Return -ENOTSUPP if no RTC device is present
Toralf Förster and Richard Weinberger noted that if there is
no RTC device, the alarm timers core prints out an annoying
"ALARM timers will not wake from suspend" message.
This warning has been removed in a previous patch, however
the issue still remains: The original idea was to support
alarm timers even if there was no rtc device, as long as the
system didn't go into suspend.
However, after further consideration, communicating to the application
that alarmtimers are not fully functional seems like the better
solution.
So this patch makes it so we return -ENOTSUPP to any posix _ALARM
clockid calls if there is no backing RTC device on the system.
Further this changes the behavior where when there is no rtc device
we will check for one on clock_getres, clock_gettime, timer_create,
and timer_nsleep instead of on suspend.
CC: Toralf Förster <toralf.foerster@gmx.de>
CC: Richard Weinberger <richard@nod.at
CC: Peter Zijlstra <peterz@infradead.org>
CC: Thomas Gleixner <tglx@linutronix.de>
Reported-by: Toralf Förster <toralf.foerster@gmx.de>
Reported by: Richard Weinberger <richard@nod.at>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'lib/libcrc32c.c')
0 files changed, 0 insertions, 0 deletions