From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Inochi Amaoto" <inochiama@gmail.com>,
"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 Wang" <unicorn_wang@outlook.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Jan Petrous (OSS)" <jan.petrous@oss.nxp.com>,
"Hariprasad Kelam" <hkelam@marvell.com>,
"Clément Léger" <clement.leger@bootlin.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Emil Renner Berthing" <emil.renner.berthing@canonical.com>,
"Drew Fustini" <dfustini@tenstorrent.com>,
"Furong Xu" <0x1207@gmail.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Joe Hattori" <joe@pf.is.s.u-tokyo.ac.jp>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Lothar Rubusch" <l.rubusch@gmail.com>,
"Giuseppe Cavallaro" <peppe.cavallaro@st.com>,
"Jose Abreu" <joabreu@synopsys.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sophgo@lists.linux.dev,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, "Yixun Lan" <dlan@gentoo.org>,
"Longbin Li" <looong.bin@gmail.com>
Subject: Re: [PATCH net-next v5 3/3] net: stmmac: Add glue layer for Sophgo SG2044 SoC
Date: Mon, 17 Feb 2025 14:10:50 +0000 [thread overview]
Message-ID: <Z7NDakd7zpQ_345D@shell.armlinux.org.uk> (raw)
In-Reply-To: <24eecc48-9061-4575-9e3b-6ef35226407a@lunn.ch>
On Mon, Feb 17, 2025 at 02:25:33PM +0100, Andrew Lunn wrote:
> > I am not sure all whether devices has this clock, but it appears in
> > the databook. So I think it is possible to move this in the core so
> > any platform with these clock can reuse it.
>
> Great
>
> The next problem will be, has everybody called it the same thing in
> DT. Since there has been a lot of cut/paste, maybe they have, by
> accident.
Tegra186: "tx"
imx: "tx"
intel: "tx_clk"
rk: "clk_mac_speed"
s32: "tx"
starfive: "tx"
sti: "sti-ethclk"
so 50% have settled on "tx" and the rest are doing their own thing, and
that horse has already bolted.
I have some ideas on sorting this out, and I'm working on some patches
today.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Inochi Amaoto" <inochiama@gmail.com>,
"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 Wang" <unicorn_wang@outlook.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Jan Petrous (OSS)" <jan.petrous@oss.nxp.com>,
"Hariprasad Kelam" <hkelam@marvell.com>,
"Clément Léger" <clement.leger@bootlin.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Emil Renner Berthing" <emil.renner.berthing@canonical.com>,
"Drew Fustini" <dfustini@tenstorrent.com>,
"Furong Xu" <0x1207@gmail.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Joe Hattori" <joe@pf.is.s.u-tokyo.ac.jp>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Lothar Rubusch" <l.rubusch@gmail.com>,
"Giuseppe Cavallaro" <peppe.cavallaro@st.com>,
"Jose Abreu" <joabreu@synopsys.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sophgo@lists.linux.dev,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, "Yixun Lan" <dlan@gentoo.org>,
"Longbin Li" <looong.bin@gmail.com>
Subject: Re: [PATCH net-next v5 3/3] net: stmmac: Add glue layer for Sophgo SG2044 SoC
Date: Mon, 17 Feb 2025 14:10:50 +0000 [thread overview]
Message-ID: <Z7NDakd7zpQ_345D@shell.armlinux.org.uk> (raw)
In-Reply-To: <24eecc48-9061-4575-9e3b-6ef35226407a@lunn.ch>
On Mon, Feb 17, 2025 at 02:25:33PM +0100, Andrew Lunn wrote:
> > I am not sure all whether devices has this clock, but it appears in
> > the databook. So I think it is possible to move this in the core so
> > any platform with these clock can reuse it.
>
> Great
>
> The next problem will be, has everybody called it the same thing in
> DT. Since there has been a lot of cut/paste, maybe they have, by
> accident.
Tegra186: "tx"
imx: "tx"
intel: "tx_clk"
rk: "clk_mac_speed"
s32: "tx"
starfive: "tx"
sti: "sti-ethclk"
so 50% have settled on "tx" and the rest are doing their own thing, and
that horse has already bolted.
I have some ideas on sorting this out, and I'm working on some patches
today.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-02-17 14:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 12:39 [PATCH net-next v5 0/3] riscv: sophgo: Add ethernet support for SG2044 Inochi Amaoto
2025-02-16 12:39 ` Inochi Amaoto
2025-02-16 12:39 ` [PATCH net-next v5 1/3] dt-bindings: net: Add support for Sophgo SG2044 dwmac Inochi Amaoto
2025-02-16 12:39 ` Inochi Amaoto
2025-02-16 12:39 ` [PATCH net-next v5 2/3] net: stmmac: platform: Add snps,dwmac-5.30a IP compatible string Inochi Amaoto
2025-02-16 12:39 ` Inochi Amaoto
2025-02-16 16:59 ` Andrew Lunn
2025-02-16 16:59 ` Andrew Lunn
2025-02-17 0:55 ` Inochi Amaoto
2025-02-17 0:55 ` Inochi Amaoto
2025-02-16 12:39 ` [PATCH net-next v5 3/3] net: stmmac: Add glue layer for Sophgo SG2044 SoC Inochi Amaoto
2025-02-16 12:39 ` Inochi Amaoto
2025-02-16 15:47 ` Russell King (Oracle)
2025-02-16 15:47 ` Russell King (Oracle)
2025-02-16 17:07 ` Andrew Lunn
2025-02-16 17:07 ` Andrew Lunn
2025-02-17 4:16 ` Inochi Amaoto
2025-02-17 4:16 ` Inochi Amaoto
2025-02-17 13:25 ` Andrew Lunn
2025-02-17 13:25 ` Andrew Lunn
2025-02-17 14:10 ` Russell King (Oracle) [this message]
2025-02-17 14:10 ` Russell King (Oracle)
2025-02-17 22:50 ` Inochi Amaoto
2025-02-17 22:50 ` Inochi Amaoto
2025-02-17 23:21 ` Russell King (Oracle)
2025-02-17 23:21 ` Russell King (Oracle)
2025-02-18 1:01 ` Inochi Amaoto
2025-02-18 1:01 ` Inochi Amaoto
2025-02-18 10:40 ` Russell King (Oracle)
2025-02-18 10:40 ` Russell King (Oracle)
2025-02-18 11:34 ` Inochi Amaoto
2025-02-18 11:34 ` Inochi Amaoto
2025-02-18 13:03 ` Inochi Amaoto
2025-02-18 13:03 ` Inochi Amaoto
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=Z7NDakd7zpQ_345D@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=bartosz.golaszewski@linaro.org \
--cc=clement.leger@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@tenstorrent.com \
--cc=dlan@gentoo.org \
--cc=edumazet@google.com \
--cc=emil.renner.berthing@canonical.com \
--cc=fancer.lancer@gmail.com \
--cc=hkelam@marvell.com \
--cc=inochiama@gmail.com \
--cc=jan.petrous@oss.nxp.com \
--cc=joabreu@synopsys.com \
--cc=joe@pf.is.s.u-tokyo.ac.jp \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=l.rubusch@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=looong.bin@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.