* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [160108 11:32]: > > Am 08.01.2016 um 20:04 schrieb Tony Lindgren <tony@xxxxxxxxxxx>: > > > * H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [160108 10:33]: > >> Am 08.01.2016 um 19:15 schrieb Tony Lindgren <tony@xxxxxxxxxxx>: > >>> * H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [160108 09:50]: > >>> > >>>> So I think it is something which is unstable in 4.4-rc8 that is (probably) fixed in > >>>> linux-next and unrelated to this DT patch. > >>>> > >>>> But I have no hint or idea what it is. > >>> > >>> Or something hangs the RTC? And the back-up battery has to drain to > >>> reset the RTC somehow? > >> > >> Indeed it could be something like this. I already suspected that it depends > >> on boot order of some components. > >> > >> But you get the /dev/rtc and /sys/class/rtc nodes? This is what this patch > >> should enable (and not fix potential driver issues). > > > > Yes no problems with $subject patch. It's just the we also need > > to figure out why RTC does not work :) > > Yes indeed. I can not focus on that at the moment but as soon as we have > the new Pyra handheld devices (with OMAP5+Palmas) running, there will > be more developers to look at it. OK so the issue is that the twl msecure pin should be high to enable the RTC registers. We used to have that code with platform_data, but no longer have it with device tree based booting. I'll send a patch for that. Curiously setting jumper j5 on beagle-x15 that controls what used to be the msecure and now is powerhold, does the opposite.. The device boots automatically but RTC is stopped? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
