12-18-2019, 01:31 PM
(12-18-2019, 12:06 PM)tsys Wrote: I saw someone mention that problem on the Dicord the other day.
I've just looked at it. First and foremost the IRQ GPIO of the pmic is just wrong which will prevent pretty much all read operations on the RTC from succeeding. I've fixed that.
Thank you for fixing it!
(12-18-2019, 12:06 PM)tsys Wrote: The broken load order of the rtc subsystem is probably an issue, too though. Imho hctosys is missing a mechanism to defer loading unti the rtc dev appears. Adding the RTC module as a builtin does result in the correct load order since it uses a late initcall. I'm not sure I like that solution though.
I was suggesting the builtin route, because it follows the same solution path that CMOS RTC is doing on PC-compatible class hardware.
But if you prefer not to do it, then the best strategy would be to use UDEV rules to manually call the hctosys, or compile *that* one as module (is it possible) and load the module right after /dev/rtc0 shows up (again, courtesy of some udev rule).
It's basically way to force the *deferring until rtc dev appears* part.