From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Shiji Yang <yangshiji66@outlook.com>
Cc: linux-mips@vger.kernel.org, John Crispin <john@phrozen.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: ralink: match all supported system controller compatible strings
Date: Fri, 23 Jun 2023 15:08:57 +0200 [thread overview]
Message-ID: <20230623130856.GA11636@alpha.franken.de> (raw)
In-Reply-To: <TYAP286MB03151148AF8C054621DD55C3BC23A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
On Fri, Jun 23, 2023 at 08:17:48AM +0800, Shiji Yang wrote:
> Recently, A new clock and reset controller driver has been introduced to
> the ralink mips target[1]. It provides proper system control and adds more
> SoC specific compatible strings. In order to better initialize CPUs, this
> patch removes the outdated "ralink,mt7620a-sysc" and add all dt-binding
> documented compatible strings to the system controller match table.
>
> [1] https://lore.kernel.org/all/20230619040941.1340372-1-sergio.paracuellos@gmail.com/
>
> Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
> ---
> arch/mips/ralink/of.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/ralink/of.c b/arch/mips/ralink/of.c
> index 53a2ae9ee..1c6c953d5 100644
> --- a/arch/mips/ralink/of.c
> +++ b/arch/mips/ralink/of.c
> @@ -40,10 +40,15 @@ static const struct of_device_id mtmips_memc_match[] = {
>
> static const struct of_device_id mtmips_sysc_match[] = {
> { .compatible = "mediatek,mt7621-sysc" },
> - { .compatible = "ralink,mt7620a-sysc" },
> + { .compatible = "ralink,mt7620-sysc" },
> + { .compatible = "ralink,mt7628-sysc" },
> + { .compatible = "ralink,mt7688-sysc" },
> { .compatible = "ralink,rt2880-sysc" },
> { .compatible = "ralink,rt3050-sysc" },
> + { .compatible = "ralink,rt3052-sysc" },
> + { .compatible = "ralink,rt3352-sysc" },
> { .compatible = "ralink,rt3883-sysc" },
> + { .compatible = "ralink,rt5350-sysc" },
> {}
> };
>
> --
> 2.30.2
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-06-23 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 0:17 [PATCH] mips: ralink: match all supported system controller compatible strings Shiji Yang
2023-06-23 3:49 ` Sergio Paracuellos
2023-06-23 13:08 ` Thomas Bogendoerfer [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=20230623130856.GA11636@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=yangshiji66@outlook.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