diff options
author | Adam Ford <aford173@gmail.com> | 2023-09-06 18:34:42 -0500 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2023-09-11 06:04:17 +0300 |
commit | 11729caa520950e17cd81bc43ffc477c46cf791e (patch) | |
tree | 08e0bbe6b4b45199d4847441d81b9bc5fc35ec59 /init/Makefile | |
parent | d929b2b7464f95ec01e47f560b1e687482ba8929 (diff) | |
download | linux-11729caa520950e17cd81bc43ffc477c46cf791e.tar.gz linux-11729caa520950e17cd81bc43ffc477c46cf791e.tar.bz2 linux-11729caa520950e17cd81bc43ffc477c46cf791e.zip |
bus: ti-sysc: Fix missing AM35xx SoC matching
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")
Signed-off-by: Adam Ford <aford173@gmail.com>
Message-ID: <20230906233442.270835-1-aford173@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'init/Makefile')
0 files changed, 0 insertions, 0 deletions