[PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description
Maxime Chevallier
maxime.chevallier at bootlin.com
Fri Nov 28 00:34:12 PST 2025
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 at lunn.ch>
>> Reviewed-by: Christophe Leroy <christophe.leroy at csgroup.eu>
>> Reviewed-by: Rob Herring (Arm) <robh at kernel.org>
>> Tested-by: Christophe Leroy <christophe.leroy at csgroup.eu>
>> Signed-off-by: Maxime Chevallier <maxime.chevallier at bootlin.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 at c263000: 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 at c263000: 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 at c265000: 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 at c265000: 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 at c263000: 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 at c263000: 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 at c265000: 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 at c265000: 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
More information about the linux-arm-kernel
mailing list