[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc539292-0b76-46b8-99b3-508b7bc7d94d@lunn.ch>
Date: Sun, 23 Jun 2024 22:00:17 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Marek Vasut <marex@...x.de>
Cc: netdev@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Joakim Zhang <qiangqing.zhang@....com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
devicetree@...r.kernel.org, kernel@...electronics.com
Subject: Re: [net-next,PATCH] dt-bindings: net: realtek,rtl82xx: Document
known PHY IDs as compatible strings
> - $ref: ethernet-phy.yaml#
>
> properties:
> + compatible:
> + enum:
> + - ethernet-phy-id0000.8201
I'm not sure that one should be listed. It is not an official ID,
since it does not have an OUI. In fact, this is one of the rare cases
where actually listing a compatible in DT makes sense, because you can
override the broken hardware and give a correct ID in realtek address
space.
Andrew
Powered by blists - more mailing lists