Re: TS-219 RTC issue with Debian Buster

[Andrew Lunn <andrew@lunn.ch>]

On Tue, Jul 23, 2019 at 08:30:45PM +0200, Oliver Hartkopp wrote:
> Sorry for answering myself again ..
> 
> After installing the 4.9.0-4-marvell kernel (from old stable Stretch) on my
> Debian Buster system it works like before:
> 
> [    1.101214] mousedev: PS/2 mouse device common for all mice
> [    2.123021] rtc-mv f1010300.rtc: internal RTC not ticking
> [    2.128592] i2c /dev entries driver
> [    2.133933] random: fast init done
> [    2.137746] rtc-s35390a 0-0030: rtc core: registered rtc-s35390a as rtc0
> [    2.145186] ledtrig-cpu: registered to indicate activity on CPUs
> [    2.151518] NET: Registered protocol family 17
> [    2.156398] registered taskstats version 1
> [    2.160561] zswap: loaded using pool lzo/zbud
> [    2.165913] rtc-s35390a 0-0030: setting system clock to 2019-07-23
> 18:16:18 UTC (1563905778)
> [    2.175514] Freeing unused kernel memory: 296K

So your system has two RTC drivers loading. First rtc-mv tries to
load, but it finds the RTC is not ticking. This often happens with
Kirkwood. Some vendors decided not to use the internal RTC. But the
default device tree has it enabled, so the driver loads. When it pokes
the hardware it discovers the clock is stopped and so the driver fails
the problem.

Later the i2c RTC loads, which does work.

So one step is to change the DT to disable the internal RTC.
You can add:
                rtc@10300 {
                        status = "disabled";
                };

	Andrew

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel