From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: netdev@vger.kernel.org, linux-sunxi@lists.linux.dev,
"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>, "Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Yinggang Gu" <guyinggang@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Yanteng Si" <si.yanteng@linux.dev>,
"Feiyang Chen" <chenfeiyang@loongson.cn>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Jinjie Ruan" <ruanjinjie@huawei.com>,
"Paul Kocialkowski" <paulk@sys-base.io>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] net: stmmac: dwmac-sun8i: Allow runtime AC200/AC300 phy selection
Date: Mon, 26 May 2025 09:04:40 +0100 [thread overview]
Message-ID: <aDQgmJMIkkQ922Bd@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250526002924.2567843-2-james.hilliard1@gmail.com>
On Sun, May 25, 2025 at 06:29:22PM -0600, James Hilliard wrote:
> + if (!nvmem_cell_read_u16(dev, "ac300", &val)) {
> + const char *phy_name = (val & AC300_KEY) ? "ac300" : "ac200";
> + int index = of_property_match_string(dev->of_node, "phy-names", phy_name);
> + if (index < 0) {
> + dev_err(dev, "PHY name not found in device tree\n");
> + return -EINVAL;
> + }
> +
> + plat_dat->phy_node = of_parse_phandle(dev->of_node, "phys", index);
> + if (!plat_dat->phy_node) {
> + dev_err(dev, "Failed to get PHY node from phys property\n");
> + return -EINVAL;
> + }
> + }
1. You are re-using the drivers/phy binding for ethernet PHYs driven by
phylib here.
2. You need to update
Documentation/devicetree/bindings/net/allwinner,sun8i-a83t-emac.yaml
in a separate patch.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-05-26 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 0:29 [RFC PATCH 1/2] net: stmmac: allow drivers to explicitly select PHY device James Hilliard
2025-05-26 0:29 ` [RFC PATCH 2/2] net: stmmac: dwmac-sun8i: Allow runtime AC200/AC300 phy selection James Hilliard
2025-05-26 1:38 ` Yanteng Si
2025-05-26 8:04 ` Russell King (Oracle) [this message]
2025-05-26 14:14 ` Andrew Lunn
2025-05-26 19:05 ` James Hilliard
2025-05-26 19:58 ` Andrew Lunn
2025-05-26 20:59 ` James Hilliard
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=aDQgmJMIkkQ922Bd@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guyinggang@loongson.cn \
--cc=james.hilliard1@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulk@sys-base.io \
--cc=ruanjinjie@huawei.com \
--cc=samuel@sholland.org \
--cc=si.yanteng@linux.dev \
--cc=u.kleine-koenig@baylibre.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).