devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Rob Herring <robh@kernel.org>
Cc: Kory Maincent <kory.maincent@bootlin.com>,
	"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>,
	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 v4 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller
Date: Wed, 21 Feb 2024 16:06:25 +0100	[thread overview]
Message-ID: <ZdYRccm7-TXcRp_v@pengutronix.de> (raw)
In-Reply-To: <20240221144135.GB2779189-robh@kernel.org>

On Wed, Feb 21, 2024 at 07:41:35AM -0700, Rob Herring wrote:
> On Sat, Feb 17, 2024 at 01:14:29PM +0100, Oleksij Rempel wrote:
> > On Thu, Feb 15, 2024 at 05:02:55PM +0100, Kory Maincent wrote:
> > > Add the PD692x0 I2C Power Sourcing Equipment controller device tree
> > > bindings documentation.
> > > 
> > > This patch is sponsored by Dent Project <dentproject@linuxfoundation.org>.
> > > 
> > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > > ---
> > ...
> > > +        pse_pis {
> > > +          #address-cells = <1>;
> > > +          #size-cells = <0>;
> > > +
> > > +          pse_pi0: pse_pi@0 {
> > > +            reg = <0>;
> > > +            #pse-cells = <0>;
> > > +            pairset-names = "alternative-a", "alternative-b";
> > > +            pairsets = <&phys0>, <&phys1>;
> > > +          };
> > > +          pse_pi1: pse_pi@1 {
> > > +            reg = <1>;
> > > +            #pse-cells = <0>;
> > > +            pairset-names = "alternative-a";
> > > +            pairsets = <&phys2>;
> > 
> > According to latest discussions, PSE PI nodes will need some
> > additional, board specific, information:
> > - this controller do not implements polarity switching, we need to know
> >   what polarity is implemented on this board. The 802.3 spec provide not
> >   really consistent names for polarity configurations:
> >   - Alternative A MDI-X
> >   - Alternative A MDI
> >   - Alternative B X
> >   - Alternative B S
> >   The board may implement one of polarity configurations per alternative
> >   or have additional helpers to switch them without using PSE
> >   controller.
> >   Even if specification explicitly say:
> >   "The PD shall be implemented to be insensitive to the polarity of the power
> >    supply and shall be able to operate per the PD Mode A column and the PD
> >    Mode B column in Table 33–13"
> >   it is possible to find reports like this:
> >   https://community.ui.com/questions/M5-cant-take-reversed-power-polarity-/d834d9a8-579d-4f08-80b1-623806cc5070
> > 
> >   Probably this kind of property is a good fit:
> >   polarity-supported = "MDI-X", "MDI", "X", "S";
> 
> Where does that live? Looks like a property of the consumers defined in 
> the provider. Generally, that's not the right way for DT. 

This is property of PSE PI (Power Interface)

                                             Ethernet PHY --\
PSE (provider) ----> PSE PI (consumer of multiple PSE's) ----> Physial port


PSE - provides power lines.
PSE PI - switches (or not) power lines in different configurations. This
is different part of the board/system. PSE PI can have combination or
one of following configurations: "MDI-X", "MDI", "X", "S";
This is not something what PSE actually do. PSE PI and PSE are described
in IEEE802.3 specification.

> I'll say it 
> again, I think you should be expanding #pse-cells (>1), not getting rid 
> of them (==0).

Did you took time to read my last explanation? Sorry for making it long
description, this topic is a bit complex.

Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-02-21 15:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 16:02 [PATCH net-next v4 00/17] net: Add support for Power over Ethernet (PoE) Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 01/17] MAINTAINERS: net: Add Oleksij to pse-pd maintainers Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 02/17] of: property: Add fw_devlink support for pse parent Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 03/17] net: pse-pd: Rectify and adapt the naming of admin_cotrol member of struct pse_control_config Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 04/17] ethtool: Expand Ethernet Power Equipment with c33 (PoE) alongside PoDL Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 05/17] net: pse-pd: Introduce PSE types enumeration Kory Maincent
2024-02-15 18:58   ` Jakub Kicinski
2024-02-16  9:42     ` Köry Maincent
2024-02-17  1:36       ` Jakub Kicinski
2024-02-19 15:04         ` Köry Maincent
2024-02-19 15:44           ` Andrew Lunn
2024-02-21 14:40             ` Köry Maincent
2024-02-21 14:36         ` Rob Herring
2024-02-15 16:02 ` [PATCH net-next v4 06/17] net: ethtool: pse-pd: Expand pse commands with the PSE PoE interface Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 07/17] netlink: specs: Modify pse attribute prefix Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 08/17] netlink: specs: Expand the pse netlink command with PoE interface Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 09/17] MAINTAINERS: Add myself to pse networking maintainer Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 10/17] net: pse-pd: Add support for PSE PIs Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 11/17] dt-bindings: net: pse-pd: Add another way of describing several " Kory Maincent
2024-02-15 18:46   ` Rob Herring
2024-02-16  8:56     ` Köry Maincent
2024-02-16  8:58       ` Köry Maincent
2024-02-16  2:16   ` Rob Herring
2024-02-17 14:01   ` Krzysztof Kozlowski
2024-02-19  9:22     ` Köry Maincent
2024-02-15 16:02 ` [PATCH net-next v4 12/17] net: pse-pd: Add support for setup_pi_matrix callback Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 13/17] net: pse-pd: Use regulator framework within PSE framework Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller Kory Maincent
2024-02-17 12:14   ` Oleksij Rempel
2024-02-19 14:38     ` Köry Maincent
2024-02-19 14:54       ` Andrew Lunn
2024-02-20 10:40     ` Köry Maincent
2024-02-20 11:05       ` Oleksij Rempel
2024-02-21 14:41     ` Rob Herring
2024-02-21 15:06       ` Oleksij Rempel [this message]
2024-02-17 14:03   ` Krzysztof Kozlowski
2024-02-15 16:02 ` [PATCH net-next v4 15/17] net: pse-pd: Add PD692x0 PSE controller driver Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 16/17] dt-bindings: net: pse-pd: Add bindings for TPS23881 PSE controller Kory Maincent
2024-02-15 16:02 ` [PATCH net-next v4 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=ZdYRccm7-TXcRp_v@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --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=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    --cc=robh@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).