devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "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>,
	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>,
	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>
Subject: Re: [PATCH net-next v3 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller
Date: Fri, 9 Feb 2024 14:57:27 +0000	[thread overview]
Message-ID: <20240209145727.GA3702230-robh@kernel.org> (raw)
In-Reply-To: <20240208-feature_poe-v3-14-531d2674469e@bootlin.com>

On Thu, Feb 08, 2024 at 02:08:51PM +0100, Kory Maincent wrote:
> Add the PD692x0 I2C Power Sourcing Equipment controller device tree
> bindings documentation.
> 
> Sponsored-by: Dent Project <dentproject@linuxfoundation.org>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> 
> Changes in v2:
> - Enhance ports-matrix description.
> - Replace additionalProperties by unevaluatedProperties.
> - Drop i2c suffix.
> 
> Changes in v3:
> - Remove ports-matrix parameter.
> - Add description of all physical ports and managers.
> - Add pse_pis subnode moving to the API of pse-controller binding.
> - Remove the MAINTAINERS section for this driver as I will be maintaining
>   all pse-pd subsystem.
> ---
>  .../bindings/net/pse-pd/microchip,pd692x0.yaml     | 157 +++++++++++++++++++++
>  1 file changed, 157 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/pse-pd/microchip,pd692x0.yaml b/Documentation/devicetree/bindings/net/pse-pd/microchip,pd692x0.yaml
> new file mode 100644
> index 000000000000..57ba5365157c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/pse-pd/microchip,pd692x0.yaml
> @@ -0,0 +1,157 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/pse-pd/microchip,pd692x0.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip PD692x0 Power Sourcing Equipment controller
> +
> +maintainers:
> +  - Kory Maincent <kory.maincent@bootlin.com>
> +
> +allOf:
> +  - $ref: pse-controller.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - microchip,pd69200
> +      - microchip,pd69210
> +      - microchip,pd69220
> +
> +  reg:
> +    maxItems: 1
> +
> +  managers:
> +    $ref: "#/$defs/managers"
> +    description:
> +      List of the PD69208T4/PD69204T4/PD69208M PSE managers. Each manager
> +      have 4 or 8 physical ports according to the chip version. No need to
> +      specify the SPI chip select as it is automatically detected by the
> +      PD692x0 PSE controller. The PSE managers have to be described from
> +      the lowest chip select to the greatest one, which is the detection
> +      behavior of the PD692x0 PSE controller. The PD692x0 support up to
> +      12 PSE managers which can expose up to 96 physical ports. All
> +      physical ports available on a manager have to be described in the
> +      incremental order even if they are not used.

Looks to me like you just need 3 PSE cells: <manager> <port> <A|B>

Really, no need for each piece of data to its own cell, so it could be 
merged into 1 or 2 cells.

But cell data is generally supposed to be meaningful to the provider and 
opaque to the consumer. It's not clear to me who needs to know 
alternative A vs. B. That seems more like a property of the PHY than the 
power provider? 

Rob

  reply	other threads:[~2024-02-09 14:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 13:08 [PATCH net-next v3 00/17] net: Add support for Power over Ethernet (PoE) Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 01/17] MAINTAINERS: net: Add Oleksij to pse-pd maintainers Kory Maincent
2024-02-14 17:13   ` Andrew Lunn
2024-02-15  8:19     ` Oleksij Rempel
2024-02-08 13:08 ` [PATCH net-next v3 02/17] of: property: Add fw_devlink support for pse parent Kory Maincent
2024-02-14 17:17   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 03/17] net: pse-pd: Rectify and adapt the naming of admin_cotrol member of struct pse_control_config Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 04/17] ethtool: Expand Ethernet Power Equipment with c33 (PoE) alongside PoDL Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 05/17] net: pse-pd: Introduce PSE types enumeration Kory Maincent
2024-02-14 17:18   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 06/17] net: ethtool: pse-pd: Expand pse commands with the PSE PoE interface Kory Maincent
2024-02-14 17:21   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 07/17] netlink: specs: Modify pse attribute prefix Kory Maincent
2024-02-14 17:22   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 08/17] netlink: specs: Expand the pse netlink command with PoE interface Kory Maincent
2024-02-14 17:22   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 09/17] MAINTAINERS: Add myself to pse networking maintainer Kory Maincent
2024-02-14 17:23   ` Andrew Lunn
2024-02-08 13:08 ` [PATCH net-next v3 10/17] dt-bindings: net: pse-pd: Add another way of describing several PSE PIs Kory Maincent
2024-02-08 15:51   ` Rob Herring
2024-02-09 14:43   ` Rob Herring
2024-02-14 13:13     ` Köry Maincent
2024-02-14 15:41       ` Köry Maincent
2024-02-15 13:51         ` Rob Herring
2024-02-15 14:01           ` Andrew Lunn
2024-02-15 14:33             ` Köry Maincent
2024-02-08 13:08 ` [PATCH net-next v3 11/17] net: pse-pd: Add support for " Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 12/17] net: pse-pd: Add support for setup_pi_matrix callback Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 13/17] net: pse-pd: Use regulator framework within PSE framework Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller Kory Maincent
2024-02-09 14:57   ` Rob Herring [this message]
2024-02-11  9:32     ` Oleksij Rempel
2024-02-14 17:41       ` Andrew Lunn
2024-02-15  8:17         ` Oleksij Rempel
2024-02-15 10:41           ` Köry Maincent
2024-02-15 12:04             ` Oleksij Rempel
2024-02-15 17:51           ` Andrew Lunn
2024-02-16  7:47             ` Oleksij Rempel
2024-02-17  6:46               ` Oleksij Rempel
2024-02-19 14:31               ` Köry Maincent
2024-02-19 16:07                 ` Oleksij Rempel
2024-02-08 13:08 ` [PATCH net-next v3 15/17] net: pse-pd: Add PD692x0 PSE controller driver Kory Maincent
2024-02-08 13:08 ` [PATCH net-next v3 16/17] dt-bindings: net: pse-pd: Add bindings for TPS23881 PSE controller Kory Maincent
2024-02-08 15:51   ` Rob Herring
2024-02-09 11:26   ` Köry Maincent
2024-02-08 13:08 ` [PATCH net-next v3 17/17] net: pse-pd: Add TI TPS23881 PSE controller driver Kory 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=20240209145727.GA3702230-robh@kernel.org \
    --to=robh@kernel.org \
    --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=kory.maincent@bootlin.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=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).