Messages in this thread | | | Date | Tue, 21 May 2013 14:42:25 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 3/4] rtc: rtc-hid-sensor-time: add option hctosys to set time at boot |
| |
On Sun, 5 May 2013 13:21:26 +0200 Alexander Holler <holler@ahsoftware.de> wrote:
> drivers/rtc/hctosys (CONFIG_RTC_HCTOSYS) doesn't work for > rtc-hid-sensor-time because it will be called in late_init, and thus before > rtc-hid-sensor-time gets loaded. To set the time through > rtc-hid-sensor-time at startup, the module now checks by default if the > system time is before 1970-01-02 and sets the system time (once) if this is > the case. > > To disable this behaviour, set the module option hctosys to zero, e.g. by > using rtc-hid-sensor-time.hctosys=0 at the kernel command line if the > driver is statically linked into the kernel.
I still find this rather unpleasant. Partly because it's hacky, mainly because it only solves the problem for one driver.
Can we please try harder to find a more general fix?
For example: if hctosys finds there are no drivers available, it sets a flag. Later when drivers are registered(?), that flag is queried and, if set, we set the system time at this time.
Or something.
| |