[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230913082551.GF5285@atomide.com>
Date: Wed, 13 Sep 2023 11:25:51 +0300
From: Tony Lindgren <tony@...mide.com>
To: Adam Ford <aford173@...il.com>
Cc: linux-omap@...r.kernel.org, aford@...conembedded.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] bus: ti-sysc: Fix missing AM35xx SoC matching
* Adam Ford <aford173@...il.com> [230907 02:34]:
> Commit feaa8baee82a ("bus: ti-sysc: Implement SoC revision handling")
> created a list of SoC types searching for strings based on names
> and wildcards which associates the SoC to different families.
>
> The OMAP34xx and OMAP35xx are treated as SOC_3430 while
> OMAP36xx and OMAP37xx are treated as SOC_3630, but the AM35xx
> isn't listed.
>
> The AM35xx is mostly an OMAP3430, and a later commit a12315d6d270
> ("bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific") looks
> for the SOC type and behaves in a certain way if it's SOC_3430.
>
> This caused a regression on the AM3517 causing it to return two
> errors:
>
> ti-sysc: probe of 48318000.target-module failed with error -16
> ti-sysc: probe of 49032000.target-module failed with error -16
>
> Fix this by treating the creating SOC_AM35 and inserting it between
> the SOC_3430 and SOC_3630. If it is treaed the same way as the
> SOC_3430 when checking the status of sysc_check_active_timer,
> the error conditions will disappear.
>
> Fixes: a12315d6d270 ("bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific")
> Fixes: feaa8baee82a ("bus: ti-sysc: Implement SoC revision handling")
Applied into fixes now, thanks
Tony
Powered by blists - more mailing lists