From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org, aford@beaconembedded.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bus: ti-sysc: Fix missing AM35xx SoC matching
Date: Wed, 6 Sep 2023 14:03:37 +0300 [thread overview]
Message-ID: <20230906110337.GC11676@atomide.com> (raw)
In-Reply-To: <20230906093244.99292-1-aford173@gmail.com>
* Adam Ford <aford173@gmail.com> [230906 12:33]:
> Fix this by treating the AM35xx as a SOC_3430, and the error
> conditions will disappear.
Looks good to me except let's just add SOC_AM35 to enum sysc_soc rather
than tag am3517 with SOC_3430. We already have checks for SOC_3430 for
several devices and the quirks may not be compatible across AM35 and 3430.
Regards,
Tony
prev parent reply other threads:[~2023-09-06 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:32 [PATCH] bus: ti-sysc: Fix missing AM35xx SoC matching Adam Ford
2023-09-06 11:03 ` Tony Lindgren [this message]
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=20230906110337.GC11676@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).