From: Krzysztof Kozlowski <krzk@kernel.org>
To: Piotr Kubik <piotr.kubik@adtran.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"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>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller
Date: Wed, 16 Apr 2025 12:58:31 +0200 [thread overview]
Message-ID: <ee0599ad-7f67-46fb-aa60-32a1dac21bd0@kernel.org> (raw)
In-Reply-To: <4ddf2ede-3f40-438d-bae4-6f8b1c25e5eb@adtran.com>
On 16/04/2025 12:47, Piotr Kubik wrote:
> From: Piotr Kubik <piotr.kubik@adtran.com>
>
> Add the Si3474 I2C Power Sourcing Equipment controller device tree
> bindings documentation.
>
> Signed-off-by: Piotr Kubik <piotr.kubik@adtran.com>
> ---
> .../bindings/net/pse-pd/skyworks,si3474.yaml | 154 ++++++++++++++++++
> 1 file changed, 154 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/net/pse-pd/skyworks,si3474.yaml
Also looks like corrupted patch.
>
> diff --git
> a/Documentation/devicetree/bindings/net/pse-pd/skyworks,si3474.yaml
> b/Documentation/devicetree/bindings/net/pse-pd/skyworks,si3474.yaml
> new file mode 100644
> index 000000000000..fd48eeb2f79b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/pse-pd/skyworks,si3474.yaml
> @@ -0,0 +1,154 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/pse-pd/skyworks,si3474.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Skyworks Si3474 Power Sourcing Equipment controller
> +
> +maintainers:
> + - Kory Maincent <kory.maincent@bootlin.com>
This should be someone interested in this hardware, not subsystem
maintainer.
> +
> +allOf:
> + - $ref: pse-controller.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - skyworks,si347
> +
> + reg:
> + maxItems: 1
> +
> + '#pse-cells':
> + const: 1
> +
> + channels:
> + description: Each Si3474 is divided into two quad PoE controllers
> + accessible on different i2c addresses. Each set of quad ports can be
> + assigned to two physical channels (currently 4p support only).
What this "currently" means? Limitation of hardware or Linux? If the
latter, then drop.
> + This parameter describes the configuration of the ports conversion
> + matrix that establishes relationship between the logical ports and
> + the physical channels.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> + patternProperties:
> + '^channel@[0-3]$':
> + type: object
> + additionalProperties: false
> +
> + properties:
> + reg:
> + maxItems: 1
> +
> + required:
> + - reg
> +
> + required:
> + - "#address-cells"
> + - "#size-cells"
> +
> +unevaluatedProperties: false
This goes after required: block.
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethernet-pse@26 {
> + compatible = "skyworks,si3474";
> + reg = <0x26>;
> +
> + channels {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + phys0_0: channel@0 {
> + reg = <0>;
> + };
> + phys0_1: channel@1 {
> + reg = <1>;
> + };
> + phys0_2: channel@2 {
> + reg = <2>;
> + };
> + phys0_3: channel@3 {
> + reg = <3>;
> + };
> + };
> + pse-pis {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pse_pi2: pse-pi@2 {
> + reg = <2>;
> + #pse-cells = <0>;
> + pairset-names = "alternative-a", "alternative-b";
> + pairsets = <&phys0_0>, <&phys0_1>;
> + polarity-supported = "MDI-X", "S";
> + vpwr-supply = <®_pse>;
> + };
> + pse_pi3: pse-pi@3 {
> + reg = <3>;
> + #pse-cells = <0>;
> + pairset-names = "alternative-a", "alternative-b";
> + pairsets = <&phys0_2>, <&phys0_3>;
> + polarity-supported = "MDI-X", "S";
> + vpwr-supply = <®_pse>;
> + };
> + };
> + };
> +
> + ethernet-pse@27 {
> + compatible = "skyworks,si3474";
This is the same as other example, so drop and keep only one.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-16 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 10:47 [PATCH 0/2] Add Si3474 PSE controller driver Piotr Kubik
2025-04-16 10:47 ` [PATCH 1/2] net: pse-pd: " Piotr Kubik
2025-04-16 10:54 ` Krzysztof Kozlowski
2025-04-17 11:30 ` [EXTERNAL]Re: " Piotr Kubik
2025-04-17 9:32 ` Oleksij Rempel
2025-04-17 11:59 ` [EXTERNAL]Re: " Piotr Kubik
2025-04-16 10:47 ` [PATCH 2/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller Piotr Kubik
2025-04-16 10:58 ` Krzysztof Kozlowski [this message]
2025-04-17 11:43 ` [EXTERNAL]Re: " Piotr Kubik
2025-04-16 12:32 ` [PATCH 0/2] Add Si3474 PSE controller driver Kory Maincent
2025-04-17 11:13 ` [EXTERNAL]Re: " Piotr Kubik
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=ee0599ad-7f67-46fb-aa60-32a1dac21bd0@kernel.org \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piotr.kubik@adtran.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