From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F3362D060C; Thu, 27 Nov 2025 18:16:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764267387; cv=none; b=VIGd8reg8b6zj1Yi8mKZB/e6x/Ge5T9rdjMAYbdlCN2eGa4jNyCczFkoV6BLl13jvLRVaDzMFEgkbtDLEHwu08zPxd7ymPoBQWOW+vh3TfQQdfpdExh2o2v0+VTNmyrd356+Vg24HPU/oODujPcuRQe52UFDZhde0s1CCAopWXo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764267387; c=relaxed/simple; bh=RflXuShl1SRrOVIWtn7ZMy5clte/Mu7DfNNyZaXZk10=; h=Date:Content-Type:MIME-Version:From:Cc:To:In-Reply-To:References: Message-Id:Subject; b=ikD+oOnXU8BqOcGu0XR/u/xrSxEgHwoqec8XD1mHv6ORFUqLksezdZehapjx5i186QfNWNqazQL9GGBwwbeY8o4xtSyRtB+maDzCUw56XmNLIJ9fxdF90iCrbvs6MtGf9jrgISwdGuDmPwPZUkTBG3pbxekJM+bGsdgjCzrKIOw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=j4GL01Qe; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="j4GL01Qe" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C76AEC4CEF8; Thu, 27 Nov 2025 18:16:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1764267387; bh=RflXuShl1SRrOVIWtn7ZMy5clte/Mu7DfNNyZaXZk10=; h=Date:From:Cc:To:In-Reply-To:References:Subject:From; b=j4GL01QeOprmmJSFmPd2dZFMiM0pK6izCKVWFTOE++RtSa0S5Lf2PeduLh5wH5U1v 8PbfXD9YuMGE0twIhs/58Hkoh3gmWEEKT5mNJTajY5lxJ6nsYaVzW+j44krTJ0+aeX //l6AyVF44R0mYell3wFGt6lieXoB9Fl/liAl8epT/guyO40whCtTRga1ogkFAqZsO GGhUeDt2tlWXchuVtmsqaM2WgLp7dg4rqRHw/leCmWo7+QTbc3TZ3jJwKSflyIsh8j L0ukfXmx2mAgSIyeUPrqjE03Wi1zPl6vSZNQvHzhgFb1GYkMIlCZzrXiNYKW2l44sb +gKNhGghLsOkQ== Date: Thu, 27 Nov 2025 12:16:25 -0600 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: "Rob Herring (Arm)" Cc: Krzysztof Kozlowski , Oleksij Rempel , davem@davemloft.net, Daniel Golle , Florian Fainelli , Romain Gantois , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Christophe Leroy , Dimitri Fedrau , Herve Codina , =?utf-8?q?Marek_Beh=C3=BAn?= , mwojtas@chromium.org, Antoine Tenart , linux-arm-kernel@lists.infradead.org, =?utf-8?q?Nicol=C3=B2_Veronese?= , thomas.petazzoni@bootlin.com, Russell King , Simon Horman , linux-arm-msm@vger.kernel.org, Eric Dumazet , Vladimir Oltean , Conor Dooley , =?utf-8?q?K=C3=B6ry_Maincent?= , Paolo Abeni , Jakub Kicinski , Andrew Lunn , Heiner Kallweit , devicetree@vger.kernel.org, Tariq Toukan To: Maxime Chevallier In-Reply-To: <20251127171800.171330-2-maxime.chevallier@bootlin.com> References: <20251127171800.171330-1-maxime.chevallier@bootlin.com> <20251127171800.171330-2-maxime.chevallier@bootlin.com> Message-Id: <176426738405.367554.14295793625592890396.robh@kernel.org> Subject: Re: [PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description 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 > Reviewed-by: Christophe Leroy > Reviewed-by: Rob Herring (Arm) > Tested-by: Christophe Leroy > Signed-off-by: Maxime Chevallier > --- > .../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@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@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@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@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@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@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@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@c265000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2'] doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20251127171800.171330-2-maxime.chevallier@bootlin.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.