Doug / smarc-fsl-linux-kernel

Download as
Browse Code ยป

Commit d3e1884bc585a43674d2cb0d3f0aeeb0ae43bc04

Authored by Feng Tang
Committed by Thomas Gleixner
1 parent ad02519a0d
Exists in master and in 7 other branches imx_3.0.35_4.1.0, imx_3.10.17_1.0.1_ga, imx_3.10.53_1.1.0_ga, imx_3.14.28_1.0.0_ga, smarc-imx_3.10.53_1.1.0_ga, smarc-imx_3.14.28_1.0.0_ga, smarc-l5.0.0_1.0.0-ga

x86, mrst: Add explanation for using 1960 as the year offset for vrtc 

Explain the reason for the apparently odd choice of year offset so we don't
get more questions about it.

Signed-off-by: Feng Tang <feng.tang@intel.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
LKML-Reference: <20101117121050.9998.89348.stgit@localhost.localdomain>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Showing 1 changed file with 5 additions and 1 deletions Side-by-side Diff

drivers/rtc/rtc-mrst.c
Diff comments   View file @ d3e1884
... ... @@ -66,7 +66,11 @@
66 66 * rtc_time's year contains the increment over 1900, but vRTC's YEAR
67 67 * register can't be programmed to value larger than 0x64, so vRTC
68 68 * driver chose to use 1960 (1970 is UNIX time start point) as the base,
69   - * and does the translation at read/write time
  69 + * and does the translation at read/write time.
  70 + *
  71 + * Why not just use 1970 as the offset? it's because using 1960 will
  72 + * make it consistent in leap year setting for both vrtc and low-level
  73 + * physical rtc devices.
70 74 */
71 75 static int mrst_read_time(struct device *dev, struct rtc_time *time)
72 76 {