linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Zummo <a.zummo@towertech.it>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 01/13] RTC Subsystem, library functions
Date: Mon, 27 Feb 2006 00:14:39 +0100	[thread overview]
Message-ID: <20060226231438.517421000@towertech.it> (raw)
In-Reply-To: 20060226231438.307751000@towertech.it

[-- Attachment #1: rtc-lib.patch --]
[-- Type: text/plain, Size: 3252 bytes --]

RTC and date/time related functions. 

Signed-off-by: Alessandro Zummo <a.zummo@towertech.it>
---
 lib/Makefile |    2 -
 lib/rtc.c    |   98 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 99 insertions(+), 1 deletion(-)

--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ linux-rtc/lib/rtc.c	2006-02-26 22:03:21.000000000 +0100
@@ -0,0 +1,98 @@
+/*
+ * 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
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; version 2 of the License.
+*/
+
+#include <linux/module.h>
+#include <linux/rtc.h>
+
+static const unsigned char rtc_days_in_month[] = {
+	31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31
+};
+
+#define LEAPS_THRU_END_OF(y) ((y)/4 - (y)/100 + (y)/400)
+#define LEAP_YEAR(year) ((!(year % 4) && (year % 100)) || !(year % 400))
+
+int rtc_month_days(unsigned int month, unsigned int year)
+{
+	return rtc_days_in_month[month] + (LEAP_YEAR(year) && month == 1);
+}
+EXPORT_SYMBOL(rtc_month_days);
+
+/*
+ * Convert seconds since 01-01-1970 00:00:00 to Gregorian date.
+ */
+void rtc_time_to_tm(unsigned long time, struct rtc_time *tm)
+{
+	int days, month, year;
+
+	days = time / 86400;
+	time -= days * 86400;
+
+	tm->tm_wday = (days + 4) % 7;
+
+	year = 1970 + days / 365;
+	days -= (year - 1970) * 365
+	        + LEAPS_THRU_END_OF(year - 1)
+	        - LEAPS_THRU_END_OF(1970 - 1);
+	if (days < 0) {
+		year -= 1;
+		days += 365 + LEAP_YEAR(year);
+	}
+	tm->tm_year = year - 1900;
+	tm->tm_yday = days + 1;
+
+	for (month = 0; month < 11; month++) {
+		int newdays;
+
+		newdays = days - rtc_month_days(month, year);
+		if (newdays < 0)
+			break;
+		days = newdays;
+	}
+	tm->tm_mon = month;
+	tm->tm_mday = days + 1;
+
+	tm->tm_hour = time / 3600;
+	time -= tm->tm_hour * 3600;
+	tm->tm_min = time / 60;
+	tm->tm_sec = time - tm->tm_min * 60;
+}
+EXPORT_SYMBOL(rtc_time_to_tm);
+
+/*
+ * Does the rtc_time represent a valid date/time?
+ */
+int rtc_valid_tm(struct rtc_time *tm)
+{
+	if (tm->tm_year < 70 ||
+	    tm->tm_mon >= 12 ||
+	    tm->tm_mday < 1 ||
+	    tm->tm_mday > rtc_month_days(tm->tm_mon, tm->tm_year + 1900) ||
+	    tm->tm_hour >= 24 ||
+	    tm->tm_min >= 60 ||
+	    tm->tm_sec >= 60)
+		return -EINVAL;
+
+	return 0;
+}
+EXPORT_SYMBOL(rtc_valid_tm);
+
+/*
+ * Convert Gregorian date to seconds since 01-01-1970 00:00:00.
+ */
+int rtc_tm_to_time(struct rtc_time *tm, unsigned long *time)
+{
+	*time = mktime(tm->tm_year + 1900, tm->tm_mon + 1, tm->tm_mday,
+		       tm->tm_hour, tm->tm_min, tm->tm_sec);
+	return 0;
+}
+EXPORT_SYMBOL(rtc_tm_to_time);
--- linux-rtc.orig/lib/Makefile	2006-02-26 21:49:51.000000000 +0100
+++ linux-rtc/lib/Makefile	2006-02-26 21:52:09.000000000 +0100
@@ -5,7 +5,7 @@
 lib-y := errno.o ctype.o string.o vsprintf.o cmdline.o \
 	 bust_spinlocks.o rbtree.o radix-tree.o dump_stack.o \
 	 idr.o div64.o int_sqrt.o bitmap.o extable.o prio_tree.o \
-	 sha1.o
+	 sha1.o rtc.o
 
 lib-y	+= kobject.o kref.o kobject_uevent.o klist.o
 

--

  reply	other threads:[~2006-02-26 23:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-26 23:14 [PATCH 00/13] RTC subsystem Alessandro Zummo
2006-02-26 23:14 ` Alessandro Zummo [this message]
2006-02-26 23:14 ` [PATCH 02/13] RTC subsystem, ARM cleanup Alessandro Zummo
2006-02-26 23:14 ` [PATCH 03/13] RTC subsystem, MIPS cleanup Alessandro Zummo
2006-02-26 23:14 ` [PATCH 04/13] RTC subsystem, class Alessandro Zummo
2006-02-26 23:14 ` [PATCH 05/13] RTC subsystem, I2C cleanup Alessandro Zummo
2006-02-26 23:14 ` [PATCH 06/13] RTC subsystem, sysfs interface Alessandro Zummo
2006-02-26 23:14 ` [PATCH 07/13] RTC subsystem, proc interface Alessandro Zummo
2006-02-26 23:14 ` [PATCH 08/13] RTC subsystem, dev interface Alessandro Zummo
2006-02-26 23:14 ` [PATCH 09/13] RTC subsystem, X1205 driver Alessandro Zummo
2006-02-26 23:14 ` [PATCH 10/13] RTC subsystem, test device/driver Alessandro Zummo
2006-02-26 23:14 ` [PATCH 11/13] RTC subsystem, DS1672 driver Alessandro Zummo
2006-02-26 23:14 ` [PATCH 12/13] RTC subsystem, PCF8563 driver Alessandro Zummo
2006-02-26 23:14 ` [PATCH 13/13] RTC subsystem, RS5C372 driver Alessandro Zummo
2006-03-04 16:42 [PATCH 00/13] RTC subsystem Alessandro Zummo
2006-03-04 16:42 ` [PATCH 01/13] RTC Subsystem, library functions Alessandro Zummo
2006-03-04 16:58   ` Adrian Bunk
2006-03-04 17:12     ` Alessandro Zummo
2006-03-04 17:20       ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060226231438.517421000@towertech.it \
    --to=a.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).