From: Roger Quadros <rogerq@kernel.org>
To: Francesco Valla <francesco@valla.it>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Tony Lindgren <tony@atomide.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] bus: ti-sysc: mark AM62 wkup_uart0 as non deferrable
Date: Mon, 13 Jan 2025 20:08:43 +0200 [thread overview]
Message-ID: <25491f79-323b-421f-8053-36d5655e5323@kernel.org> (raw)
In-Reply-To: <20250109175211.113945-2-francesco@valla.it>
On 09/01/2025 19:52, Francesco Valla wrote:
> The ti-sysc driver implements a probe deferral logic to be sure to probe
> the parent interconnects before their children, postponing the probe of
> interconnects not marked as "early" instances until one of these is
> found.
>
> Since the driver is alse used for the wkup_uart0 block found on the AM62
alse/also
> SoC, but not for other devices on the same platform, this logic forces
> the probe for it to be artificially deferred 10 times and can lead to
> the device not being probed at all. The missed probe was seen on a
> BeaglePlay with the kernel configuration stripped to bare minimum and
> no module support.
>
> Add the ranges for wkup_uart0 to the list of "early" interconnect
> instances, forcing the driver to skip the defer logic entirely for this
> device.
>
> Signed-off-by: Francesco Valla <francesco@valla.it>
> ---
> drivers/bus/ti-sysc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c
> index f67b927ae4ca..917b7168fbd0 100644
> --- a/drivers/bus/ti-sysc.c
> +++ b/drivers/bus/ti-sysc.c
> @@ -687,6 +687,8 @@ static struct resource early_bus_ranges[] = {
> { .start = 0x4a300000, .end = 0x4a300000 + 0x30000, },
> /* omap5 and dra7 l4_wkup without dra7 dcan segment */
> { .start = 0x4ae00000, .end = 0x4ae00000 + 0x30000, },
> + /* am62 wkup_uart0 */
> + { .start = 0x2b300000, .end = 0x2b300000 + 0x100000, },
> };
>
> static atomic_t sysc_defer = ATOMIC_INIT(10);
While this is probably OK for now, we need to ensure that sysc_defer_non_critical()
is not called for such devices that don't have an interconnect managed by
the sysc driver (i.e. non OMAP based systems).
Maybe this calls for a new compatible for AM62 sysc?
Reviewed-by: Roger Quadros <rogerq@kernel.org>
--
cheers,
-roger
next prev parent reply other threads:[~2025-01-13 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 17:52 [PATCH] bus: ti-sysc: mark AM62 wkup_uart0 as non deferrable Francesco Valla
2025-01-13 18:08 ` Roger Quadros [this message]
2025-01-16 13:14 ` Francesco Valla
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=25491f79-323b-421f-8053-36d5655e5323@kernel.org \
--to=rogerq@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=francesco@valla.it \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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