Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCKchanges?

[John Stultz]

On 04/25/2013 12:11 AM, Alexander Holler wrote:
> Am 24.04.2013 18:07, schrieb John Stultz:
>
> > > And why is RTC_SYSTOHC now gone on x86?
> >
> > So summarizing the above, because as much as I'm aware, its always been
> > redundant and unnecessary on x86.  Thus being able at build time to mark
> > it as unnecessary was attractive, since it reduced the code paths
> > running at suspend/resume.
>
> Hmm, I thought RTC_SYSTOHC was there to update the used RTC clock with 
> the time from NTP (and liked that). Therefor I don't understand why it 
> is redundant and unnecessary on x86. Of course, most systems do have 
> something in userspace to set the RTC on shutdown, so it isn't really 
> needed.

Prior to SYSTOHC being introduced, we only synced system time to the RTC 
via update_persistent_clock() on systems that had that interface. 
SYSTOHC is relatively new and lets the system sync to RTCs that don't 
have the persistent clock.

thanks
-john

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/