Dne sobota, 24. avgust 2019 ob 14:56:12 CEST je Ondřej Jirman napisal(a): > Hi, > > On Sat, Aug 24, 2019 at 10:06:14AM +0200, Jernej Škrabec wrote: > > Dne sobota, 24. avgust 2019 ob 10:04:24 CEST je Jernej Škrabec napisal(a): > > > Hi! > > > > > > Dne torek, 20. avgust 2019 ob 17:19:31 CEST je megous@xxxxxxxxxx napisal(a): > > > > From: Ondrej Jirman <megous@xxxxxxxxxx> > > > > > > > > I went through the datasheets for H6 and H5, and compared the > > > > differences. > > > > RTCs are largely similar, but not entirely compatible. > > > > Incompatibilities > > > > are in details not yet implemented by the rtc driver though. > > > > > > > > I also corrected the clock tree in H6 DTSI. > > > > > > > > This patchset is necessary for implementing the WiFi/Bluetooth support > > > > on boards using H6 SoC. > > > > > > > > There was some discussion previously of describing HOSC, DCXO and XO > > > > oscillators and clocks as part of RTC in DT, but I decided against it > > > > because it's not necessary, becuse information that would be provided > > > > as a part of DT can already be determined at runtime from RTC > > > > registers, > > > > so this woudn't add any value and would only introduce complications > > > > to the driver. See: https://patchwork.kernel.org/cover/10898083/ > > > > > > > > Please take a look. > > > > > > > > > > > > Thank you and regards, > > > > > > > > Ondrej Jirman > > > > > > Sorry for a bit late test, but with your patches on Tanix TX6 box I get > > > this in dmesg: > > > > > > [ 17.431742] sun6i-rtc 7000000.rtc: Failed to set rtc time. > > > [ 20.439742] sun6i-rtc 7000000.rtc: rtc is still busy. > > > [ 21.435744] sun6i-rtc 7000000.rtc: rtc is still busy. > > > [ 24.055741] sun6i-rtc 7000000.rtc: rtc is still busy. > > > [ 24.439752] sun6i-rtc 7000000.rtc: rtc is still busy. > > > > > > Last line is repeated non-stop. > > > > > > Any idea what could be wrong? > > > > Additional info - this is on kernel 5.2.6 with your patches applied. > > Do you have schematics, or a FEX file for the board or any other info on how > the RTC is set up on that board? > > Can you dump the RTC register range? I have only Android DT, but as I already said in latest reply to patch 2, changing switch bypass to bit 14 instead of 15 solved all issues. Best regards, Jernej > > regards, > o. > > > Best regards, > > Jernej > > > > > > > > > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
