From: Matthias Brugger <matthias.bgg@gmail.com>
To: Biao Huang <biao.huang@mediatek.com>,
davem@davemloft.net, Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
srv_heupstream@mediatek.com, macpaul.lin@mediatek.com,
angelogioacchino.delregno@collabora.com, dkirjanov@suse.de
Subject: Re: [PATCH net-next v8 3/6] arm64: dts: mt2712: update ethernet device node
Date: Wed, 15 Dec 2021 20:22:57 +0100 [thread overview]
Message-ID: <c9b3d31a-1c18-32ec-8077-603bb93fe8d0@gmail.com> (raw)
In-Reply-To: <20211210013129.811-4-biao.huang@mediatek.com>
On 10/12/2021 02:31, Biao Huang wrote:
> Since there are some changes in ethernet driver,
> update ethernet device node in dts to accommodate to it.
>
I have a hard time to understand how the first two patches are related to this
one. Please be more specific in your commit message.
Also please beware that we should make sure that a newer driver version should
still work properly with an older device tree, which does not have your changes.
Regards,
Matthias
> Signed-off-by: Biao Huang <biao.huang@mediatek.com>
> ---
> arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 1 +
> arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 14 +++++++++-----
> 2 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt2712-evb.dts b/arch/arm64/boot/dts/mediatek/mt2712-evb.dts
> index 7d369fdd3117..11aa135aa0f3 100644
> --- a/arch/arm64/boot/dts/mediatek/mt2712-evb.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt2712-evb.dts
> @@ -110,6 +110,7 @@ ð {
> phy-handle = <ðernet_phy0>;
> mediatek,tx-delay-ps = <1530>;
> snps,reset-gpio = <&pio 87 GPIO_ACTIVE_LOW>;
> + snps,reset-delays-us = <0 10000 10000>;
> pinctrl-names = "default", "sleep";
> pinctrl-0 = <ð_default>;
> pinctrl-1 = <ð_sleep>;
> diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
> index a9cca9c146fd..9e850e04fffb 100644
> --- a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
> @@ -726,7 +726,7 @@ queue2 {
> };
>
> eth: ethernet@1101c000 {
> - compatible = "mediatek,mt2712-gmac";
> + compatible = "mediatek,mt2712-gmac", "snps,dwmac-4.20a";
> reg = <0 0x1101c000 0 0x1300>;
> interrupts = <GIC_SPI 237 IRQ_TYPE_LEVEL_LOW>;
> interrupt-names = "macirq";
> @@ -734,15 +734,19 @@ eth: ethernet@1101c000 {
> clock-names = "axi",
> "apb",
> "mac_main",
> - "ptp_ref";
> + "ptp_ref",
> + "rmii_internal";
> clocks = <&pericfg CLK_PERI_GMAC>,
> <&pericfg CLK_PERI_GMAC_PCLK>,
> <&topckgen CLK_TOP_ETHER_125M_SEL>,
> - <&topckgen CLK_TOP_ETHER_50M_SEL>;
> + <&topckgen CLK_TOP_ETHER_50M_SEL>,
> + <&topckgen CLK_TOP_ETHER_50M_RMII_SEL>;
> assigned-clocks = <&topckgen CLK_TOP_ETHER_125M_SEL>,
> - <&topckgen CLK_TOP_ETHER_50M_SEL>;
> + <&topckgen CLK_TOP_ETHER_50M_SEL>,
> + <&topckgen CLK_TOP_ETHER_50M_RMII_SEL>;
> assigned-clock-parents = <&topckgen CLK_TOP_ETHERPLL_125M>,
> - <&topckgen CLK_TOP_APLL1_D3>;
> + <&topckgen CLK_TOP_APLL1_D3>,
> + <&topckgen CLK_TOP_ETHERPLL_50M>;
> power-domains = <&scpsys MT2712_POWER_DOMAIN_AUDIO>;
> mediatek,pericfg = <&pericfg>;
> snps,axi-config = <&stmmac_axi_setup>;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-15 19:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 1:31 [PATCH net-next v8 0/6] MediaTek Ethernet Patches on MT8195 Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 1/6] stmmac: dwmac-mediatek: add platform level clocks management Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 2/6] stmmac: dwmac-mediatek: Reuse more common features Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 3/6] arm64: dts: mt2712: update ethernet device node Biao Huang
2021-12-15 19:20 ` Matthias Brugger
2021-12-16 9:19 ` Biao Huang
2021-12-15 19:22 ` Matthias Brugger [this message]
2021-12-16 1:28 ` Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 4/6] net: dt-bindings: dwmac: Convert mediatek-dwmac to DT schema Biao Huang
2021-12-10 14:02 ` Rob Herring
2021-12-10 18:49 ` Rob Herring
2021-12-13 1:34 ` Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 5/6] stmmac: dwmac-mediatek: add support for mt8195 Biao Huang
2021-12-10 1:31 ` [PATCH net-next v8 6/6] net: dt-bindings: dwmac: " Biao Huang
2021-12-10 14:02 ` Rob Herring
2021-12-10 18:52 ` Rob Herring
2021-12-13 1:27 ` Biao Huang
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=c9b3d31a-1c18-32ec-8077-603bb93fe8d0@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=biao.huang@mediatek.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dkirjanov@suse.de \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=macpaul.lin@mediatek.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).