2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
|
* Generic RTC interface.
|
|
|
|
|
* This version contains the part of the user interface to the Real Time Clock
|
|
|
|
|
* service. It is used with both the legacy mc146818 and also EFI
|
|
|
|
|
* Struct rtc_time and first 12 ioctl by Paul Gortmaker, 1996 - separated out
|
|
|
|
|
* from <linux/mc146818rtc.h> to this file for 2.4 kernels.
|
2007-05-08 15:33:30 +08:00
|
|
|
*
|
2005-04-17 06:20:36 +08:00
|
|
|
* Copyright (C) 1999 Hewlett-Packard Co.
|
|
|
|
|
* Copyright (C) 1999 Stephane Eranian <eranian@hpl.hp.com>
|
|
|
|
|
*/
|
|
|
|
|
#ifndef _LINUX_RTC_H_
|
|
|
|
|
#define _LINUX_RTC_H_
|
|
|
|
|
|
|
|
|
|
|
2009-04-01 06:24:48 +08:00
|
|
|
#include <linux/types.h>
|
2006-03-22 16:07:43 +08:00
|
|
|
#include <linux/interrupt.h>
|
2012-10-13 17:46:48 +08:00
|
|
|
#include <uapi/linux/rtc.h>
|
2006-03-22 16:07:43 +08:00
|
|
|
|
2006-03-27 17:16:34 +08:00
|
|
|
extern int rtc_month_days(unsigned int month, unsigned int year);
|
2006-06-25 20:48:25 +08:00
|
|
|
extern int rtc_year_days(unsigned int day, unsigned int month, unsigned int year);
|
2006-03-27 17:16:34 +08:00
|
|
|
extern int rtc_valid_tm(struct rtc_time *tm);
|
|
|
|
|
extern int rtc_tm_to_time(struct rtc_time *tm, unsigned long *time);
|
|
|
|
|
extern void rtc_time_to_tm(unsigned long time, struct rtc_time *tm);
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
ktime_t rtc_tm_to_ktime(struct rtc_time tm);
|
|
|
|
|
struct rtc_time rtc_ktime_to_tm(ktime_t kt);
|
|
|
|
|
|
2006-03-27 17:16:34 +08:00
|
|
|
|
2006-03-27 17:16:37 +08:00
|
|
|
#include <linux/device.h>
|
|
|
|
|
#include <linux/seq_file.h>
|
|
|
|
|
#include <linux/cdev.h>
|
|
|
|
|
#include <linux/poll.h>
|
|
|
|
|
#include <linux/mutex.h>
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
#include <linux/timerqueue.h>
|
|
|
|
|
#include <linux/workqueue.h>
|
2006-03-27 17:16:37 +08:00
|
|
|
|
|
|
|
|
extern struct class *rtc_class;
|
|
|
|
|
|
2008-07-24 12:30:33 +08:00
|
|
|
/*
|
|
|
|
|
* For these RTC methods the device parameter is the physical device
|
|
|
|
|
* on whatever bus holds the hardware (I2C, Platform, SPI, etc), which
|
|
|
|
|
* was passed to rtc_device_register(). Its driver_data normally holds
|
|
|
|
|
* device state, including the rtc_device pointer for the RTC.
|
|
|
|
|
*
|
|
|
|
|
* Most of these methods are called with rtc_device.ops_lock held,
|
|
|
|
|
* through the rtc_*(struct rtc_device *, ...) calls.
|
|
|
|
|
*
|
|
|
|
|
* The (current) exceptions are mostly filesystem hooks:
|
|
|
|
|
* - the proc() hook for procfs
|
|
|
|
|
* - non-ioctl() chardev hooks: open(), release(), read_callback()
|
|
|
|
|
*
|
|
|
|
|
* REVISIT those periodic irq calls *do* have ops_lock when they're
|
|
|
|
|
* issued through ioctl() ...
|
|
|
|
|
*/
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_class_ops {
|
|
|
|
|
int (*open)(struct device *);
|
|
|
|
|
void (*release)(struct device *);
|
|
|
|
|
int (*ioctl)(struct device *, unsigned int, unsigned long);
|
|
|
|
|
int (*read_time)(struct device *, struct rtc_time *);
|
|
|
|
|
int (*set_time)(struct device *, struct rtc_time *);
|
|
|
|
|
int (*read_alarm)(struct device *, struct rtc_wkalrm *);
|
|
|
|
|
int (*set_alarm)(struct device *, struct rtc_wkalrm *);
|
|
|
|
|
int (*proc)(struct device *, struct seq_file *);
|
|
|
|
|
int (*set_mmss)(struct device *, unsigned long secs);
|
|
|
|
|
int (*read_callback)(struct device *, int data);
|
2009-01-05 04:00:54 +08:00
|
|
|
int (*alarm_irq_enable)(struct device *, unsigned int enabled);
|
2006-03-27 17:16:37 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define RTC_DEVICE_NAME_SIZE 20
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
typedef struct rtc_task {
|
|
|
|
|
void (*func)(void *private_data);
|
|
|
|
|
void *private_data;
|
|
|
|
|
} rtc_task_t;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
struct rtc_timer {
|
|
|
|
|
struct rtc_task task;
|
|
|
|
|
struct timerqueue_node node;
|
|
|
|
|
ktime_t period;
|
|
|
|
|
int enabled;
|
|
|
|
|
};
|
|
|
|
|
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2007-11-29 08:22:03 +08:00
|
|
|
/* flags */
|
|
|
|
|
#define RTC_DEV_BUSY 0
|
|
|
|
|
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_device
|
|
|
|
|
{
|
2007-05-08 15:33:40 +08:00
|
|
|
struct device dev;
|
2006-03-27 17:16:37 +08:00
|
|
|
struct module *owner;
|
|
|
|
|
|
|
|
|
|
int id;
|
|
|
|
|
char name[RTC_DEVICE_NAME_SIZE];
|
|
|
|
|
|
2006-10-01 14:28:17 +08:00
|
|
|
const struct rtc_class_ops *ops;
|
2006-03-27 17:16:37 +08:00
|
|
|
struct mutex ops_lock;
|
|
|
|
|
|
|
|
|
|
struct cdev char_dev;
|
2007-11-29 08:22:03 +08:00
|
|
|
unsigned long flags;
|
2006-03-27 17:16:37 +08:00
|
|
|
|
|
|
|
|
unsigned long irq_data;
|
|
|
|
|
spinlock_t irq_lock;
|
|
|
|
|
wait_queue_head_t irq_queue;
|
|
|
|
|
struct fasync_struct *async_queue;
|
|
|
|
|
|
|
|
|
|
struct rtc_task *irq_task;
|
|
|
|
|
spinlock_t irq_task_lock;
|
|
|
|
|
int irq_freq;
|
2006-06-25 20:48:20 +08:00
|
|
|
int max_user_freq;
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
|
|
|
|
|
struct timerqueue_head timerqueue;
|
|
|
|
|
struct rtc_timer aie_timer;
|
|
|
|
|
struct rtc_timer uie_rtctimer;
|
|
|
|
|
struct hrtimer pie_timer; /* sub second exp, so needs hrtimer */
|
|
|
|
|
int pie_enabled;
|
|
|
|
|
struct work_struct irqwork;
|
2012-03-07 09:16:09 +08:00
|
|
|
/* Some hardware can't support UIE mode */
|
|
|
|
|
int uie_unsupported;
|
2011-02-12 09:45:40 +08:00
|
|
|
|
|
|
|
|
#ifdef CONFIG_RTC_INTF_DEV_UIE_EMUL
|
|
|
|
|
struct work_struct uie_task;
|
|
|
|
|
struct timer_list uie_timer;
|
|
|
|
|
/* Those fields are protected by rtc->irq_lock */
|
|
|
|
|
unsigned int oldsecs;
|
|
|
|
|
unsigned int uie_irq_active:1;
|
|
|
|
|
unsigned int stop_uie_polling:1;
|
|
|
|
|
unsigned int uie_task_active:1;
|
|
|
|
|
unsigned int uie_timer_active:1;
|
|
|
|
|
#endif
|
2006-03-27 17:16:37 +08:00
|
|
|
};
|
2007-05-08 15:33:40 +08:00
|
|
|
#define to_rtc_device(d) container_of(d, struct rtc_device, dev)
|
2006-03-27 17:16:37 +08:00
|
|
|
|
|
|
|
|
extern struct rtc_device *rtc_device_register(const char *name,
|
|
|
|
|
struct device *dev,
|
2006-10-01 14:28:17 +08:00
|
|
|
const struct rtc_class_ops *ops,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct module *owner);
|
2013-04-30 07:18:33 +08:00
|
|
|
extern struct rtc_device *devm_rtc_device_register(struct device *dev,
|
|
|
|
|
const char *name,
|
2013-04-30 07:18:27 +08:00
|
|
|
const struct rtc_class_ops *ops,
|
|
|
|
|
struct module *owner);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern void rtc_device_unregister(struct rtc_device *rtc);
|
2013-04-30 07:18:27 +08:00
|
|
|
extern void devm_rtc_device_unregister(struct device *dev,
|
|
|
|
|
struct rtc_device *rtc);
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_read_time(struct rtc_device *rtc, struct rtc_time *tm);
|
|
|
|
|
extern int rtc_set_time(struct rtc_device *rtc, struct rtc_time *tm);
|
|
|
|
|
extern int rtc_set_mmss(struct rtc_device *rtc, unsigned long secs);
|
2012-12-18 05:30:53 +08:00
|
|
|
extern int rtc_set_ntp_time(struct timespec now);
|
RTC: Initialize kernel state from RTC
Mark Brown pointed out a corner case: that RTC alarms should
be allowed to be persistent across reboots if the hardware
supported it.
The rework of the generic layer to virtualize the RTC alarm
virtualized much of the alarm handling, and removed the
code used to read the alarm time from the hardware.
Mark noted if we want the alarm to be persistent across
reboots, we need to re-read the alarm value into the
virtualized generic layer at boot up, so that the generic
layer properly exposes that value.
This patch restores much of the earlier removed
rtc_read_alarm code and wires it in so that we
set the kernel's alarm value to what we find in the
hardware at boot time.
NOTE: Not all hardware supports persistent RTC alarm state across
system reset. rtc-cmos for example will keep the alarm time, but
disables the AIE mode irq. Applications should not expect the RTC
alarm to be valid after a system reset. We will preserve what
we can, to represent the hardware state at boot, but its not
guarenteed.
Further, in the future, with multiplexed RTC alarms, the
soonest alarm to fire may not be the one set via the /dev/rt
ioctls. So an application may set the alarm with RTC_ALM_SET,
but after a reset find that RTC_ALM_READ returns an earlier
time. Again, we preserve what we can, but applications should
not expect the RTC alarm state to persist across a system reset.
Big thanks to Mark for pointing out the issue!
Thanks also to Marcelo for helping think through the solution.
CC: Mark Brown <broonie@opensource.wolfsonmicro.com>
CC: Marcelo Roberto Jimenez <mroberto@cpti.cetuc.puc-rio.br>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: rtc-linux@googlegroups.com
Reported-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2011-02-22 14:58:51 +08:00
|
|
|
int __rtc_read_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_read_alarm(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_wkalrm *alrm);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_set_alarm(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_wkalrm *alrm);
|
2011-03-30 09:00:27 +08:00
|
|
|
extern int rtc_initialize_alarm(struct rtc_device *rtc,
|
|
|
|
|
struct rtc_wkalrm *alrm);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern void rtc_update_irq(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
unsigned long num, unsigned long events);
|
|
|
|
|
|
2013-02-02 03:40:17 +08:00
|
|
|
extern struct rtc_device *rtc_class_open(const char *name);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern void rtc_class_close(struct rtc_device *rtc);
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_irq_register(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_task *task);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern void rtc_irq_unregister(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_task *task);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_irq_set_state(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_task *task, int enabled);
|
2007-05-08 15:33:30 +08:00
|
|
|
extern int rtc_irq_set_freq(struct rtc_device *rtc,
|
2006-03-27 17:16:37 +08:00
|
|
|
struct rtc_task *task, int freq);
|
2009-01-05 04:00:54 +08:00
|
|
|
extern int rtc_update_irq_enable(struct rtc_device *rtc, unsigned int enabled);
|
|
|
|
|
extern int rtc_alarm_irq_enable(struct rtc_device *rtc, unsigned int enabled);
|
2011-02-12 09:45:40 +08:00
|
|
|
extern int rtc_dev_update_irq_enable_emul(struct rtc_device *rtc,
|
|
|
|
|
unsigned int enabled);
|
2006-03-27 17:16:37 +08:00
|
|
|
|
2011-02-12 10:15:23 +08:00
|
|
|
void rtc_handle_legacy_irq(struct rtc_device *rtc, int num, int mode);
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
void rtc_aie_update_irq(void *private);
|
|
|
|
|
void rtc_uie_update_irq(void *private);
|
|
|
|
|
enum hrtimer_restart rtc_pie_update_irq(struct hrtimer *timer);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
int rtc_register(rtc_task_t *task);
|
|
|
|
|
int rtc_unregister(rtc_task_t *task);
|
|
|
|
|
int rtc_control(rtc_task_t *t, unsigned int cmd, unsigned long arg);
|
|
|
|
|
|
2010-12-14 05:45:48 +08:00
|
|
|
void rtc_timer_init(struct rtc_timer *timer, void (*f)(void* p), void* data);
|
|
|
|
|
int rtc_timer_start(struct rtc_device *rtc, struct rtc_timer* timer,
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
ktime_t expires, ktime_t period);
|
2010-12-14 05:45:48 +08:00
|
|
|
int rtc_timer_cancel(struct rtc_device *rtc, struct rtc_timer* timer);
|
|
|
|
|
void rtc_timer_do_work(struct work_struct *work);
|
RTC: Rework RTC code to use timerqueue for events
This patch reworks a large portion of the generic RTC code
to in-effect virtualize the rtc interrupt code.
The current RTC interface is very much a raw hardware interface.
Via the proc, /dev/, or sysfs interfaces, applciations can set
the hardware to trigger interrupts in one of three modes:
AIE: Alarm interrupt
UIE: Update interrupt (ie: once per second)
PIE: Periodic interrupt (sub-second irqs)
The problem with this interface is that it limits the RTC hardware
so it can only be used by one application at a time.
The purpose of this patch is to extend the RTC code so that we can
multiplex multiple applications event needs onto a single RTC device.
This is done by utilizing the timerqueue infrastructure to manage
a list of events, which cause the RTC hardware to be programmed
to fire an interrupt for the next event in the list.
In order to preserve the functionality of the exsting proc,/dev/ and
sysfs interfaces, we emulate the different interrupt modes as follows:
AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
only one per device, so we don't change existing interface semantics.
UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
to emulate UIE interrupts. Again, only one per device.
PIE: Since PIE mode interrupts fire faster then the RTC's clock read
granularity, we emulate PIE mode interrupts using a hrtimer. Again,
one per device.
With this patch, the rtctest.c application in Documentation/rtc.txt
passes fine on x86 hardware. However, there may very well still be
bugs, so greatly I'd appreciate any feedback or testing!
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
Acked-by: Alessandro Zummo <a.zummo@towertech.it>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Richard Cochran <richardcochran@gmail.com>
2010-09-24 06:07:34 +08:00
|
|
|
|
2009-04-01 06:24:48 +08:00
|
|
|
static inline bool is_leap_year(unsigned int year)
|
|
|
|
|
{
|
|
|
|
|
return (!(year % 4) && (year % 100)) || !(year % 400);
|
|
|
|
|
}
|
|
|
|
|
|
2012-10-05 08:14:12 +08:00
|
|
|
#ifdef CONFIG_RTC_HCTOSYS_DEVICE
|
2010-03-11 07:20:35 +08:00
|
|
|
extern int rtc_hctosys_ret;
|
|
|
|
|
#else
|
|
|
|
|
#define rtc_hctosys_ret -ENODEV
|
|
|
|
|
#endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
#endif /* _LINUX_RTC_H_ */
|