From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, David Jander <david@protonic.nl>,
Luka Perkov <luka.perkov@sartura.hr>,
Robert Marko <robert.marko@sartura.hr>
Subject: Re: [PATCH net-next v5 6/7] dt-bindings: net: pse-dt: add bindings for regulator based PoDL PSE controller
Date: Fri, 2 Sep 2022 15:50:50 -0500 [thread overview]
Message-ID: <20220902205050.GA382567-robh@kernel.org> (raw)
In-Reply-To: <20220831133240.3236779-7-o.rempel@pengutronix.de>
On Wed, Aug 31, 2022 at 03:32:39PM +0200, Oleksij Rempel wrote:
> Add bindings for the regulator based Ethernet PoDL PSE controller and
> generic bindings for all PSE controllers.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> changes v5:
> - rename to podl-pse-regulator.yaml
> - remove compatible description
> - remove "-1" on node name
> - add pse-controller.yaml for common properties
> changes v4:
> - rename to PSE regulator
> - drop currently unused properties
> - use own compatible for PoDL PSE
> changes v2:
> - rename compatible to more generic "ieee802.3-pse"
> - add class and type properties for PoDL and PoE variants
> - add pairs property
> ---
> .../net/pse-pd/podl-pse-regulator.yaml | 40 +++++++++++++++++++
> .../bindings/net/pse-pd/pse-controller.yaml | 28 +++++++++++++
> 2 files changed, 68 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/pse-pd/podl-pse-regulator.yaml
> create mode 100644 Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/pse-pd/podl-pse-regulator.yaml b/Documentation/devicetree/bindings/net/pse-pd/podl-pse-regulator.yaml
> new file mode 100644
> index 0000000000000..c6b1c188abf7e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/pse-pd/podl-pse-regulator.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/pse-pd/podl-pse-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Regulator based Power Sourcing Equipment
> +
> +maintainers:
> + - Oleksij Rempel <o.rempel@pengutronix.de>
> +
> +description: Regulator based PoDL PSE controller. The device must be referenced
> + by the PHY node to control power injection to the Ethernet cable.
> +
> +allOf:
> + - $ref: "pse-controller.yaml#"
> +
> +properties:
> + compatible:
> + const: podl-pse-regulator
> +
> + '#pse-cells':
> + const: 0
> +
> + pse-supply:
> + description: Power supply for the PSE controller
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - pse-supply
> +
> +examples:
> + - |
> + ethernet-pse {
> + compatible = "podl-pse-regulator";
> + pse-supply = <®_t1l1>;
> + #pse-cells = <0>;
> + };
> diff --git a/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
> new file mode 100644
> index 0000000000000..36e398fea220c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml
> @@ -0,0 +1,28 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/pse-pd/pse-controller.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: PSE Generic Bindings
What is PSE?
When would I use this binding? Does this follow some spec? Who is
the consumer? Please answer all those questions in this doc.
> +
> +maintainers:
> + - Oleksij Rempel <o.rempel@pengutronix.de>
> +
> +properties:
> + $nodename:
> + pattern: "^ethernet-pse(@[a-f0-9]+)?$"
The format of the unit-address depends on the bus, so it shouldn't be
defined here. Just '^ethernet-pse(@.*)?$'.
> +
> + "#pse-cells":
> + 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.
> + enum: [0, 1]
> +
> +required:
> + - "#pse-cells"
> +
> +additionalProperties: true
> +
> +...
> --
> 2.30.2
>
>
next prev parent reply other threads:[~2022-09-02 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 13:32 [PATCH net-next v5 0/7] add generic PSE support Oleksij Rempel
2022-08-31 13:32 ` [PATCH net-next v5 1/7] dt-bindings: net: phy: add PoDL PSE property Oleksij Rempel
2022-08-31 13:32 ` [PATCH net-next v5 2/7] net: add framework to support Ethernet PSE and PDs devices Oleksij Rempel
2022-08-31 13:32 ` [PATCH net-next v5 3/7] net: mdiobus: fwnode_mdiobus_register_phy() rework error handling Oleksij Rempel
2022-08-31 13:32 ` [PATCH net-next v5 4/7] net: mdiobus: search for PSE nodes by parsing PHY nodes Oleksij Rempel
2022-08-31 13:32 ` [PATCH net-next v5 5/7] ethtool: add interface to interact with Ethernet Power Equipment Oleksij Rempel
2022-09-02 3:21 ` Jakub Kicinski
2022-09-02 3:22 ` Jakub Kicinski
2022-08-31 13:32 ` [PATCH net-next v5 6/7] dt-bindings: net: pse-dt: add bindings for regulator based PoDL PSE controller Oleksij Rempel
2022-09-02 20:50 ` Rob Herring [this message]
2022-08-31 13:32 ` [PATCH net-next v5 7/7] net: pse-pd: add regulator based PSE driver Oleksij Rempel
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=20220902205050.GA382567-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--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=luka.perkov@sartura.hr \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robert.marko@sartura.hr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.