From: "Kumar, Udit" <u-kumar1@ti.com>
To: Anurag Dutta <a-dutta@ti.com>, <aaro.koskinen@iki.fi>,
<andreas@kemnade.info>, <khilman@baylibre.com>,
<rogerq@kernel.org>, <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vigneshr@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 1/2] bus: ti-sysc: Add DRA7 SoC matching
Date: Fri, 29 Aug 2025 19:52:02 +0530 [thread overview]
Message-ID: <8259de18-2b5d-4b54-a8ab-f4c3e956b577@ti.com> (raw)
In-Reply-To: <20250829092947.855974-2-a-dutta@ti.com>
On 8/29/2025 2:59 PM, Anurag Dutta wrote:
> From: Sinthu Raja <sinthu.raja@ti.com>
>
> Kernel Commit 25de4ce5ed02 ("clocksource/drivers/timer-ti-dm: Handle
> dra7 timer wrap errata i940") states that "There is a timer wrap issue
> on dra7 and as a work around, we need to use timer-ti-dm percpu timers
> instead. So, configure dmtimer3 and 4 as percpu timers by default." In
> this commit, the author has used ti,no-reset-on-init and ti,no-idle quirks.
>
> The sysc_check_active_timer() checks for these quirks and accordingly,
> returns EBUSY error if the quirks match. Because of this, the timer
> modules fail to probe as can be observed during bootup :"ti-sysc
> 4882c000.target-module: probe with driver ti-sysc failed with error -16"
>
> Return 'ENXIO' instead of 'EBUSY' for DRA7 SoC, so that the error is set
> to ENXIO and the module gets probed under "certain conditions".
Please define, what are "certain conditions".
With addition of conditions in commit message, for this patch
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
>
> Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
> ---
> drivers/bus/ti-sysc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c
> index 5566ad11399e..90766f804706 100644
> --- a/drivers/bus/ti-sysc.c
> +++ b/drivers/bus/ti-sysc.c
> @@ -3117,7 +3117,8 @@ static int sysc_check_active_timer(struct sysc *ddata)
> * can be dropped if we stop supporting old beagleboard revisions
> * A to B4 at some point.
> */
> - if (sysc_soc->soc == SOC_3430 || sysc_soc->soc == SOC_AM35)
> + if (sysc_soc->soc == SOC_3430 || sysc_soc->soc == SOC_AM35 ||
> + sysc_soc->soc == SOC_DRA7)
> error = -ENXIO;
> else
> error = -EBUSY;
next prev parent reply other threads:[~2025-08-29 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 9:29 [PATCH 0/2] AM57 timer fixes Anurag Dutta
2025-08-29 9:29 ` [PATCH 1/2] bus: ti-sysc: Add DRA7 SoC matching Anurag Dutta
2025-08-29 14:22 ` Kumar, Udit [this message]
2025-08-29 9:29 ` [PATCH 2/2] arm: dts: Use DMTimer as Clocksource instead of counter_32k Anurag Dutta
2025-08-29 14:25 ` Kumar, Udit
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=8259de18-2b5d-4b54-a8ab-f4c3e956b577@ti.com \
--to=u-kumar1@ti.com \
--cc=a-dutta@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®