Hello Uwe,
On 23.07.19 21:34, Uwe Kleine-König wrote:
On Tue, Jul 23, 2019 at 09:21:06PM +0200, Oliver Hartkopp wrote:
I think I already solved the problem, see here:
https://marc.info/?l=linux-arm-kernel&m=156390875629259&w=2
IMHO the right fix is teach hwclock to handle your rtc correctly.
Changing the driver from =m to =y is only a workaround.
Agreed.
Maybe also using the time stuff from systemd instead of hwclock will
help^Wwork around your problem (not sure though).
Also I wonder why the ioctl to enable UIE doesn't fail if the driver set
.uie_unsupported (but I didn't look closely).
Right. When executing the ioctl(4, RTC_UIE_ON) syscall it just get's
stuck and the select() timeout captures the call after 10 seconds.
I would have expected that ioctl(4, RTC_UIE_ON) returns with some
-EINVAL or -ENOTSUPP value.
I'm not sure if hwclock needs the trigger for precision reasons:
https://github.com/karelzak/util-linux/blob/master/sys-utils/hwclock.c#L276
... or if this can be omitted.
Will file a Debian bug for it ...
Not sure this will have success. These were switched from =y to =m
because the kernel images got to big.
(https://salsa.debian.org/kernel-team/linux/commit/c55043a43eaacb9f876dabd71273b084cb024441)
Too late ;-)
I will just wait for the answer.
Best regards,
Oliver
