From: Andrew Lunn <andrew@lunn.ch>
To: Buday Csaba <buday.csaba@prolan.hu>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"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>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: ethernet-phy: clarify when compatible must specify PHY ID
Date: Fri, 31 Oct 2025 14:01:26 +0100 [thread overview]
Message-ID: <f08d956b-4392-41c0-93d7-d7dd105c016c@lunn.ch> (raw)
In-Reply-To: <b8613028fb2f7f69e2fa5e658bd2840c790935d4.1761898321.git.buday.csaba@prolan.hu>
On Fri, Oct 31, 2025 at 09:15:06AM +0100, Buday Csaba wrote:
> Change PHY ID description in ethernet-phy.yaml to clarify that a
> PHY ID is required (may -> must) when the PHY requires special
> initialization sequence.
>
> Link: https://lore.kernel.org/netdev/20251026212026.GA2959311-robh@kernel.org/
> Link: https://lore.kernel.org/netdev/aQIZvDt5gooZSTcp@debianbuilder/
>
> Signed-off-by: Buday Csaba <buday.csaba@prolan.hu>
> ---
> Documentation/devicetree/bindings/net/ethernet-phy.yaml | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> index 2ec2d9fda..6f5599902 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> @@ -35,9 +35,10 @@ properties:
> description: PHYs that implement IEEE802.3 clause 45
> - pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
> description:
> - If the PHY reports an incorrect ID (or none at all) then the
> - compatible list may contain an entry with the correct PHY ID
> - in the above form.
> + If the PHY reports an incorrect ID (or none at all), or the PHY
> + requires a specific initialization sequence (like a particular
> + order of clocks, resets, power supplies), then the compatible list
> + must contain an entry with the correct PHY ID in the above form.
That is good start, but how about:
PHYs contain identification registers. These will be read to
identify the PHY. If the PHY reports an incorrect ID, or the
PHY requires a specific initialization sequence (like a
particular order of clocks, resets, power supplies), in
order to be able to read the ID registers, then the
compatible list must contain an entry with the correct PHY
ID in the above form.
The first two sentences make it clear we ideally use the ID registers.
Then we say what happens if cannot work.
The "(or none at all)" is exactly the case you are trying to clarify,
it does not respond due to missing reset, clocks etc. We don't need to
say it twice, so i removed it.
Andrew
next prev parent reply other threads:[~2025-10-31 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 8:15 [PATCH] dt-bindings: net: ethernet-phy: clarify when compatible must specify PHY ID Buday Csaba
2025-10-31 13:01 ` Andrew Lunn [this message]
2025-10-31 15:08 ` Conor Dooley
2025-11-03 8:13 ` [PATCH v2 1/1] " Buday Csaba
2025-11-03 13:19 ` Andrew Lunn
2025-11-03 16:49 ` Florian Fainelli
2025-11-05 1:50 ` patchwork-bot+netdevbpf
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=f08d956b-4392-41c0-93d7-d7dd105c016c@lunn.ch \
--to=andrew@lunn.ch \
--cc=buday.csaba@prolan.hu \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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