From: Andre Przywara <andre.przywara@arm.com>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej@kernel.org>,
Samuel Holland <samuel@sholland.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH net 0/2] allwinner: a523: Rename emac0 to gmac0
Date: Sat, 5 Jul 2025 08:36:00 +0100 [thread overview]
Message-ID: <20250705083600.2916bf0c@minigeek.lan> (raw)
In-Reply-To: <20250628054438.2864220-1-wens@kernel.org>
On Sat, 28 Jun 2025 13:44:36 +0800
Chen-Yu Tsai <wens@kernel.org> wrote:
Hi,
> From: Chen-Yu Tsai <wens@csie.org>
>
> Hi folks,
>
> This small series aims to align the name of the first ethernet
> controller found on the Allwinner A523 SoC family with the name
> found in the datasheets. It renames the compatible string and
> any other references from "emac0" to "gmac0".
To be honest I am not a big fan of those cosmetic renames when it
touches DT files. It seems to not break compatibility in this case,
since we don't use the specific compatible string, but leaves a bitter
taste anyway. Also I pick DT patches out of -rc releases for U-Boot,
and did so internally already, so it's not without churns.
So is this really necessary, and what is the purpose of this patch?
I am fine with using GMAC for the GMAC200 part in the SoC, but the A64,
H6, H616, A133 all use the same IP - as the fallback compatible proves -
and they call it all EMAC.
That's not a NAK, but just wanted to bring this up.
Cheers,
Andre.
> When support of the hardware was introduced, the name chosen was
> "EMAC", which followed previous generations. However the datasheets
> use the name "GMAC" instead, likely because there is another "GMAC"
> based on a newer DWMAC IP.
>
> The first patch fixes the compatible string entry in the device tree
> binding.
>
> The second patch fixes all references in the existing device trees.
>
> Since this was introduced in v6.16-rc1, I hope to land this for v6.16
> as well.
>
> There's a small conflict in patch one around the patch context with
>
> dt-bindings: net: sun8i-emac: Add A100 EMAC compatible
>
> that just landed in net-next today. I will leave this patch to the net
> mainainers to merge to avoid making a bigger mess. Once that is landed
> I will merge the second patch through the sunxi tree.
>
>
> Thanks
> ChenYu
>
>
> Chen-Yu Tsai (2):
> dt-bindings: net: sun8i-emac: Rename A523 EMAC0 to GMAC0
> arm64: dts: allwinner: a523: Rename emac0 to gmac0
>
> .../devicetree/bindings/net/allwinner,sun8i-a83t-emac.yaml | 2 +-
> arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi | 6 +++---
> arch/arm64/boot/dts/allwinner/sun55i-a527-cubie-a5e.dts | 4 ++--
> arch/arm64/boot/dts/allwinner/sun55i-t527-avaota-a1.dts | 4 ++--
> 4 files changed, 8 insertions(+), 8 deletions(-)
>
next prev parent reply other threads:[~2025-07-05 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 5:44 [PATCH net 0/2] allwinner: a523: Rename emac0 to gmac0 Chen-Yu Tsai
2025-06-28 5:44 ` [PATCH net 1/2] dt-bindings: net: sun8i-emac: Rename A523 EMAC0 to GMAC0 Chen-Yu Tsai
2025-07-08 12:48 ` Rob Herring (Arm)
2025-06-28 5:44 ` [PATCH net 2/2] arm64: dts: allwinner: a523: Rename emac0 to gmac0 Chen-Yu Tsai
2025-07-05 7:36 ` Andre Przywara [this message]
2025-07-05 12:20 ` [PATCH net 0/2] " Chen-Yu Tsai
2025-07-05 15:53 ` Andrew Lunn
2025-07-05 23:22 ` Andre Przywara
2025-07-06 7:50 ` Andrew Lunn
2025-07-06 13:14 ` Chen-Yu Tsai
2025-07-07 17:15 ` Andre Przywara
2025-07-07 17:34 ` Chen-Yu Tsai
2025-07-08 9:20 ` Paolo Abeni
2025-07-08 15:10 ` patchwork-bot+netdevbpf
2025-07-08 16:25 ` (subset) " Chen-Yu Tsai
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=20250705083600.2916bf0c@minigeek.lan \
--to=andre.przywara@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jernej@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
--cc=wens@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