From: Andreas Kemnade <andreas@kemnade.info>
To: Romain Naour <romain.naour@smile.fr>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
Romain Naour <romain.naour@skf.com>
Subject: Re: [PATCH] bus: ti-sysc: Fix error handling for sysc_check_active_timer() again
Date: Sat, 23 Dec 2023 23:41:02 +0100 [thread overview]
Message-ID: <20231223234102.556eaa07@aktux> (raw)
In-Reply-To: <20231222163710.215362-1-romain.naour@smile.fr>
Hi,
On Fri, 22 Dec 2023 17:37:10 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> From: Romain Naour <romain.naour@skf.com>
>
> sysc_check_active_timer() has been introduced by 6cfcd5563b4f
> ("clocksource/drivers/timer-ti-dm: Fix suspend and resume for am3 and am4")
> and initially returned -EBUSY to ignore timers tagged with no-reset
> and no-idle.
>
> But the return code has been updated from -EBUSY to -ENXIO by
> 65fb73676112 ("bus: ti-sysc: suppress err msg for timers used as clockevent/source")
> and introduced a regression fixed by 06a089ef6449
> ("bus: ti-sysc: Fix error handling for sysc_check_active_timer()")
> since sysc_probe() was still checking for -EBUSY.
>
> Finally the sysc_check_active_timer() return code was reverted
> back to -EBUSY by a12315d6d270
> ("bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific") except
> for SOC_3430.
>
> Now sysc_check_active_timer() may return ENXIO for SOC_3430 and
> EBUSY for all other SoC.
>
> But sysc_probe() still check for -ENXIO leading to the following
> errors in dmesg on AM57xx:
>
> ti-sysc: probe of 4ae18000.target-module failed with error -16 (timer1_target)
> ti-sysc: probe of 4882c000.target-module failed with error -16 (timer15_target)
> ti-sysc: probe of 4882e000.target-module failed with error -16 (timer6_target)
>
> Fix this by checking for both error code...
>
Well, fix what? As long as -EBUSY comes form sysc_check_active_timer(), there
is no problem besides the noise. So clearly state what you want to fix,
so is it only the noise.
Of course I would also like the noise to be gone. I also stumbled across this.
Bringing this to discussion is of course good.
Changing it to -ENXIO has side effects as more lines are executed and the
device is touched although it might be already in use by dmtimer_systimer.
As far as I understand things: there are broken timers, timers used by clocksource
and timers generally useable. And we return -ENXIO for the broken ones... The
main issue here is that this needs more documentation/comments.
I might of course be wrong...
Regards,
Andreas
next prev parent reply other threads:[~2023-12-23 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 16:37 [PATCH] bus: ti-sysc: Fix error handling for sysc_check_active_timer() again Romain Naour
2023-12-23 22:41 ` Andreas Kemnade [this message]
2024-01-19 22:47 ` Romain Naour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231223234102.556eaa07@aktux \
--to=andreas@kemnade.info \
--cc=linux-omap@vger.kernel.org \
--cc=romain.naour@skf.com \
--cc=romain.naour@smile.fr \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox