On 01/04/2019 17:07:42+0200, Wolfram Sang wrote: > On Mon, Apr 01, 2019 at 03:39:43PM +0200, Geert Uytterhoeven wrote: > > Hi Wolfram, > > > > On Mon, Apr 1, 2019 at 3:21 PM Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: > > > > I was just wondering whether they work for Wolfram, who has a similar > > > > but different board than I have. Last time I tried, they didn't work for me. > > > > > > How did you test? > > > > tools/testing/selftests/rtc/rtctest.c cfr. > > https://lore.kernel.org/lkml/CAMuHMdWbV2=LfSWz0rFTGRakZ=2iXKOYdM_Uwaov8-OsJpUgoA@xxxxxxxxxxxxxx/ > > Hmm, with vanilla v5.1-rc3, I don't even get that far: > > [==========] Running 7 tests from 2 test cases. > [ RUN ] rtc.date_read > rtctest.c:49:rtc.date_read:Current RTC date/time is 01/01/2000 04:06:40. > [ OK ] rtc.date_read > [ RUN ] rtc.uie_read > > And here it blocks forever. Any pointers? > This means that you don't get any interrupt from your RTC (and that I have to fix the timeout for uie_read). -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
