2019-03-14 06:02:48 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2006-03-27 17:16:34 +08:00
|
|
|
/*
|
|
|
|
* rtc and date/time utility functions
|
|
|
|
*
|
|
|
|
* Copyright (C) 2005-06 Tower Technologies
|
|
|
|
* Author: Alessandro Zummo <a.zummo@towertech.it>
|
|
|
|
*
|
|
|
|
* based on arch/arm/common/rtctime.c and other bits
|
2021-06-25 04:13:43 +08:00
|
|
|
*
|
|
|
|
* Author: Cassio Neri <cassio.neri@gmail.com> (rtc_time64_to_tm)
|
2019-03-14 06:02:48 +08:00
|
|
|
*/
|
2006-03-27 17:16:34 +08:00
|
|
|
|
2016-11-01 02:55:25 +08:00
|
|
|
#include <linux/export.h>
|
2006-03-27 17:16:34 +08:00
|
|
|
#include <linux/rtc.h>
|
|
|
|
|
|
|
|
static const unsigned char rtc_days_in_month[] = {
|
|
|
|
31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31
|
|
|
|
};
|
|
|
|
|
2006-06-25 20:48:25 +08:00
|
|
|
static const unsigned short rtc_ydays[2][13] = {
|
|
|
|
/* Normal years */
|
|
|
|
{ 0, 31, 59, 90, 120, 151, 181, 212, 243, 273, 304, 334, 365 },
|
|
|
|
/* Leap years */
|
|
|
|
{ 0, 31, 60, 91, 121, 152, 182, 213, 244, 274, 305, 335, 366 }
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The number of days in the month.
|
|
|
|
*/
|
2006-03-27 17:16:34 +08:00
|
|
|
int rtc_month_days(unsigned int month, unsigned int year)
|
|
|
|
{
|
2009-04-01 06:24:48 +08:00
|
|
|
return rtc_days_in_month[month] + (is_leap_year(year) && month == 1);
|
2006-03-27 17:16:34 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(rtc_month_days);
|
|
|
|
|
2006-06-25 20:48:25 +08:00
|
|
|
/*
|
|
|
|
* The number of days since January 1. (0 to 365)
|
|
|
|
*/
|
|
|
|
int rtc_year_days(unsigned int day, unsigned int month, unsigned int year)
|
|
|
|
{
|
2019-03-20 19:59:09 +08:00
|
|
|
return rtc_ydays[is_leap_year(year)][month] + day - 1;
|
2006-06-25 20:48:25 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(rtc_year_days);
|
|
|
|
|
2021-06-25 04:13:43 +08:00
|
|
|
/**
|
|
|
|
* rtc_time64_to_tm - converts time64_t to rtc_time.
|
|
|
|
*
|
|
|
|
* @time: The number of seconds since 01-01-1970 00:00:00.
|
|
|
|
* (Must be positive.)
|
|
|
|
* @tm: Pointer to the struct rtc_time.
|
2006-03-27 17:16:34 +08:00
|
|
|
*/
|
2014-11-18 19:15:19 +08:00
|
|
|
void rtc_time64_to_tm(time64_t time, struct rtc_time *tm)
|
2006-03-27 17:16:34 +08:00
|
|
|
{
|
2021-06-25 04:13:43 +08:00
|
|
|
unsigned int secs;
|
2008-09-03 05:36:05 +08:00
|
|
|
int days;
|
2006-03-27 17:16:34 +08:00
|
|
|
|
2021-06-25 04:13:43 +08:00
|
|
|
u64 u64tmp;
|
|
|
|
u32 u32tmp, udays, century, day_of_century, year_of_century, year,
|
|
|
|
day_of_year, month, day;
|
|
|
|
bool is_Jan_or_Feb, is_leap_year;
|
|
|
|
|
2014-11-18 19:15:19 +08:00
|
|
|
/* time must be positive */
|
2017-12-25 19:10:37 +08:00
|
|
|
days = div_s64_rem(time, 86400, &secs);
|
2006-03-27 17:16:34 +08:00
|
|
|
|
|
|
|
/* day of the week, 1970-01-01 was a Thursday */
|
|
|
|
tm->tm_wday = (days + 4) % 7;
|
|
|
|
|
2021-06-25 04:13:43 +08:00
|
|
|
/*
|
|
|
|
* The following algorithm is, basically, Proposition 6.3 of Neri
|
|
|
|
* and Schneider [1]. In a few words: it works on the computational
|
|
|
|
* (fictitious) calendar where the year starts in March, month = 2
|
|
|
|
* (*), and finishes in February, month = 13. This calendar is
|
|
|
|
* mathematically convenient because the day of the year does not
|
|
|
|
* depend on whether the year is leap or not. For instance:
|
|
|
|
*
|
|
|
|
* March 1st 0-th day of the year;
|
|
|
|
* ...
|
|
|
|
* April 1st 31-st day of the year;
|
|
|
|
* ...
|
|
|
|
* January 1st 306-th day of the year; (Important!)
|
|
|
|
* ...
|
|
|
|
* February 28th 364-th day of the year;
|
|
|
|
* February 29th 365-th day of the year (if it exists).
|
|
|
|
*
|
|
|
|
* After having worked out the date in the computational calendar
|
|
|
|
* (using just arithmetics) it's easy to convert it to the
|
|
|
|
* corresponding date in the Gregorian calendar.
|
|
|
|
*
|
|
|
|
* [1] "Euclidean Affine Functions and Applications to Calendar
|
|
|
|
* Algorithms". https://arxiv.org/abs/2102.06959
|
|
|
|
*
|
|
|
|
* (*) The numbering of months follows rtc_time more closely and
|
|
|
|
* thus, is slightly different from [1].
|
|
|
|
*/
|
|
|
|
|
|
|
|
udays = ((u32) days) + 719468;
|
|
|
|
|
|
|
|
u32tmp = 4 * udays + 3;
|
|
|
|
century = u32tmp / 146097;
|
|
|
|
day_of_century = u32tmp % 146097 / 4;
|
|
|
|
|
|
|
|
u32tmp = 4 * day_of_century + 3;
|
|
|
|
u64tmp = 2939745ULL * u32tmp;
|
|
|
|
year_of_century = upper_32_bits(u64tmp);
|
|
|
|
day_of_year = lower_32_bits(u64tmp) / 2939745 / 4;
|
|
|
|
|
|
|
|
year = 100 * century + year_of_century;
|
|
|
|
is_leap_year = year_of_century != 0 ?
|
|
|
|
year_of_century % 4 == 0 : century % 4 == 0;
|
|
|
|
|
|
|
|
u32tmp = 2141 * day_of_year + 132377;
|
|
|
|
month = u32tmp >> 16;
|
|
|
|
day = ((u16) u32tmp) / 2141;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Recall that January 01 is the 306-th day of the year in the
|
|
|
|
* computational (not Gregorian) calendar.
|
|
|
|
*/
|
|
|
|
is_Jan_or_Feb = day_of_year >= 306;
|
|
|
|
|
|
|
|
/* Converts to the Gregorian calendar. */
|
|
|
|
year = year + is_Jan_or_Feb;
|
|
|
|
month = is_Jan_or_Feb ? month - 12 : month;
|
|
|
|
day = day + 1;
|
|
|
|
|
|
|
|
day_of_year = is_Jan_or_Feb ?
|
|
|
|
day_of_year - 306 : day_of_year + 31 + 28 + is_leap_year;
|
|
|
|
|
|
|
|
/* Converts to rtc_time's format. */
|
|
|
|
tm->tm_year = (int) (year - 1900);
|
|
|
|
tm->tm_mon = (int) month;
|
|
|
|
tm->tm_mday = (int) day;
|
|
|
|
tm->tm_yday = (int) day_of_year + 1;
|
2006-03-27 17:16:34 +08:00
|
|
|
|
2014-11-18 19:15:19 +08:00
|
|
|
tm->tm_hour = secs / 3600;
|
|
|
|
secs -= tm->tm_hour * 3600;
|
|
|
|
tm->tm_min = secs / 60;
|
|
|
|
tm->tm_sec = secs - tm->tm_min * 60;
|
2011-08-13 05:04:30 +08:00
|
|
|
|
|
|
|
tm->tm_isdst = 0;
|
2006-03-27 17:16:34 +08:00
|
|
|
}
|
2014-11-18 19:15:19 +08:00
|
|
|
EXPORT_SYMBOL(rtc_time64_to_tm);
|
2006-03-27 17:16:34 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Does the rtc_time represent a valid date/time?
|
|
|
|
*/
|
|
|
|
int rtc_valid_tm(struct rtc_time *tm)
|
|
|
|
{
|
2019-03-20 19:59:09 +08:00
|
|
|
if (tm->tm_year < 70 ||
|
2019-02-15 11:13:59 +08:00
|
|
|
tm->tm_year > (INT_MAX - 1900) ||
|
2019-03-20 19:59:09 +08:00
|
|
|
((unsigned int)tm->tm_mon) >= 12 ||
|
|
|
|
tm->tm_mday < 1 ||
|
|
|
|
tm->tm_mday > rtc_month_days(tm->tm_mon,
|
|
|
|
((unsigned int)tm->tm_year + 1900)) ||
|
|
|
|
((unsigned int)tm->tm_hour) >= 24 ||
|
|
|
|
((unsigned int)tm->tm_min) >= 60 ||
|
|
|
|
((unsigned int)tm->tm_sec) >= 60)
|
2006-03-27 17:16:34 +08:00
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(rtc_valid_tm);
|
|
|
|
|
|
|
|
/*
|
2014-11-18 19:15:19 +08:00
|
|
|
* rtc_tm_to_time64 - Converts rtc_time to time64_t.
|
2006-03-27 17:16:34 +08:00
|
|
|
* Convert Gregorian date to seconds since 01-01-1970 00:00:00.
|
|
|
|
*/
|
2014-11-18 19:15:19 +08:00
|
|
|
time64_t rtc_tm_to_time64(struct rtc_time *tm)
|
2006-03-27 17:16:34 +08:00
|
|
|
{
|
2019-03-20 19:59:09 +08:00
|
|
|
return mktime64(((unsigned int)tm->tm_year + 1900), tm->tm_mon + 1,
|
2018-12-20 17:36:56 +08:00
|
|
|
tm->tm_mday, tm->tm_hour, tm->tm_min, tm->tm_sec);
|
2006-03-27 17:16:34 +08:00
|
|
|
}
|
2014-11-18 19:15:19 +08:00
|
|
|
EXPORT_SYMBOL(rtc_tm_to_time64);
|
2006-03-27 17:16:34 +08:00
|
|
|
|
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
|
|
|
/*
|
|
|
|
* Convert rtc_time to ktime
|
|
|
|
*/
|
|
|
|
ktime_t rtc_tm_to_ktime(struct rtc_time tm)
|
|
|
|
{
|
2014-11-18 19:15:19 +08:00
|
|
|
return ktime_set(rtc_tm_to_time64(&tm), 0);
|
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
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(rtc_tm_to_ktime);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Convert ktime to rtc_time
|
|
|
|
*/
|
|
|
|
struct rtc_time rtc_ktime_to_tm(ktime_t kt)
|
|
|
|
{
|
2014-11-18 19:15:19 +08:00
|
|
|
struct timespec64 ts;
|
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 rtc_time ret;
|
|
|
|
|
2014-11-18 19:15:19 +08:00
|
|
|
ts = ktime_to_timespec64(kt);
|
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
|
|
|
/* Round up any ns */
|
|
|
|
if (ts.tv_nsec)
|
|
|
|
ts.tv_sec++;
|
2014-11-18 19:15:19 +08:00
|
|
|
rtc_time64_to_tm(ts.tv_sec, &ret);
|
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
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(rtc_ktime_to_tm);
|