Bug#932845: TS-219 RTC issue with Debian Buster

[Oliver Hartkopp <socketcan@hartkopp.net>]

Just a thought:

There are some of these rtc drivers that set

rtc->rtc->uie_unsupported = 1;

in the case that they can't assign an irq line.

But others set

rtc->rtc->uie_unsupported = 1;

when they don't support an (alarm) trigger with 1 sec accuracy.

Wouldn't it make sense to put

+       select RTC_INTF_DEV
+       select RTC_INTF_DEV_UIE_EMUL

in the Kconfig entries of the latter devices?

Best regards,
Oliver


On 26.07.19 12:26, Oliver Hartkopp wrote:
> Hello Alexandre,
>
> On 26.07.19 11:39, Alexandre Belloni wrote:
>
> > > > > Maybe this problem is only relevant for the S35390A and PCF8563 
> > > > > chip which
> > > > > both lack the UIE support needed by hwclock. Both have only alarm 
> > > > > triggers
> > > > > in a minute accuracy according to the driver source code.
> > > >
> > > > AFAIK the rtc framework should then emulate this event somehow.
> > >
> > > I don't think so. When the rtc chip is not able to trigger an event 
> > > with a
> > > one second resolution - how can you emulate that?
> >
> > CONFIG_RTC_INTF_DEV_UIE_EMUL emulates it by polling the RTC.
>
> Just booted my NAS box and /boot/config-4.19.0-5-marvell contains
>
> # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
>
> Would be cool when this would make hwclock happy.
>
> Best regards,
> Oliver