lkml.org 
[lkml]   [2011]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [rtc-linux] [PATCH 04/10] RTC: Cleanup rtc_class_ops->read_alarm()
On Tue, Feb 22, 2011 at 12:09:38AM -0800, john stultz wrote:

> Just so I can better get a grip of the cases your considering, could you
> maybe give me some more detailed examples of where you'd like to see the
> alarm timer be set and then persist across multiple power cycles before
> firing? And how is that persistent value managed by the application
> setting it?

The WM83xx RTCs can do this (the alarm can be used to initiate a boot)
and I'd expect many embedded RTC controllers can do similar. The
application would manage this by owning the RTC in the system, usually
with a configuration saying something like "boot every day at 7am" or
something.

Having thought about this a bit I'm thinking that this sort of alarm
handling is probably something I'd expect to see handled in userspace.
I can see us providing a virtual RTC driver that can generate alarms
when there's no actual RTC hardware but adding additional functionality
on top of the hardware feels like an application issue.


\
 
 \ /
  Last update: 2011-02-22 19:19    [W:1.229 / U:0.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site