On Saturday 06 January 2007 3:35 am, Zhang Rui wrote:
>
> Create /sys/power/alarm.
Urg. This doesn't work with the RTC framework, which accepts the reality
that some systems have multiple RTCs ... /sys/class/rtc/rtcN/alarm is a
much more appropriate location for that RTC's alarm.
(How to handle RTCs with multiple alarms is a different issue; I'm just
assuming for now that one of them wil be designated primary.)
> The way it works is exactly the same as /proc/acpi/alarm.
> I.e. "#echo yyyy-mm-dd hh-mm-ss >/sys/power/alarm" supports existing absolute
> time.
> And "#echo +yyyy-mm-dd hh-mm-ss >/sys/power/alarm" supports a duration.
There was a proposal a while back to have /sys/class/rtc/rtcN/alarm
files -- for alarm-capable RTCs, they don't all have alarms -- have
only the absolute seconds. "date" can do the math for you; e.g.
# cd /sys/class/rtc/rtcN
# date -d '5pm tuesday' "+%s" > alarm
# date -d '5 hours 24 minutes 11 seconds' "+%s" > alarm
# date -d '4pm 8 january 2007' "+%s" > alarm
It's usually felt to be a Good Thing if the kernel doesn't have to be
in the business of parsing and validating complex input ...
(And "cat" of the alarm attribute would return either seconds since
the POSIX epoch, if the alarm's active, else the null string.)
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
