* H. Nikolaus Schaller <h...@goldelico.com> [160106 08:48]: > Hi Tony, > > Am 06.01.2016 um 17:41 schrieb Tony Lindgren <t...@atomide.com>: > > > Hi, > > > > * H. Nikolaus Schaller <h...@goldelico.com> [160106 00:12]: > >> Am 06.01.2016 um 02:00 schrieb Tony Lindgren <t...@atomide.com>: > >>> > >>> Also I'm not seeing just zeroes coming from RTC after typing hwclock > >>> on omap5-uevm. It's working on x15 though. > >>> > >>> Nikolaus, is hwclock command working for you on omap5-uevm? > >> > >> Well, yes and no. It appears it *was* working when tested last time > >> (we sometimes have months of delay for submitting patches upstream). > >> > >> I have found an SD image with 4.3-rc6 with this patch in the dtb and > >> there it works. With 4.4-rc8 it does not work. hwclock command hangs for > >> 10 seconds (I guess some timeout). > >> > >> I have checked the dtb and in both cases it is interrupts = <8 0>; > >> > >> xxd /sys/firmware/devicetree/base/ocp/i2c@48070000/palmas@48/rtc/interrupts > >> 0000000: 0000 0008 0000 0000 > >> > >> So I think something has changed in the rtc driver or somewhere else. > > > > I just gave it a try on v4.3-rc6 with omap5-uevm.dts patched for > > RTC, and I still don't have hwclock working with RTC. > > > > It seems you have some additional patches there that make it work? > > Hm. Not that I am aware of. We just did add the rtc nodes but did not > touch palmas drivers (except adding the gpadc of this patch series).
OK > > I guess it could also be a bootloader change if it's a different > > SD image that works for you. > > Yes, it is using a 2 years old U-Boot instead 2015.10 compiled from > source. I will try to find out if it makes a difference. OK. It could be also some .config change with something built-in? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html