From: yangshiji66@outlook.com
To: sergio.paracuellos@gmail.com
Cc: arinc.unal@arinc9.com, devicetree@vger.kernel.org,
john@phrozen.org, krzysztof.kozlowski+dt@linaro.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, matthias.bgg@gmail.com,
mturquette@baylibre.com, p.zabel@pengutronix.de,
robh+dt@kernel.org, sboyd@kernel.org, tsbogend@alpha.franken.de
Subject: Re: [PATCH v3 2/9] clk: ralink: add clock and reset driver for MTMIPS SoCs
Date: Sat, 17 Jun 2023 12:51:13 +0800 [thread overview]
Message-ID: <TYAP286MB0315C35BA080B686EB5EA980BC59A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230418090312.2818879-3-sergio.paracuellos@gmail.com>
Thank you for taking care of these old amazing SoCs. When I ported these
patches to OpenWrt, I found some issues.
>+
>+static const struct of_device_id mtmips_of_match[] = {
>+ {
>+ .compatible = "ralink,rt2880-sysc",
>+ .data = &rt2880_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,rt3050-sysc",
>+ .data = &rt3050_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,rt3052-sysc",
>+ .data = &rt3052_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,rt3352-sysc",
>+ .data = &rt3052_clk_data,
It seems that there should be `.data = &rt3352_clk_data,`?
>+ },
>+ {
>+ .compatible = "ralink,rt3883-sysc",
>+ .data = &rt3352_clk_data,
>+ },
And there should be `.data = &rt3883_clk_data,`?
>+ {
>+ .compatible = "ralink,rt5350-sysc",
>+ .data = &rt5350_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,mt7620a-sysc",
>+ .data = &mt7620_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,mt7620-sysc",
>+ .data = &mt7620_clk_data,
>+ },
>+ {
I am confused about the difference between `ralink,mt7620-sysc` and
`ralink,mt7620a-sysc`. Do you mean mt7620n?
https://www.mediatek.com/products/home-networking/mt7620n-a
>+ .compatible = "ralink,mt7628-sysc",
>+ .data = &mt76x8_clk_data,
>+ },
>+ {
>+ .compatible = "ralink,mt7688-sysc",
>+ .data = &mt76x8_clk_data,
>+ },
>+ {}
>+};
>+
Thanks,
Shiji Yang
next prev parent reply other threads:[~2023-06-17 4:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 9:03 [PATCH v3 0/9] mips: ralink: add complete clock and reset driver for mtmips SoCs Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 1/9] dt-bindings: clock: add mtmips SoCs system controller Sergio Paracuellos
2023-04-21 18:00 ` Rob Herring
2023-06-16 18:03 ` Stephen Boyd
2023-04-18 9:03 ` [PATCH v3 2/9] clk: ralink: add clock and reset driver for MTMIPS SoCs Sergio Paracuellos
2023-06-16 18:03 ` Stephen Boyd
2023-06-17 4:51 ` yangshiji66 [this message]
2023-06-17 5:06 ` Sergio Paracuellos
2023-06-17 5:50 ` Shiji Yang
2023-06-17 6:00 ` Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 3/9] mips: ralink: rt288x: remove clock related code Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 4/9] mips: ralink: rt305x: " Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 5/9] mips: ralink: rt3883: " Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 6/9] mips: ralink: mt7620: " Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 7/9] mips: ralink: remove reset " Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 8/9] mips: ralink: get cpu rate from new driver code Sergio Paracuellos
2023-04-18 9:03 ` [PATCH v3 9/9] MAINTAINERS: add Mediatek MTMIPS Clock maintainer Sergio Paracuellos
2023-05-04 14:48 ` [PATCH v3 0/9] mips: ralink: add complete clock and reset driver for mtmips SoCs Sergio Paracuellos
2023-05-23 9:47 ` Sergio Paracuellos
2023-06-16 6:12 ` Sergio Paracuellos
2023-06-16 6:47 ` Thomas Bogendoerfer
2023-06-17 5:24 [PATCH v4 2/9] clk: ralink: add clock and reset driver for MTMIPS SoCs Sergio Paracuellos
2023-06-17 12:54 ` [PATCH v3 " Shiji Yang
2023-06-17 13:07 ` Krzysztof Kozlowski
2023-06-17 13:31 ` Sergio Paracuellos
2023-06-17 14:43 ` Krzysztof Kozlowski
2023-06-17 15:37 ` Sergio Paracuellos
2023-06-17 17:20 ` Krzysztof Kozlowski
2023-06-17 19:11 ` Sergio Paracuellos
2023-06-18 5:04 ` Sergio Paracuellos
2023-06-17 13:26 ` Sergio Paracuellos
2023-06-17 14:43 ` Krzysztof Kozlowski
2023-06-17 15:31 ` Sergio Paracuellos
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=TYAP286MB0315C35BA080B686EB5EA980BC59A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM \
--to=yangshiji66@outlook.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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
Powered by JetHome