netdev - Re: [PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b8d12481-2637-470d-a3f1-784c0d7b4b3e@bootlin.com>
Date: Fri, 28 Nov 2025 09:34:12 +0100
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: "Rob Herring (Arm)" <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Oleksij Rempel <o.rempel@...gutronix.de>, davem@...emloft.net,
 Daniel Golle <daniel@...rotopia.org>, Florian Fainelli
 <f.fainelli@...il.com>, Romain Gantois <romain.gantois@...tlin.com>,
 netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 Christophe Leroy <christophe.leroy@...roup.eu>,
 Dimitri Fedrau <dimitri.fedrau@...bherr.com>,
 Herve Codina <herve.codina@...tlin.com>, Marek Behún
 <kabel@...nel.org>, mwojtas@...omium.org, Antoine Tenart
 <atenart@...nel.org>, linux-arm-kernel@...ts.infradead.org,
 Nicolò Veronese <nicveronese@...il.com>,
 thomas.petazzoni@...tlin.com, Russell King <linux@...linux.org.uk>,
 Simon Horman <horms@...nel.org>, linux-arm-msm@...r.kernel.org,
 Eric Dumazet <edumazet@...gle.com>, Vladimir Oltean
 <vladimir.oltean@....com>, Conor Dooley <conor+dt@...nel.org>,
 Köry Maincent <kory.maincent@...tlin.com>,
 Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
 Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
 devicetree@...r.kernel.org, Tariq Toukan <tariqt@...dia.com>
Subject: Re: [PATCH net-next v20 01/14] dt-bindings: net: Introduce the
 ethernet-connector description

Hi,

On 27/11/2025 19:16, Rob Herring (Arm) wrote:
> 
> On Thu, 27 Nov 2025 18:17:44 +0100, Maxime Chevallier wrote:
>> The ability to describe the physical ports of Ethernet devices is useful
>> to describe multi-port devices, as well as to remove any ambiguity with
>> regard to the nature of the port.
>>
>> Moreover, describing ports allows for a better description of features
>> that are tied to connectors, such as PoE through the PSE-PD devices.
>>
>> Introduce a binding to allow describing the ports, for now with 2
>> attributes :
>>
>>  - The number of pairs, which is a quite generic property that allows
>>    differentating between multiple similar technologies such as BaseT1
>>    and "regular" BaseT (which usually means BaseT4).
>>
>>  - The media that can be used on that port, such as BaseT for Twisted
>>    Copper, BaseC for coax copper, BaseS/L for Fiber, BaseK for backplane
>>    ethernet, etc. This allows defining the nature of the port, and
>>    therefore avoids the need for vendor-specific properties such as
>>    "micrel,fiber-mode" or "ti,fiber-mode".
>>
>> The port description lives in its own file, as it is intended in the
>> future to allow describing the ports for phy-less devices.
>>
>> Reviewed-by: Andrew Lunn <andrew@...n.ch>
>> Reviewed-by: Christophe Leroy <christophe.leroy@...roup.eu>
>> Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
>> Tested-by: Christophe Leroy <christophe.leroy@...roup.eu>
>> Signed-off-by: Maxime Chevallier <maxime.chevallier@...tlin.com>
>> ---
>>  .../bindings/net/ethernet-connector.yaml      | 57 +++++++++++++++++++
>>  .../devicetree/bindings/net/ethernet-phy.yaml | 18 ++++++
>>  MAINTAINERS                                   |  1 +
>>  3 files changed, 76 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/net/ethernet-connector.yaml
>>
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']

Hmm I don't see the connection between this error and my patch...

Make dt_binding_check doesn't show any issue related to the binding
introduced by this patch :(

Maxime