From: Judith Mendez <jm@ti.com>
To: "Markus Schneider-Pargmann (TI)" <msp@baylibre.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Matthias Schiffer <matthias.schiffer@tq-group.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Julien Panis <jpanis@baylibre.com>,
"Francis, Sebin" <sebin.francis@ti.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] bus: ti-sysc: Don't reserve the system timers on AM33xx
Date: Wed, 4 Nov 2026 09:53:10 -0600 [thread overview]
Message-ID: <bbe7c601-88df-4162-83bc-047b810430a9@ti.com> (raw)
In-Reply-To: <20261103-v7-3-topic-am335lpm-ti-sysc-v1-1-1b9a23b4a7c1@baylibre.com>
Hi Markus
On 11/3/26 7:24 AM, Markus Schneider-Pargmann (TI) wrote:
> Commit
> 3f6178392050 ("ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx")
> introduced handling of am33 SoC timers that are already active as
> reserved. During probe this means the clocks are enabled and a reference
> is kept.
>
> On AM33xx deep sleep is entered by the PM coprocessor which
> requires the PER power domain to be idle. The system timer driver
> disables the clock during suspend but the additional reference held by
> ti-sysc leads to the PER power domain not being idle:
>
> pm33xx pm33xx: PM: Could not transition all powerdomains to target state
>
> The reserved status is only needed where the
> gpt12 system timer must be kept from idling, see commit
> 3ff340e24c9d ("bus: ti-sysc: Fix gpt12 system timer issue with reserved status")
>
> The timer configuration in the devicetree is the same on all SoCs, so
> there is no reason to reserve the timers on AM33xx.
>
> Return -ENODEV for the system timers on all other SoCs. Like -EBUSY it
> stops the probe but the driver core doesn't report it as failure.
>
> Fixes: 3f6178392050 ("ti-sysc: allow OMAP2 and OMAP4 timers to be reserved on AM33xx")
> Cc: stable@vger.kernel.org
> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
Thanks for the patch, tested on various AM3* boards.
Tested-by: Judith Mendez <jm@ti.com>
> ---
> drivers/bus/ti-sysc.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c
> index e118b900c9ac..922a90d4c5a3 100644
> --- a/drivers/bus/ti-sysc.c
> +++ b/drivers/bus/ti-sysc.c
> @@ -48,7 +48,6 @@ enum sysc_soc {
> SOC_UNKNOWN,
> SOC_2420,
> SOC_2430,
> - SOC_AM33,
> SOC_3430,
> SOC_AM35,
> SOC_3630,
> @@ -2917,7 +2916,6 @@ static void ti_sysc_idle(struct work_struct *work)
> static const struct soc_device_attribute sysc_soc_match[] = {
> SOC_FLAG("OMAP242*", SOC_2420),
> SOC_FLAG("OMAP243*", SOC_2430),
> - SOC_FLAG("AM33*", SOC_AM33),
> SOC_FLAG("AM35*", SOC_AM35),
> SOC_FLAG("OMAP3[45]*", SOC_3430),
> SOC_FLAG("OMAP3[67]*", SOC_3630),
> @@ -3124,13 +3122,12 @@ static int sysc_check_active_timer(struct sysc *ddata)
> * A to B4 at some point.
> */
> switch (sysc_soc->soc) {
> - case SOC_AM33:
> case SOC_3430:
> case SOC_AM35:
> error = -ENXIO;
> break;
> default:
> - error = -EBUSY;
> + error = -ENODEV;
> }
>
> if ((ddata->cfg.quirks & SYSC_QUIRK_NO_RESET_ON_INIT) &&
>
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20261030-v7-3-topic-am335lpm-ti-sysc-13f0219c9d67
>
> Best regards,
> --
> Markus Schneider-Pargmann (TI) <msp@baylibre.com>
>
next prev parent reply other threads:[~2026-11-04 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:24 Markus Schneider-Pargmann (TI)
2026-11-04 15:53 ` Judith Mendez [this message]
2026-11-06 11:15 ` Kory Maincent
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=bbe7c601-88df-4162-83bc-047b810430a9@ti.com \
--to=jm@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=alexander.stein@ew.tq-group.com \
--cc=andreas@kemnade.info \
--cc=jpanis@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthias.schiffer@tq-group.com \
--cc=msp@baylibre.com \
--cc=rogerq@kernel.org \
--cc=sebin.francis@ti.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®