+Cc Fabio On 09/11/2017 at 09:59:02 +0000, Patrick Brünn wrote: > > >From: Alexandre Belloni [mailto:alexandre.belloni@xxxxxxxxxxxxxxxxxx] > >Sent: Donnerstag, 9. November 2017 04:03 > > > >hwclock times out because the alarm is not working properly. Can you > >check whether rtctest is working? > > > You mean "tools/testing/selftests/timers/rtctest", right? > > I just run it and it's stuck at "Counting 5 update (1/sec) interrupts from reading /dev/rtc0:" > So alarms or interrupts definitively don't work. > Kernel log shows a new message for each try I restart rtctest. > [ 1032.349562] imxdi_rtc 53fa4000.srtc: Write-wait timeout val = 0x5a042418 reg = 0x00000008" > That would explain it because failing to write DCAMR means that the alarm is not set to the proper value. But that doesn't explain all the spurious interrupts you are seeing. Fabio, is there any recent change in the platform code that would make reading/writing the rtc register fail? -- Alexandre Belloni, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
