From: Andrew Lunn <andrew@lunn.ch>
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>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Russell King <linux@armlinux.org.uk>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Furong Xu <0x1207@gmail.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] net: stmmac: allow drivers to explicitly select PHY device
Date: Tue, 27 May 2025 21:14:12 +0200 [thread overview]
Message-ID: <631ed4fe-f28a-443b-922b-7f41c20f31f3@lunn.ch> (raw)
In-Reply-To: <20250527175558.2738342-1-james.hilliard1@gmail.com>
On Tue, May 27, 2025 at 11:55:54AM -0600, James Hilliard wrote:
> Some devices like the Allwinner H616 need the ability to select a phy
> in cases where multiple PHY's may be present in a device tree due to
> needing the ability to support multiple SoC variants with runtime
> PHY selection.
I'm not convinced about this yet. As far as i see, it is different
variants of the H616. They should have different compatibles, since
they are not actually compatible, and you should have different DT
descriptions. So you don't need runtime PHY selection.
Andrew
next prev parent reply other threads:[~2025-05-27 19:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 17:55 [PATCH v2 1/3] net: stmmac: allow drivers to explicitly select PHY device James Hilliard
2025-05-27 17:55 ` [PATCH v2 2/3] net: stmmac: dwmac-sun8i: Allow runtime AC200/AC300 phy selection James Hilliard
2025-05-27 17:55 ` [PATCH v2 3/3] dt-bindings: net: sun8i-emac: Add AC300 EMAC1 nvmem " James Hilliard
2025-05-27 19:14 ` Andrew Lunn [this message]
2025-05-27 19:21 ` [PATCH v2 1/3] net: stmmac: allow drivers to explicitly select PHY device James Hilliard
2025-05-27 20:01 ` Andrew Lunn
2025-05-27 20:16 ` James Hilliard
2025-05-27 20:30 ` Andrew Lunn
2025-05-27 20:37 ` James Hilliard
2025-05-27 21:48 ` Andrew Lunn
2025-05-27 22:47 ` James Hilliard
2025-05-28 7:53 ` Russell King (Oracle)
2025-05-28 11:57 ` James Hilliard
2025-05-28 13:24 ` Andrew Lunn
2025-05-28 14:11 ` Chen-Yu Tsai
2025-05-28 17:25 ` James Hilliard
2025-05-28 18:34 ` Russell King (Oracle)
2025-05-28 19:10 ` James Hilliard
2025-05-28 19:26 ` Andrew Lunn
2025-05-28 19:45 ` James Hilliard
2025-05-28 21:05 ` Andrew Lunn
2025-05-28 21:14 ` James Hilliard
2025-05-28 21:29 ` Andrew Lunn
2025-05-28 21:45 ` James Hilliard
2025-05-28 23:47 ` Andrew Lunn
2025-05-29 0:31 ` James Hilliard
2025-05-30 23:46 ` James Hilliard
2025-05-30 23:56 ` Florian Fainelli
2025-05-31 0:02 ` James Hilliard
2025-05-31 0:24 ` Florian Fainelli
2025-05-31 0:49 ` 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=631ed4fe-f28a-443b-922b-7f41c20f31f3@lunn.ch \
--to=andrew@lunn.ch \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=james.hilliard1@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=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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).