Am Tue, 31 Oct 2023 09:07:08 +0200
schrieb Tony Lindgren <tony@xxxxxxxxxxx>:
> * Andreas Kemnade <andreas@xxxxxxxxxxxx> [231029 09:13]:
> > I am seeing the error message from $subject on omap4 devices
> > regularly, on omap4430-panda and on the epson bt200 (omap4460).
> > While not having the timer seems not critical in itself. I am
> > wondering whether something nasty is behind it which might cause
> > more severe problems.
> > Is this really seen everywhere?
>
> That should be for gptimer1 that is used as a clocksource by the
> drivers/clocksource/timer-ti-dm-systimer.c driver, and ti-sysc will
> ignore it.
>
hmm, it is about this I think:
timer1_target: target-module@8000 { /* 0x4a318000, ap 9 1c.0
*/ compatible = "ti,sysc-omap2-timer", "ti,sysc";
but I see no ti,no-reset-on-init or ti,no-idle as checked by
sysc_check_active_timer(). It is a bit strange. Well, we have some
alwon below.
It sysc-omap2-timer here right instead of sysc-omap4-timer?
> Maybe we should not show the error for timers, or change it to
> dev_info if EBUSY and timer?
>
Well, I am not sure yet whether I understand that
-ENXIO vs. -EBUSY business there fully.
I want to really have a checkmark behind that issue in my head...
Regards,
Andreas
