From: Kory Maincent <kory.maincent@bootlin.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Mark Brown <broonie@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
Dent Project <dentproject@linuxfoundation.org>,
Kory Maincent <kory.maincent@bootlin.com>
Subject: [PATCH net-next v5 11/17] dt-bindings: net: pse-pd: Add another way of describing several PSE PIs
Date: Tue, 27 Feb 2024 15:42:53 +0100 [thread overview]
Message-ID: <20240227-feature_poe-v5-11-28f0aa48246d@bootlin.com> (raw)
In-Reply-To: <20240227-feature_poe-v5-0-28f0aa48246d@bootlin.com>
PSE PI setup may encompass multiple PSE controllers or auxiliary circuits
that collectively manage power delivery to one Ethernet port.
Such configurations might support a range of PoE standards and require
the capability to dynamically configure power delivery based on the
operational mode (e.g., PoE2 versus PoE4) or specific requirements of
connected devices. In these instances, a dedicated PSE PI node becomes
essential for accurately documenting the system architecture. This node
would serve to detail the interactions between different PSE controllers,
the support for various PoE modes, and any additional logic required to
coordinate power delivery across the network infrastructure.
The old usage of "#pse-cells" is unsuficient as it carries only the PSE PI
index information.
This patch is sponsored by Dent Project <dentproject@linuxfoundation.org>.
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Changes in v3:
- New patch
Changes in v4:
- Remove $def
- Fix pairset-names item list
- Upgrade few properties description
- Update the commit message
Changes in v5:
- Fix yamllint error.
- Replace underscore by dash in properties names.
- Add polarity-supported property.
---
.../bindings/net/pse-pd/pse-controller.yaml | 100 ++++++++++++++++++++-
1 file changed, 97 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
index 2d382faca0e6..76a301463b48 100644
--- a/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
+++ b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
@@ -13,6 +13,7 @@ description: Binding for the Power Sourcing Equipment (PSE) as defined in the
maintainers:
- Oleksij Rempel <o.rempel@pengutronix.de>
+ - Kory Maincent <kory.maincent@bootlin.com>
properties:
$nodename:
@@ -22,11 +23,104 @@ properties:
description:
Used to uniquely identify a PSE instance within an IC. Will be
0 on PSE nodes with only a single output and at least 1 on nodes
- controlling several outputs.
+ controlling several outputs which are not described in the pse-pis
+ subnode. This property is deprecated, please use pse-pis instead.
enum: [0, 1]
-required:
- - "#pse-cells"
+ pse-pis:
+ type: object
+ description:
+ Overview of the PSE PIs provided by the controller.
+
+ properties:
+ "#address-cells":
+ const: 1
+
+ "#size-cells":
+ const: 0
+
+ required:
+ - "#address-cells"
+ - "#size-cells"
+
+ patternProperties:
+ "^pse-pi@[0-9a-f]+$":
+ type: object
+ description:
+ PSE PI for power delivery via pairsets, compliant with IEEE
+ 802.3-2022, Section 145.2.4. Each pairset comprises a positive and
+ a negative VPSE pair, adhering to the pinout configurations
+ detailed in the standard.
+ See Documentation/networking/pse-pd/pse-pi.rst for details.
+
+ properties:
+ reg:
+ description:
+ Address describing the PSE PI index.
+ maxItems: 1
+
+ "#pse-cells":
+ const: 0
+
+ pairset-names:
+ $ref: /schemas/types.yaml#/definitions/string-array
+ description:
+ Names of the pairsets as per IEEE 802.3-2022, Section 145.2.4.
+ Valid values are "alternative-a" and "alternative-b". Each name
+ should correspond to a phandle in the 'pairset' property
+ pointing to the power supply for that pairset.
+ minItems: 1
+ maxItems: 2
+ items:
+ enum:
+ - alternative-a
+ - alternative-b
+
+ pairsets:
+ $ref: /schemas/types.yaml#/definitions/phandle-array
+ description:
+ List of phandles, each pointing to the power supply for the
+ corresponding pairset named in 'pairset-names'. This property
+ aligns with IEEE 802.3-2022, Section 33.2.3 and 145.2.4.
+ PSE Pinout Alternatives (as per IEEE 802.3-2022 Table 145–3)
+ | Conductor | Alternative A (MDI-X) | Alternative A (MDI) | Alternative B(X) | Alternative B(S) |
+ |-----------|-----------------------|---------------------|------------------|------------------|
+ | 1 | Negative VPSE | Positive VPSE | — | — |
+ | 2 | Negative VPSE | Positive VPSE | — | — |
+ | 3 | Positive VPSE | Negative VPSE | — | — |
+ | 4 | — | — | Negative VPSE | Positive VPSE |
+ | 5 | — | — | Negative VPSE | Positive VPSE |
+ | 6 | Positive VPSE | Negative VPSE | — | — |
+ | 7 | — | — | Positive VPSE | Negative VPSE |
+ | 8 | — | — | Positive VPSE | Negative VPSE |
+ minItems: 1
+ maxItems: 2
+
+ polarity-supported:
+ $ref: /schemas/types.yaml#/definitions/string-array
+ description:
+ Polarity configuration supported by the PSE PI pairsets.
+ minItems: 1
+ maxItems: 4
+ items:
+ enum:
+ - MDI-X
+ - MDI
+ - X
+ - S
+
+ required:
+ - reg
+ - "#pse-cells"
+ - pairset-names
+ - pairsets
+ - polarity-supported
+
+oneOf:
+ - required:
+ - "#pse-cells"
+ - required:
+ - pse-pis
additionalProperties: true
--
2.25.1
next prev parent reply other threads:[~2024-02-27 14:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:42 [PATCH net-next v5 00/17] net: Add support for Power over Ethernet (PoE) Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 01/17] MAINTAINERS: net: Add Oleksij to pse-pd maintainers Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 02/17] of: property: Add fw_devlink support for pse parent Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 03/17] net: pse-pd: Rectify and adapt the naming of admin_cotrol member of struct pse_control_config Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 04/17] ethtool: Expand Ethernet Power Equipment with c33 (PoE) alongside PoDL Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 05/17] net: pse-pd: Introduce PSE types enumeration Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 06/17] net: ethtool: pse-pd: Expand pse commands with the PSE PoE interface Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 07/17] netlink: specs: Modify pse attribute prefix Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 08/17] netlink: specs: Expand the pse netlink command with PoE interface Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 09/17] MAINTAINERS: Add myself to pse networking maintainer Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 10/17] net: pse-pd: Add support for PSE PIs Kory Maincent
2024-03-01 14:24 ` Oleksij Rempel
2024-03-01 16:10 ` Köry Maincent
2024-03-01 16:48 ` Oleksij Rempel
2024-02-27 14:42 ` Kory Maincent [this message]
2024-02-28 16:42 ` [PATCH net-next v5 11/17] dt-bindings: net: pse-pd: Add another way of describing several " Rob Herring
2024-02-27 14:42 ` [PATCH net-next v5 12/17] net: pse-pd: Add support for setup_pi_matrix callback Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 13/17] net: pse-pd: Use regulator framework within PSE framework Kory Maincent
2024-02-28 0:56 ` Jakub Kicinski
2024-02-29 10:19 ` Köry Maincent
2024-02-28 12:48 ` Simon Horman
2024-02-29 9:41 ` Köry Maincent
2024-03-02 21:35 ` Oleksij Rempel
2024-03-04 9:27 ` Köry Maincent
2024-03-04 10:31 ` Oleksij Rempel
2024-03-21 16:15 ` Kory Maincent
2024-03-21 16:43 ` Oleksij Rempel
2024-03-22 10:39 ` Kory Maincent
2024-03-22 14:07 ` Oleksij Rempel
2024-03-22 14:22 ` Kory Maincent
2024-03-04 13:32 ` Andrew Lunn
2024-03-04 13:39 ` Oleksij Rempel
2024-03-04 13:53 ` Andrew Lunn
2024-03-04 14:23 ` Oleksij Rempel
2024-02-27 14:42 ` [PATCH net-next v5 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 15/17] net: pse-pd: Add PD692x0 PSE controller driver Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 16/17] dt-bindings: net: pse-pd: Add bindings for TPS23881 PSE controller Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 17/17] net: pse-pd: Add TI TPS23881 PSE controller driver Kory Maincent
2024-02-28 12:53 ` Simon Horman
2024-02-29 11:09 ` Köry Maincent
2024-02-27 15:31 ` [PATCH net-next v5 00/17] net: Add support for Power over Ethernet (PoE) Jamal Hadi Salim
2024-03-08 13:54 ` Köry Maincent
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=20240227-feature_poe-v5-11-28f0aa48246d@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dentproject@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=russ.weight@linux.dev \
--cc=thomas.petazzoni@bootlin.com \
/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;
as well as URLs for NNTP newsgroup(s).