2011-01-12 01:42:13 +08:00
|
|
|
/*
|
|
|
|
* Alarmtimer interface
|
|
|
|
*
|
|
|
|
* This interface provides a timer which is similarto hrtimers,
|
|
|
|
* but triggers a RTC alarm if the box is suspend.
|
|
|
|
*
|
|
|
|
* This interface is influenced by the Android RTC Alarm timer
|
|
|
|
* interface.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2010 IBM Corperation
|
|
|
|
*
|
|
|
|
* Author: John Stultz <john.stultz@linaro.org>
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
#include <linux/time.h>
|
|
|
|
#include <linux/hrtimer.h>
|
|
|
|
#include <linux/timerqueue.h>
|
|
|
|
#include <linux/rtc.h>
|
2017-02-03 02:15:33 +08:00
|
|
|
#include <linux/sched/signal.h>
|
2017-02-09 01:51:35 +08:00
|
|
|
#include <linux/sched/debug.h>
|
2011-01-12 01:42:13 +08:00
|
|
|
#include <linux/alarmtimer.h>
|
|
|
|
#include <linux/mutex.h>
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <linux/posix-timers.h>
|
|
|
|
#include <linux/workqueue.h>
|
|
|
|
#include <linux/freezer.h>
|
2017-06-07 16:42:31 +08:00
|
|
|
#include <linux/compat.h>
|
2017-08-21 06:01:46 +08:00
|
|
|
#include <linux/module.h>
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2017-05-31 05:15:41 +08:00
|
|
|
#include "posix-timers.h"
|
|
|
|
|
2016-11-29 06:35:21 +08:00
|
|
|
#define CREATE_TRACE_POINTS
|
|
|
|
#include <trace/events/alarmtimer.h>
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
|
|
|
* struct alarm_base - Alarm timer bases
|
|
|
|
* @lock: Lock for syncrhonized access to the base
|
|
|
|
* @timerqueue: Timerqueue head managing the list of events
|
|
|
|
* @gettime: Function to read the time correlating to the base
|
|
|
|
* @base_clockid: clockid for the base
|
|
|
|
*/
|
2011-01-12 01:42:13 +08:00
|
|
|
static struct alarm_base {
|
|
|
|
spinlock_t lock;
|
|
|
|
struct timerqueue_head timerqueue;
|
|
|
|
ktime_t (*gettime)(void);
|
|
|
|
clockid_t base_clockid;
|
|
|
|
} alarm_bases[ALARM_NUMTYPE];
|
|
|
|
|
2017-05-27 18:23:47 +08:00
|
|
|
#if defined(CONFIG_POSIX_TIMERS) || defined(CONFIG_RTC_CLASS)
|
2016-11-29 06:35:21 +08:00
|
|
|
/* freezer information to handle clock_nanosleep triggered wakeups */
|
|
|
|
static enum alarmtimer_type freezer_alarmtype;
|
|
|
|
static ktime_t freezer_expires;
|
2011-06-17 09:27:09 +08:00
|
|
|
static ktime_t freezer_delta;
|
|
|
|
static DEFINE_SPINLOCK(freezer_delta_lock);
|
2017-05-27 18:23:47 +08:00
|
|
|
#endif
|
2011-06-17 09:27:09 +08:00
|
|
|
|
2017-07-05 20:08:35 +08:00
|
|
|
#ifdef CONFIG_RTC_CLASS
|
2012-08-09 15:37:27 +08:00
|
|
|
static struct wakeup_source *ws;
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/* rtc timer and device for setting alarm wakeups at suspend */
|
2012-03-24 19:46:23 +08:00
|
|
|
static struct rtc_timer rtctimer;
|
2011-01-12 01:42:13 +08:00
|
|
|
static struct rtc_device *rtcdev;
|
2011-06-17 09:27:09 +08:00
|
|
|
static DEFINE_SPINLOCK(rtcdev_lock);
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2011-06-17 09:27:09 +08:00
|
|
|
/**
|
|
|
|
* alarmtimer_get_rtcdev - Return selected rtcdevice
|
|
|
|
*
|
|
|
|
* This function returns the rtc device to use for wakealarms.
|
|
|
|
* If one has not already been chosen, it checks to see if a
|
|
|
|
* functional rtc device is available.
|
|
|
|
*/
|
2012-04-21 03:31:45 +08:00
|
|
|
struct rtc_device *alarmtimer_get_rtcdev(void)
|
2011-06-17 09:27:09 +08:00
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_device *ret;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&rtcdev_lock, flags);
|
|
|
|
ret = rtcdev;
|
|
|
|
spin_unlock_irqrestore(&rtcdev_lock, flags);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
2014-06-13 14:19:42 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarmtimer_get_rtcdev);
|
2011-07-15 09:35:13 +08:00
|
|
|
|
|
|
|
static int alarmtimer_rtc_add_device(struct device *dev,
|
|
|
|
struct class_interface *class_intf)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_device *rtc = to_rtc_device(dev);
|
2017-07-05 20:08:35 +08:00
|
|
|
struct wakeup_source *__ws;
|
2011-07-15 09:35:13 +08:00
|
|
|
|
|
|
|
if (rtcdev)
|
|
|
|
return -EBUSY;
|
|
|
|
|
|
|
|
if (!rtc->ops->set_alarm)
|
|
|
|
return -1;
|
|
|
|
if (!device_may_wakeup(rtc->dev.parent))
|
|
|
|
return -1;
|
|
|
|
|
2017-07-05 20:08:35 +08:00
|
|
|
__ws = wakeup_source_register("alarmtimer");
|
|
|
|
|
2011-07-15 09:35:13 +08:00
|
|
|
spin_lock_irqsave(&rtcdev_lock, flags);
|
|
|
|
if (!rtcdev) {
|
2017-08-21 06:01:46 +08:00
|
|
|
if (!try_module_get(rtc->owner)) {
|
|
|
|
spin_unlock_irqrestore(&rtcdev_lock, flags);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2011-07-15 09:35:13 +08:00
|
|
|
rtcdev = rtc;
|
|
|
|
/* hold a reference so it doesn't go away */
|
|
|
|
get_device(dev);
|
2017-07-05 20:08:35 +08:00
|
|
|
ws = __ws;
|
|
|
|
__ws = NULL;
|
2011-07-15 09:35:13 +08:00
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&rtcdev_lock, flags);
|
2017-07-05 20:08:35 +08:00
|
|
|
|
|
|
|
wakeup_source_unregister(__ws);
|
|
|
|
|
2011-07-15 09:35:13 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-03-24 19:46:23 +08:00
|
|
|
static inline void alarmtimer_rtc_timer_init(void)
|
|
|
|
{
|
|
|
|
rtc_timer_init(&rtctimer, NULL, NULL);
|
|
|
|
}
|
|
|
|
|
2011-07-15 09:35:13 +08:00
|
|
|
static struct class_interface alarmtimer_rtc_interface = {
|
|
|
|
.add_dev = &alarmtimer_rtc_add_device,
|
|
|
|
};
|
|
|
|
|
2011-09-14 16:54:29 +08:00
|
|
|
static int alarmtimer_rtc_interface_setup(void)
|
2011-07-15 09:35:13 +08:00
|
|
|
{
|
|
|
|
alarmtimer_rtc_interface.class = rtc_class;
|
2011-09-14 16:54:29 +08:00
|
|
|
return class_interface_register(&alarmtimer_rtc_interface);
|
|
|
|
}
|
|
|
|
static void alarmtimer_rtc_interface_remove(void)
|
|
|
|
{
|
|
|
|
class_interface_unregister(&alarmtimer_rtc_interface);
|
2011-07-15 09:35:13 +08:00
|
|
|
}
|
2011-06-17 09:47:37 +08:00
|
|
|
#else
|
2012-04-21 03:31:45 +08:00
|
|
|
struct rtc_device *alarmtimer_get_rtcdev(void)
|
2011-09-14 16:54:29 +08:00
|
|
|
{
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
#define rtcdev (NULL)
|
|
|
|
static inline int alarmtimer_rtc_interface_setup(void) { return 0; }
|
|
|
|
static inline void alarmtimer_rtc_interface_remove(void) { }
|
2012-03-24 19:46:23 +08:00
|
|
|
static inline void alarmtimer_rtc_timer_init(void) { }
|
2011-06-17 09:27:09 +08:00
|
|
|
#endif
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2011-01-12 01:42:13 +08:00
|
|
|
* alarmtimer_enqueue - Adds an alarm timer to an alarm_base timerqueue
|
|
|
|
* @base: pointer to the base where the timer is being run
|
|
|
|
* @alarm: pointer to alarm being enqueued.
|
|
|
|
*
|
2012-09-14 07:12:16 +08:00
|
|
|
* Adds alarm to a alarm_base timerqueue
|
2011-01-12 01:42:13 +08:00
|
|
|
*
|
|
|
|
* Must hold base->lock when calling.
|
|
|
|
*/
|
|
|
|
static void alarmtimer_enqueue(struct alarm_base *base, struct alarm *alarm)
|
|
|
|
{
|
2012-09-14 07:12:16 +08:00
|
|
|
if (alarm->state & ALARMTIMER_STATE_ENQUEUED)
|
|
|
|
timerqueue_del(&base->timerqueue, &alarm->node);
|
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
timerqueue_add(&base->timerqueue, &alarm->node);
|
2011-08-11 03:30:21 +08:00
|
|
|
alarm->state |= ALARMTIMER_STATE_ENQUEUED;
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2012-09-14 07:25:22 +08:00
|
|
|
* alarmtimer_dequeue - Removes an alarm timer from an alarm_base timerqueue
|
2011-01-12 01:42:13 +08:00
|
|
|
* @base: pointer to the base where the timer is running
|
|
|
|
* @alarm: pointer to alarm being removed
|
|
|
|
*
|
2012-09-14 07:12:16 +08:00
|
|
|
* Removes alarm to a alarm_base timerqueue
|
2011-01-12 01:42:13 +08:00
|
|
|
*
|
|
|
|
* Must hold base->lock when calling.
|
|
|
|
*/
|
2012-09-14 07:25:22 +08:00
|
|
|
static void alarmtimer_dequeue(struct alarm_base *base, struct alarm *alarm)
|
2011-01-12 01:42:13 +08:00
|
|
|
{
|
2011-08-11 03:30:21 +08:00
|
|
|
if (!(alarm->state & ALARMTIMER_STATE_ENQUEUED))
|
|
|
|
return;
|
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
timerqueue_del(&base->timerqueue, &alarm->node);
|
2011-08-11 03:30:21 +08:00
|
|
|
alarm->state &= ~ALARMTIMER_STATE_ENQUEUED;
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
|
|
|
|
2011-04-29 04:29:18 +08:00
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2011-04-29 04:29:18 +08:00
|
|
|
* alarmtimer_fired - Handles alarm hrtimer being fired.
|
|
|
|
* @timer: pointer to hrtimer being run
|
2011-01-12 01:42:13 +08:00
|
|
|
*
|
2011-04-29 03:58:11 +08:00
|
|
|
* When a alarm timer fires, this runs through the timerqueue to
|
|
|
|
* see which alarms expired, and runs those. If there are more alarm
|
|
|
|
* timers queued for the future, we set the hrtimer to fire when
|
|
|
|
* when the next future alarm timer expires.
|
2011-01-12 01:42:13 +08:00
|
|
|
*/
|
2011-04-29 04:29:18 +08:00
|
|
|
static enum hrtimer_restart alarmtimer_fired(struct hrtimer *timer)
|
2011-01-12 01:42:13 +08:00
|
|
|
{
|
2012-09-14 07:12:16 +08:00
|
|
|
struct alarm *alarm = container_of(timer, struct alarm, timer);
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
2011-01-12 01:42:13 +08:00
|
|
|
unsigned long flags;
|
2011-04-29 04:29:18 +08:00
|
|
|
int ret = HRTIMER_NORESTART;
|
2011-08-11 02:08:07 +08:00
|
|
|
int restart = ALARMTIMER_NORESTART;
|
2011-01-12 01:42:13 +08:00
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
2012-09-14 07:25:22 +08:00
|
|
|
alarmtimer_dequeue(base, alarm);
|
2012-09-14 07:12:16 +08:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2011-08-11 02:08:07 +08:00
|
|
|
|
2012-09-14 07:12:16 +08:00
|
|
|
if (alarm->function)
|
|
|
|
restart = alarm->function(alarm, base->gettime());
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2012-09-14 07:12:16 +08:00
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
if (restart != ALARMTIMER_NORESTART) {
|
|
|
|
hrtimer_set_expires(&alarm->timer, alarm->node.expires);
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
2011-04-29 04:29:18 +08:00
|
|
|
ret = HRTIMER_RESTART;
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
|
2016-11-29 06:35:21 +08:00
|
|
|
trace_alarmtimer_fired(alarm, base->gettime());
|
2011-04-29 04:29:18 +08:00
|
|
|
return ret;
|
2011-01-12 01:42:13 +08:00
|
|
|
|
|
|
|
}
|
|
|
|
|
2013-05-16 05:38:11 +08:00
|
|
|
ktime_t alarm_expires_remaining(const struct alarm *alarm)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
return ktime_sub(alarm->node.expires, base->gettime());
|
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_expires_remaining);
|
2013-05-16 05:38:11 +08:00
|
|
|
|
2011-04-30 06:03:10 +08:00
|
|
|
#ifdef CONFIG_RTC_CLASS
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2011-01-12 01:42:13 +08:00
|
|
|
* alarmtimer_suspend - Suspend time callback
|
|
|
|
* @dev: unused
|
|
|
|
* @state: unused
|
|
|
|
*
|
|
|
|
* When we are going into suspend, we look through the bases
|
|
|
|
* to see which is the soonest timer to expire. We then
|
|
|
|
* set an rtc timer to fire that far into the future, which
|
|
|
|
* will wake us from suspend.
|
|
|
|
*/
|
|
|
|
static int alarmtimer_suspend(struct device *dev)
|
|
|
|
{
|
2016-11-29 06:35:21 +08:00
|
|
|
ktime_t min, now, expires;
|
|
|
|
int i, ret, type;
|
2011-06-17 09:27:09 +08:00
|
|
|
struct rtc_device *rtc;
|
2016-11-29 06:35:21 +08:00
|
|
|
unsigned long flags;
|
|
|
|
struct rtc_time tm;
|
2011-01-12 01:42:13 +08:00
|
|
|
|
|
|
|
spin_lock_irqsave(&freezer_delta_lock, flags);
|
|
|
|
min = freezer_delta;
|
2016-11-29 06:35:21 +08:00
|
|
|
expires = freezer_expires;
|
|
|
|
type = freezer_alarmtype;
|
2016-12-25 19:30:41 +08:00
|
|
|
freezer_delta = 0;
|
2011-01-12 01:42:13 +08:00
|
|
|
spin_unlock_irqrestore(&freezer_delta_lock, flags);
|
|
|
|
|
2011-07-15 09:35:13 +08:00
|
|
|
rtc = alarmtimer_get_rtcdev();
|
2011-01-12 01:42:13 +08:00
|
|
|
/* If we have no rtcdev, just return */
|
2011-06-17 09:27:09 +08:00
|
|
|
if (!rtc)
|
2011-01-12 01:42:13 +08:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Find the soonest timer to expire*/
|
|
|
|
for (i = 0; i < ALARM_NUMTYPE; i++) {
|
|
|
|
struct alarm_base *base = &alarm_bases[i];
|
|
|
|
struct timerqueue_node *next;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
next = timerqueue_getnext(&base->timerqueue);
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
if (!next)
|
|
|
|
continue;
|
|
|
|
delta = ktime_sub(next->expires, base->gettime());
|
2016-12-25 18:38:40 +08:00
|
|
|
if (!min || (delta < min)) {
|
2016-11-29 06:35:21 +08:00
|
|
|
expires = next->expires;
|
2011-01-12 01:42:13 +08:00
|
|
|
min = delta;
|
2016-11-29 06:35:21 +08:00
|
|
|
type = i;
|
|
|
|
}
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
2016-12-25 18:38:40 +08:00
|
|
|
if (min == 0)
|
2011-01-12 01:42:13 +08:00
|
|
|
return 0;
|
|
|
|
|
2012-08-09 15:37:27 +08:00
|
|
|
if (ktime_to_ns(min) < 2 * NSEC_PER_SEC) {
|
|
|
|
__pm_wakeup_event(ws, 2 * MSEC_PER_SEC);
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2016-11-29 06:35:21 +08:00
|
|
|
trace_alarmtimer_suspend(expires, type);
|
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
/* Setup an rtc timer to fire that far in the future */
|
2011-06-17 09:27:09 +08:00
|
|
|
rtc_timer_cancel(rtc, &rtctimer);
|
|
|
|
rtc_read_time(rtc, &tm);
|
2011-01-12 01:42:13 +08:00
|
|
|
now = rtc_tm_to_ktime(tm);
|
|
|
|
now = ktime_add(now, min);
|
|
|
|
|
2012-08-09 15:37:27 +08:00
|
|
|
/* Set alarm, if in the past reject suspend briefly to handle */
|
2016-12-25 19:30:41 +08:00
|
|
|
ret = rtc_timer_start(rtc, &rtctimer, now, 0);
|
2012-08-09 15:37:27 +08:00
|
|
|
if (ret < 0)
|
|
|
|
__pm_wakeup_event(ws, MSEC_PER_SEC);
|
|
|
|
return ret;
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
2015-11-17 20:08:07 +08:00
|
|
|
|
|
|
|
static int alarmtimer_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
struct rtc_device *rtc;
|
|
|
|
|
|
|
|
rtc = alarmtimer_get_rtcdev();
|
|
|
|
if (rtc)
|
|
|
|
rtc_timer_cancel(rtc, &rtctimer);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-04-30 06:03:10 +08:00
|
|
|
#else
|
|
|
|
static int alarmtimer_suspend(struct device *dev)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
2015-11-17 20:08:07 +08:00
|
|
|
|
|
|
|
static int alarmtimer_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
2011-04-30 06:03:10 +08:00
|
|
|
#endif
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2018-03-26 21:29:57 +08:00
|
|
|
static void
|
|
|
|
__alarm_init(struct alarm *alarm, enum alarmtimer_type type,
|
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
|
|
|
{
|
|
|
|
timerqueue_init(&alarm->node);
|
|
|
|
alarm->timer.function = alarmtimer_fired;
|
|
|
|
alarm->function = function;
|
|
|
|
alarm->type = type;
|
|
|
|
alarm->state = ALARMTIMER_STATE_INACTIVE;
|
|
|
|
}
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2011-01-12 01:42:13 +08:00
|
|
|
* alarm_init - Initialize an alarm structure
|
|
|
|
* @alarm: ptr to alarm to be initialized
|
|
|
|
* @type: the type of the alarm
|
|
|
|
* @function: callback that is run when the alarm fires
|
|
|
|
*/
|
|
|
|
void alarm_init(struct alarm *alarm, enum alarmtimer_type type,
|
2011-08-11 01:37:59 +08:00
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
2011-01-12 01:42:13 +08:00
|
|
|
{
|
2012-09-14 07:12:16 +08:00
|
|
|
hrtimer_init(&alarm->timer, alarm_bases[type].base_clockid,
|
2018-03-26 21:29:57 +08:00
|
|
|
HRTIMER_MODE_ABS);
|
|
|
|
__alarm_init(alarm, type, function);
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_init);
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2013-05-16 05:38:11 +08:00
|
|
|
* alarm_start - Sets an absolute alarm to fire
|
2011-01-12 01:42:13 +08:00
|
|
|
* @alarm: ptr to alarm to set
|
|
|
|
* @start: time to run the alarm
|
|
|
|
*/
|
2015-04-15 05:09:18 +08:00
|
|
|
void alarm_start(struct alarm *alarm, ktime_t start)
|
2011-01-12 01:42:13 +08:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
alarm->node.expires = start;
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
2015-04-15 05:09:18 +08:00
|
|
|
hrtimer_start(&alarm->timer, alarm->node.expires, HRTIMER_MODE_ABS);
|
2011-01-12 01:42:13 +08:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2016-11-29 06:35:21 +08:00
|
|
|
|
|
|
|
trace_alarmtimer_start(alarm, base->gettime());
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_start);
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2013-05-16 05:38:11 +08:00
|
|
|
/**
|
|
|
|
* alarm_start_relative - Sets a relative alarm to fire
|
|
|
|
* @alarm: ptr to alarm to set
|
|
|
|
* @start: time relative to now to run the alarm
|
|
|
|
*/
|
2015-04-15 05:09:18 +08:00
|
|
|
void alarm_start_relative(struct alarm *alarm, ktime_t start)
|
2013-05-16 05:38:11 +08:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
|
2017-05-31 05:15:34 +08:00
|
|
|
start = ktime_add_safe(start, base->gettime());
|
2015-04-15 05:09:18 +08:00
|
|
|
alarm_start(alarm, start);
|
2013-05-16 05:38:11 +08:00
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_start_relative);
|
2013-05-16 05:38:11 +08:00
|
|
|
|
|
|
|
void alarm_restart(struct alarm *alarm)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
hrtimer_set_expires(&alarm->timer, alarm->node.expires);
|
|
|
|
hrtimer_restart(&alarm->timer);
|
|
|
|
alarmtimer_enqueue(base, alarm);
|
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_restart);
|
2013-05-16 05:38:11 +08:00
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
2011-08-11 03:41:36 +08:00
|
|
|
* alarm_try_to_cancel - Tries to cancel an alarm timer
|
2011-01-12 01:42:13 +08:00
|
|
|
* @alarm: ptr to alarm to be canceled
|
2011-08-11 03:41:36 +08:00
|
|
|
*
|
|
|
|
* Returns 1 if the timer was canceled, 0 if it was not running,
|
|
|
|
* and -1 if the callback was running
|
2011-01-12 01:42:13 +08:00
|
|
|
*/
|
2011-08-11 03:41:36 +08:00
|
|
|
int alarm_try_to_cancel(struct alarm *alarm)
|
2011-01-12 01:42:13 +08:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
unsigned long flags;
|
2012-09-14 07:12:16 +08:00
|
|
|
int ret;
|
2011-08-11 03:41:36 +08:00
|
|
|
|
2012-09-14 07:12:16 +08:00
|
|
|
spin_lock_irqsave(&base->lock, flags);
|
|
|
|
ret = hrtimer_try_to_cancel(&alarm->timer);
|
|
|
|
if (ret >= 0)
|
2012-09-14 07:25:22 +08:00
|
|
|
alarmtimer_dequeue(base, alarm);
|
2011-01-12 01:42:13 +08:00
|
|
|
spin_unlock_irqrestore(&base->lock, flags);
|
2016-11-29 06:35:21 +08:00
|
|
|
|
|
|
|
trace_alarmtimer_cancel(alarm, base->gettime());
|
2011-08-11 03:41:36 +08:00
|
|
|
return ret;
|
2011-01-12 01:42:13 +08:00
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_try_to_cancel);
|
2011-01-12 01:42:13 +08:00
|
|
|
|
|
|
|
|
2011-08-11 03:41:36 +08:00
|
|
|
/**
|
|
|
|
* alarm_cancel - Spins trying to cancel an alarm timer until it is done
|
|
|
|
* @alarm: ptr to alarm to be canceled
|
|
|
|
*
|
|
|
|
* Returns 1 if the timer was canceled, 0 if it was not active.
|
|
|
|
*/
|
|
|
|
int alarm_cancel(struct alarm *alarm)
|
|
|
|
{
|
|
|
|
for (;;) {
|
|
|
|
int ret = alarm_try_to_cancel(alarm);
|
|
|
|
if (ret >= 0)
|
|
|
|
return ret;
|
|
|
|
cpu_relax();
|
|
|
|
}
|
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_cancel);
|
2011-08-11 03:41:36 +08:00
|
|
|
|
2011-08-11 02:31:03 +08:00
|
|
|
|
|
|
|
u64 alarm_forward(struct alarm *alarm, ktime_t now, ktime_t interval)
|
|
|
|
{
|
|
|
|
u64 overrun = 1;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
delta = ktime_sub(now, alarm->node.expires);
|
|
|
|
|
2016-12-25 18:38:40 +08:00
|
|
|
if (delta < 0)
|
2011-08-11 02:31:03 +08:00
|
|
|
return 0;
|
|
|
|
|
2016-12-25 18:38:40 +08:00
|
|
|
if (unlikely(delta >= interval)) {
|
2011-08-11 02:31:03 +08:00
|
|
|
s64 incr = ktime_to_ns(interval);
|
|
|
|
|
|
|
|
overrun = ktime_divns(delta, incr);
|
|
|
|
|
|
|
|
alarm->node.expires = ktime_add_ns(alarm->node.expires,
|
|
|
|
incr*overrun);
|
|
|
|
|
2016-12-25 18:38:40 +08:00
|
|
|
if (alarm->node.expires > now)
|
2011-08-11 02:31:03 +08:00
|
|
|
return overrun;
|
|
|
|
/*
|
|
|
|
* This (and the ktime_add() below) is the
|
|
|
|
* correction for exact:
|
|
|
|
*/
|
|
|
|
overrun++;
|
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:34 +08:00
|
|
|
alarm->node.expires = ktime_add_safe(alarm->node.expires, interval);
|
2011-08-11 02:31:03 +08:00
|
|
|
return overrun;
|
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_forward);
|
2011-08-11 02:31:03 +08:00
|
|
|
|
2013-05-16 05:38:11 +08:00
|
|
|
u64 alarm_forward_now(struct alarm *alarm, ktime_t interval)
|
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
|
|
|
|
return alarm_forward(alarm, base->gettime(), interval);
|
|
|
|
}
|
2013-06-04 15:32:09 +08:00
|
|
|
EXPORT_SYMBOL_GPL(alarm_forward_now);
|
2011-08-11 02:31:03 +08:00
|
|
|
|
2017-05-26 17:03:11 +08:00
|
|
|
#ifdef CONFIG_POSIX_TIMERS
|
|
|
|
|
|
|
|
static void alarmtimer_freezerset(ktime_t absexp, enum alarmtimer_type type)
|
|
|
|
{
|
|
|
|
struct alarm_base *base;
|
|
|
|
unsigned long flags;
|
|
|
|
ktime_t delta;
|
|
|
|
|
|
|
|
switch(type) {
|
|
|
|
case ALARM_REALTIME:
|
|
|
|
base = &alarm_bases[ALARM_REALTIME];
|
|
|
|
type = ALARM_REALTIME_FREEZER;
|
|
|
|
break;
|
|
|
|
case ALARM_BOOTTIME:
|
|
|
|
base = &alarm_bases[ALARM_BOOTTIME];
|
|
|
|
type = ALARM_BOOTTIME_FREEZER;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
WARN_ONCE(1, "Invalid alarm type: %d\n", type);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
delta = ktime_sub(absexp, base->gettime());
|
|
|
|
|
|
|
|
spin_lock_irqsave(&freezer_delta_lock, flags);
|
|
|
|
if (!freezer_delta || (delta < freezer_delta)) {
|
|
|
|
freezer_delta = delta;
|
|
|
|
freezer_expires = absexp;
|
|
|
|
freezer_alarmtype = type;
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&freezer_delta_lock, flags);
|
|
|
|
}
|
2011-08-11 02:31:03 +08:00
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
* clock2alarm - helper that converts from clockid to alarmtypes
|
|
|
|
* @clockid: clockid.
|
|
|
|
*/
|
|
|
|
static enum alarmtimer_type clock2alarm(clockid_t clockid)
|
|
|
|
{
|
|
|
|
if (clockid == CLOCK_REALTIME_ALARM)
|
|
|
|
return ALARM_REALTIME;
|
|
|
|
if (clockid == CLOCK_BOOTTIME_ALARM)
|
|
|
|
return ALARM_BOOTTIME;
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
* alarm_handle_timer - Callback for posix timers
|
|
|
|
* @alarm: alarm that fired
|
|
|
|
*
|
|
|
|
* Posix timer callback for expired alarm timers.
|
|
|
|
*/
|
2011-08-11 01:37:59 +08:00
|
|
|
static enum alarmtimer_restart alarm_handle_timer(struct alarm *alarm,
|
|
|
|
ktime_t now)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
|
|
|
struct k_itimer *ptr = container_of(alarm, struct k_itimer,
|
2017-05-31 05:15:59 +08:00
|
|
|
it.alarm.alarmtimer);
|
2014-09-10 09:31:05 +08:00
|
|
|
enum alarmtimer_restart result = ALARMTIMER_NORESTART;
|
2017-05-31 05:15:59 +08:00
|
|
|
unsigned long flags;
|
|
|
|
int si_private = 0;
|
2014-09-10 09:31:05 +08:00
|
|
|
|
|
|
|
spin_lock_irqsave(&ptr->it_lock, flags);
|
2011-08-11 01:37:59 +08:00
|
|
|
|
2017-05-31 05:15:59 +08:00
|
|
|
ptr->it_active = 0;
|
|
|
|
if (ptr->it_interval)
|
|
|
|
si_private = ++ptr->it_requeue_pending;
|
|
|
|
|
|
|
|
if (posix_timer_event(ptr, si_private) && ptr->it_interval) {
|
|
|
|
/*
|
|
|
|
* Handle ignored signals and rearm the timer. This will go
|
|
|
|
* away once we handle ignored signals proper.
|
|
|
|
*/
|
|
|
|
ptr->it_overrun += alarm_forward_now(alarm, ptr->it_interval);
|
|
|
|
++ptr->it_requeue_pending;
|
|
|
|
ptr->it_active = 1;
|
2014-09-10 09:31:05 +08:00
|
|
|
result = ALARMTIMER_RESTART;
|
2011-08-11 02:08:07 +08:00
|
|
|
}
|
2014-09-10 09:31:05 +08:00
|
|
|
spin_unlock_irqrestore(&ptr->it_lock, flags);
|
|
|
|
|
|
|
|
return result;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:54 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_rearm - Posix timer callback for rearming timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
*/
|
|
|
|
static void alarm_timer_rearm(struct k_itimer *timr)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
|
|
|
timr->it_overrun += alarm_forward_now(alarm, timr->it_interval);
|
|
|
|
alarm_start(alarm, alarm->node.expires);
|
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:55 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_forward - Posix timer callback for forwarding timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @now: Current time to forward the timer against
|
|
|
|
*/
|
|
|
|
static int alarm_timer_forward(struct k_itimer *timr, ktime_t now)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
|
|
|
return (int) alarm_forward(alarm, timr->it_interval, now);
|
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:56 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_remaining - Posix timer callback to retrieve remaining time
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @now: Current time to calculate against
|
|
|
|
*/
|
|
|
|
static ktime_t alarm_timer_remaining(struct k_itimer *timr, ktime_t now)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
|
|
|
|
return ktime_sub(now, alarm->node.expires);
|
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:57 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_try_to_cancel - Posix timer callback to cancel a timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
*/
|
|
|
|
static int alarm_timer_try_to_cancel(struct k_itimer *timr)
|
|
|
|
{
|
|
|
|
return alarm_try_to_cancel(&timr->it.alarm.alarmtimer);
|
|
|
|
}
|
|
|
|
|
2017-05-31 05:15:58 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_arm - Posix timer callback to arm a timer
|
|
|
|
* @timr: Pointer to the posixtimer data struct
|
|
|
|
* @expires: The new expiry time
|
|
|
|
* @absolute: Expiry value is absolute time
|
|
|
|
* @sigev_none: Posix timer does not deliver signals
|
|
|
|
*/
|
|
|
|
static void alarm_timer_arm(struct k_itimer *timr, ktime_t expires,
|
|
|
|
bool absolute, bool sigev_none)
|
|
|
|
{
|
|
|
|
struct alarm *alarm = &timr->it.alarm.alarmtimer;
|
|
|
|
struct alarm_base *base = &alarm_bases[alarm->type];
|
|
|
|
|
|
|
|
if (!absolute)
|
|
|
|
expires = ktime_add_safe(expires, base->gettime());
|
|
|
|
if (sigev_none)
|
|
|
|
alarm->node.expires = expires;
|
|
|
|
else
|
|
|
|
alarm_start(&timr->it.alarm.alarmtimer, expires);
|
|
|
|
}
|
|
|
|
|
2011-04-29 03:58:11 +08:00
|
|
|
/**
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
* alarm_clock_getres - posix getres interface
|
|
|
|
* @which_clock: clockid
|
|
|
|
* @tp: timespec to fill
|
|
|
|
*
|
|
|
|
* Returns the granularity of underlying alarm base clock
|
|
|
|
*/
|
2017-03-27 03:04:15 +08:00
|
|
|
static int alarm_clock_getres(const clockid_t which_clock, struct timespec64 *tp)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
2011-06-17 09:47:37 +08:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2013-10-15 05:33:16 +08:00
|
|
|
return -EINVAL;
|
2011-06-17 09:47:37 +08:00
|
|
|
|
2015-04-15 05:08:32 +08:00
|
|
|
tp->tv_sec = 0;
|
|
|
|
tp->tv_nsec = hrtimer_resolution;
|
|
|
|
return 0;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarm_clock_get - posix clock_get interface
|
|
|
|
* @which_clock: clockid
|
|
|
|
* @tp: timespec to fill.
|
|
|
|
*
|
|
|
|
* Provides the underlying alarm base time.
|
|
|
|
*/
|
2017-03-27 03:04:14 +08:00
|
|
|
static int alarm_clock_get(clockid_t which_clock, struct timespec64 *tp)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
|
|
|
struct alarm_base *base = &alarm_bases[clock2alarm(which_clock)];
|
|
|
|
|
2011-06-17 09:47:37 +08:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
2013-10-15 05:33:16 +08:00
|
|
|
return -EINVAL;
|
2011-06-17 09:47:37 +08:00
|
|
|
|
2017-03-27 03:04:14 +08:00
|
|
|
*tp = ktime_to_timespec64(base->gettime());
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarm_timer_create - posix timer_create interface
|
|
|
|
* @new_timer: k_itimer pointer to manage
|
|
|
|
*
|
|
|
|
* Initializes the k_itimer structure.
|
|
|
|
*/
|
|
|
|
static int alarm_timer_create(struct k_itimer *new_timer)
|
|
|
|
{
|
|
|
|
enum alarmtimer_type type;
|
|
|
|
|
2011-06-17 09:47:37 +08:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
|
|
|
return -ENOTSUPP;
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
if (!capable(CAP_WAKE_ALARM))
|
|
|
|
return -EPERM;
|
|
|
|
|
|
|
|
type = clock2alarm(new_timer->it_clock);
|
2011-08-11 03:09:24 +08:00
|
|
|
alarm_init(&new_timer->it.alarm.alarmtimer, type, alarm_handle_timer);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarmtimer_nsleep_wakeup - Wakeup function for alarm_timer_nsleep
|
|
|
|
* @alarm: ptr to alarm that fired
|
|
|
|
*
|
|
|
|
* Wakes up the task that set the alarmtimer
|
|
|
|
*/
|
2011-08-11 01:37:59 +08:00
|
|
|
static enum alarmtimer_restart alarmtimer_nsleep_wakeup(struct alarm *alarm,
|
|
|
|
ktime_t now)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
|
|
|
struct task_struct *task = (struct task_struct *)alarm->data;
|
|
|
|
|
|
|
|
alarm->data = NULL;
|
|
|
|
if (task)
|
|
|
|
wake_up_process(task);
|
2011-08-11 01:37:59 +08:00
|
|
|
return ALARMTIMER_NORESTART;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarmtimer_do_nsleep - Internal alarmtimer nsleep implementation
|
|
|
|
* @alarm: ptr to alarmtimer
|
|
|
|
* @absexp: absolute expiration time
|
|
|
|
*
|
|
|
|
* Sets the alarm timer and sleeps until it is fired or interrupted.
|
|
|
|
*/
|
2017-06-07 16:42:27 +08:00
|
|
|
static int alarmtimer_do_nsleep(struct alarm *alarm, ktime_t absexp,
|
|
|
|
enum alarmtimer_type type)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
2017-06-07 16:42:31 +08:00
|
|
|
struct restart_block *restart;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
alarm->data = (void *)current;
|
|
|
|
do {
|
|
|
|
set_current_state(TASK_INTERRUPTIBLE);
|
2011-08-11 03:09:24 +08:00
|
|
|
alarm_start(alarm, absexp);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
if (likely(alarm->data))
|
|
|
|
schedule();
|
|
|
|
|
|
|
|
alarm_cancel(alarm);
|
|
|
|
} while (alarm->data && !signal_pending(current));
|
|
|
|
|
|
|
|
__set_current_state(TASK_RUNNING);
|
|
|
|
|
2018-03-26 21:29:57 +08:00
|
|
|
destroy_hrtimer_on_stack(&alarm->timer);
|
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
if (!alarm->data)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
return 0;
|
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
if (freezing(current))
|
|
|
|
alarmtimer_freezerset(absexp, type);
|
2017-06-07 16:42:31 +08:00
|
|
|
restart = ¤t->restart_block;
|
|
|
|
if (restart->nanosleep.type != TT_NONE) {
|
2017-06-25 02:45:06 +08:00
|
|
|
struct timespec64 rmt;
|
2017-06-07 16:42:27 +08:00
|
|
|
ktime_t rem;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
rem = ktime_sub(absexp, alarm_bases[type].gettime());
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
if (rem <= 0)
|
|
|
|
return 0;
|
2017-06-25 02:45:06 +08:00
|
|
|
rmt = ktime_to_timespec64(rem);
|
2017-06-07 16:42:27 +08:00
|
|
|
|
2017-06-07 16:42:32 +08:00
|
|
|
return nanosleep_copyout(restart, &rmt);
|
2017-06-07 16:42:27 +08:00
|
|
|
}
|
|
|
|
return -ERESTART_RESTARTBLOCK;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
}
|
|
|
|
|
2018-03-26 21:29:57 +08:00
|
|
|
static void
|
|
|
|
alarm_init_on_stack(struct alarm *alarm, enum alarmtimer_type type,
|
|
|
|
enum alarmtimer_restart (*function)(struct alarm *, ktime_t))
|
|
|
|
{
|
|
|
|
hrtimer_init_on_stack(&alarm->timer, alarm_bases[type].base_clockid,
|
|
|
|
HRTIMER_MODE_ABS);
|
|
|
|
__alarm_init(alarm, type, function);
|
|
|
|
}
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
/**
|
|
|
|
* alarm_timer_nsleep_restart - restartblock alarmtimer nsleep
|
|
|
|
* @restart: ptr to restart block
|
|
|
|
*
|
|
|
|
* Handles restarted clock_nanosleep calls
|
|
|
|
*/
|
|
|
|
static long __sched alarm_timer_nsleep_restart(struct restart_block *restart)
|
|
|
|
{
|
2011-05-20 19:05:15 +08:00
|
|
|
enum alarmtimer_type type = restart->nanosleep.clockid;
|
2017-06-07 16:42:27 +08:00
|
|
|
ktime_t exp = restart->nanosleep.expires;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
struct alarm alarm;
|
|
|
|
|
2018-03-26 21:29:57 +08:00
|
|
|
alarm_init_on_stack(&alarm, type, alarmtimer_nsleep_wakeup);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
return alarmtimer_do_nsleep(&alarm, exp, type);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarm_timer_nsleep - alarmtimer nanosleep
|
|
|
|
* @which_clock: clockid
|
|
|
|
* @flags: determins abstime or relative
|
|
|
|
* @tsreq: requested sleep time (abs or rel)
|
|
|
|
* @rmtp: remaining sleep time saved
|
|
|
|
*
|
|
|
|
* Handles clock_nanosleep calls against _ALARM clockids
|
|
|
|
*/
|
|
|
|
static int alarm_timer_nsleep(const clockid_t which_clock, int flags,
|
2017-06-14 05:34:33 +08:00
|
|
|
const struct timespec64 *tsreq)
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
{
|
|
|
|
enum alarmtimer_type type = clock2alarm(which_clock);
|
2017-06-07 16:42:27 +08:00
|
|
|
struct restart_block *restart = ¤t->restart_block;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
struct alarm alarm;
|
|
|
|
ktime_t exp;
|
|
|
|
int ret = 0;
|
|
|
|
|
2011-06-17 09:47:37 +08:00
|
|
|
if (!alarmtimer_get_rtcdev())
|
|
|
|
return -ENOTSUPP;
|
|
|
|
|
2014-07-08 05:06:11 +08:00
|
|
|
if (flags & ~TIMER_ABSTIME)
|
|
|
|
return -EINVAL;
|
|
|
|
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
if (!capable(CAP_WAKE_ALARM))
|
|
|
|
return -EPERM;
|
|
|
|
|
2018-03-26 21:29:57 +08:00
|
|
|
alarm_init_on_stack(&alarm, type, alarmtimer_nsleep_wakeup);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
2017-03-27 03:04:18 +08:00
|
|
|
exp = timespec64_to_ktime(*tsreq);
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
/* Convert (if necessary) to absolute time */
|
|
|
|
if (flags != TIMER_ABSTIME) {
|
|
|
|
ktime_t now = alarm_bases[type].gettime();
|
|
|
|
exp = ktime_add(now, exp);
|
|
|
|
}
|
|
|
|
|
2017-06-07 16:42:27 +08:00
|
|
|
ret = alarmtimer_do_nsleep(&alarm, exp, type);
|
|
|
|
if (ret != -ERESTART_RESTARTBLOCK)
|
|
|
|
return ret;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
|
|
|
/* abs timers don't set remaining time or restart */
|
2017-06-07 16:42:27 +08:00
|
|
|
if (flags == TIMER_ABSTIME)
|
|
|
|
return -ERESTARTNOHAND;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
|
|
|
restart->fn = alarm_timer_nsleep_restart;
|
2011-05-20 19:05:15 +08:00
|
|
|
restart->nanosleep.clockid = type;
|
2016-12-25 18:38:40 +08:00
|
|
|
restart->nanosleep.expires = exp;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
return ret;
|
|
|
|
}
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2017-05-26 17:03:11 +08:00
|
|
|
const struct k_clock alarm_clock = {
|
2017-05-31 05:15:56 +08:00
|
|
|
.clock_getres = alarm_clock_getres,
|
|
|
|
.clock_get = alarm_clock_get,
|
|
|
|
.timer_create = alarm_timer_create,
|
2017-05-31 05:15:59 +08:00
|
|
|
.timer_set = common_timer_set,
|
|
|
|
.timer_del = common_timer_del,
|
|
|
|
.timer_get = common_timer_get,
|
2017-05-31 05:15:58 +08:00
|
|
|
.timer_arm = alarm_timer_arm,
|
2017-05-31 05:15:56 +08:00
|
|
|
.timer_rearm = alarm_timer_rearm,
|
|
|
|
.timer_forward = alarm_timer_forward,
|
|
|
|
.timer_remaining = alarm_timer_remaining,
|
2017-05-31 05:15:57 +08:00
|
|
|
.timer_try_to_cancel = alarm_timer_try_to_cancel,
|
2017-05-31 05:15:56 +08:00
|
|
|
.nsleep = alarm_timer_nsleep,
|
2017-05-26 17:03:11 +08:00
|
|
|
};
|
|
|
|
#endif /* CONFIG_POSIX_TIMERS */
|
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
|
|
|
|
/* Suspend hook structures */
|
|
|
|
static const struct dev_pm_ops alarmtimer_pm_ops = {
|
|
|
|
.suspend = alarmtimer_suspend,
|
2015-11-17 20:08:07 +08:00
|
|
|
.resume = alarmtimer_resume,
|
2011-01-12 01:42:13 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
static struct platform_driver alarmtimer_driver = {
|
|
|
|
.driver = {
|
|
|
|
.name = "alarmtimer",
|
|
|
|
.pm = &alarmtimer_pm_ops,
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* alarmtimer_init - Initialize alarm timer code
|
|
|
|
*
|
|
|
|
* This function initializes the alarm bases and registers
|
|
|
|
* the posix clock ids.
|
|
|
|
*/
|
|
|
|
static int __init alarmtimer_init(void)
|
|
|
|
{
|
2011-09-14 16:54:29 +08:00
|
|
|
struct platform_device *pdev;
|
2011-01-12 01:42:13 +08:00
|
|
|
int error = 0;
|
|
|
|
int i;
|
timers: Posix interface for alarm-timers
This patch exposes alarm-timers to userland via the posix clock
and timers interface, using two new clockids: CLOCK_REALTIME_ALARM
and CLOCK_BOOTTIME_ALARM. Both clockids behave identically to
CLOCK_REALTIME and CLOCK_BOOTTIME, respectively, but timers
set against the _ALARM suffixed clockids will wake the system if
it is suspended.
Some background can be found here:
https://lwn.net/Articles/429925/
The concept for Alarm-timers was inspired by the Android Alarm
driver (by Arve Hjønnevåg) found in the Android kernel tree.
See: http://android.git.kernel.org/?p=kernel/common.git;a=blob;f=drivers/rtc/alarm.c;h=1250edfbdf3302f5e4ea6194847c6ef4bb7beb1c;hb=android-2.6.36
While the in-kernel interface is pretty similar between
alarm-timers and Android alarm driver, the user-space interface
for the Android alarm driver is via ioctls to a new char device.
As mentioned above, I've instead chosen to export this functionality
via the posix interface, as it seemed a little simpler and avoids
creating duplicate interfaces to things like CLOCK_REALTIME and
CLOCK_MONOTONIC under alternate names (ie:ANDROID_ALARM_RTC and
ANDROID_ALARM_SYSTEMTIME).
The semantics of the Android alarm driver are different from what
this posix interface provides. For instance, threads other then
the thread waiting on the Android alarm driver are able to modify
the alarm being waited on. Also this interface does not allow
the same wakelock semantics that the Android driver provides
(ie: kernel takes a wakelock on RTC alarm-interupt, and holds it
through process wakeup, and while the process runs, until the
process either closes the char device or calls back in to wait
on a new alarm).
One potential way to implement similar semantics may be via
the timerfd infrastructure, but this needs more research.
There may also need to be some sort of sysfs system level policy
hooks that allow alarm timers to be disabled to keep them
from firing at inappropriate times (ie: laptop in a well insulated
bag, mid-flight).
CC: Arve Hjønnevåg <arve@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-01-12 01:54:33 +08:00
|
|
|
|
2012-03-24 19:46:23 +08:00
|
|
|
alarmtimer_rtc_timer_init();
|
2012-03-24 06:52:25 +08:00
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
/* Initialize alarm bases */
|
|
|
|
alarm_bases[ALARM_REALTIME].base_clockid = CLOCK_REALTIME;
|
|
|
|
alarm_bases[ALARM_REALTIME].gettime = &ktime_get_real;
|
|
|
|
alarm_bases[ALARM_BOOTTIME].base_clockid = CLOCK_BOOTTIME;
|
|
|
|
alarm_bases[ALARM_BOOTTIME].gettime = &ktime_get_boottime;
|
|
|
|
for (i = 0; i < ALARM_NUMTYPE; i++) {
|
|
|
|
timerqueue_init_head(&alarm_bases[i].timerqueue);
|
|
|
|
spin_lock_init(&alarm_bases[i].lock);
|
|
|
|
}
|
2011-07-15 09:35:13 +08:00
|
|
|
|
2011-09-14 16:54:29 +08:00
|
|
|
error = alarmtimer_rtc_interface_setup();
|
|
|
|
if (error)
|
|
|
|
return error;
|
|
|
|
|
2011-01-12 01:42:13 +08:00
|
|
|
error = platform_driver_register(&alarmtimer_driver);
|
2011-09-14 16:54:29 +08:00
|
|
|
if (error)
|
|
|
|
goto out_if;
|
2011-01-12 01:42:13 +08:00
|
|
|
|
2011-09-14 16:54:29 +08:00
|
|
|
pdev = platform_device_register_simple("alarmtimer", -1, NULL, 0);
|
|
|
|
if (IS_ERR(pdev)) {
|
|
|
|
error = PTR_ERR(pdev);
|
|
|
|
goto out_drv;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
out_drv:
|
|
|
|
platform_driver_unregister(&alarmtimer_driver);
|
|
|
|
out_if:
|
|
|
|
alarmtimer_rtc_interface_remove();
|
2011-01-12 01:42:13 +08:00
|
|
|
return error;
|
|
|
|
}
|
|
|
|
device_initcall(alarmtimer_init);
|