Signed-off-by: Feng Tang <[email protected]>
---
drivers/rtc/rtc-mrst.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/rtc/rtc-mrst.c b/drivers/rtc/rtc-mrst.c
index 85f97dc..93914ec 100644
--- a/drivers/rtc/rtc-mrst.c
+++ b/drivers/rtc/rtc-mrst.c
@@ -70,7 +70,11 @@ static inline int is_intr(u8 rtc_intr)
* rtc_time's year contains the increment over 1900, but vRTC's YEAR
* register can't be programmed to value larger than 0x64, so vRTC
* driver chose to use 1960 (1970 is UNIX time start point) as the base,
- * and do the translation in read/write time
+ * and do the translation in read/write time.
+ *
+ * Why not just using 1970 as the offset? it's because using 1960 will
+ * make it consisten in Leap year setting for both vrtc and low-level
+ * physical rtc devices.
*/
static int mrst_read_time(struct device *dev, struct rtc_time *time)
{
--
1.7.0.4
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel