Hi Alexandre,
On Wed, Mar 20, 2019 at 12:30 PM Alexandre Belloni
<alexandre.belloni@xxxxxxxxxxx> wrote:
> There is no point in resetting the time to epoch as this means that
> userspace will never get the valuable information that time is actually
> invalid.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx>
Thanks for your patch!
Reviewed-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
Impact before/after (cold boot):
-sh-rtc fcff1000.rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
+sh-rtc fcff1000.rtc: hctosys: unable to read the hardware clock
After warm boot (Linux reboot command):
sh-rtc fcff1000.rtc: setting system clock to 2019-03-21T08:47:54
UTC (1553158074)
After reset (reset switch):
sh-rtc fcff1000.rtc: hctosys: unable to read the hardware clock
Tested-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
