From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Rob Herring <robh@kernel.org>
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>
Subject: Re: [PATCH net-next v1 1/7] dt-bindings: net: pse-dt: add bindings for generic PSE controller
Date: Tue, 23 Aug 2022 18:22:57 +0200 [thread overview]
Message-ID: <20220823162257.GO10138@pengutronix.de> (raw)
In-Reply-To: <20220822184112.GA113650-robh@kernel.org>
On Mon, Aug 22, 2022 at 01:41:12PM -0500, Rob Herring wrote:
> On Fri, Aug 19, 2022 at 02:01:03PM +0200, Oleksij Rempel wrote:
> > Add binding for generic Ethernet PSE controller.
> >
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > ---
> > .../bindings/net/pse-pd/generic-pse.yaml | 40 +++++++++++++++++++
> > 1 file changed, 40 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/net/pse-pd/generic-pse.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/net/pse-pd/generic-pse.yaml b/Documentation/devicetree/bindings/net/pse-pd/generic-pse.yaml
> > new file mode 100644
> > index 0000000000000..64f91efa79a56
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/net/pse-pd/generic-pse.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/generic-pse.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Generic Power Sourcing Equipment
> > +
> > +maintainers:
> > + - Oleksij Rempel <o.rempel@pengutronix.de>
> > +
> > +description: |
> > + Generic PSE controller. The device must be referenced by the PHY node
> > + to control power injection to the Ethernet cable.
>
> Isn't this separate from the PHY other than you need to associate
> supplies with ethernet ports?
>
> Is there a controller here? Or it is just a regulator consumer
> associated with an ethernet port?
Current version has only regulator. It will be extended with IEEE 802.3
specific power source classification information, wich will be overkill for the
regulator framework. I can add it to the v2 version.
> > +properties:
> > + compatible:
> > + const: ieee802.3-podl-pse-generic
>
> Is this for 802.3bu only (which is where PoDL comes from) or all the
> flavors? If all, do they need to be distinguished?
yes. ieee802.3 defines type and class with different enumeration and
meanings for PSE and PoDL PSE.
So far we have two different modes:
- 802.3bu (PoDL PSE). Has own types and classes
- 802.3af is extended by 802.3at, and the extended by 802.3bt
all of them are named as PSE and has own types and classes as well.
I worry more about the fact is some one will implement HW supporting both
modes. IMO, it is possible to take usual ethernet PHY, configure to
10Bit half-duplex and run over single pair. In this case it is possible
to use only PoDL PSE mode.
In this case I need single generic compatible but different properties
to describe supported PSE and PoDL PSE modes.
> 'generic' is redundant.
ok
> > +
> > + '#pse-cells':
>
> What's this for? You don't have a consumer.
the consumer is PHY.
> > + const: 0
> > +
> > + ieee802.3-podl-pse-supply:
>
> Seems a bit long
ok. Reduce it to pse-supply ?
> > + description: |
>
> Don't need '|' if no formatting to maintain.
ok
> > + Power supply for the PSE controller
> > +
> > +additionalProperties: false
> > +
> > +required:
> > + - compatible
> > + - '#pse-cells'
> > + - ieee802.3-podl-pse-supply
> > +
> > +examples:
> > + - |
> > + ethernet-pse-1 {
> > + compatible = "ieee802.3-podl-pse-generic";
> > + ieee802.3-podl-pse-supply = <®_t1l1>;
> > + #pse-cells = <0>;
> > + };
> > --
> > 2.30.2
> >
> >
>
--
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 |
next prev parent reply other threads:[~2022-08-23 18:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 12:01 [PATCH net-next v1 0/7] add generic PSE support Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 1/7] dt-bindings: net: pse-dt: add bindings for generic PSE controller Oleksij Rempel
2022-08-22 18:41 ` Rob Herring
2022-08-23 16:22 ` Oleksij Rempel [this message]
2022-08-19 12:01 ` [PATCH net-next v1 2/7] dt-bindings: net: phy: add PoDL PSE property Oleksij Rempel
2022-08-22 18:45 ` Rob Herring
2022-08-22 19:34 ` Andrew Lunn
2022-08-23 14:44 ` Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 3/7] net: add framework to support Ethernet PSE and PDs devices Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 4/7] net: pse-pd: add generic PSE driver Oleksij Rempel
2022-08-19 20:54 ` Andrew Lunn
2022-08-20 12:00 ` Oleksij Rempel
2022-08-19 21:32 ` Andrew Lunn
2022-08-20 12:10 ` Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 5/7] net: mdiobus: fwnode_mdiobus_register_phy() rework error handling Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 6/7] net: mdiobus: search for PSE nodes by parsing PHY nodes Oleksij Rempel
2022-08-19 12:01 ` [PATCH net-next v1 7/7] ethtool: add interface to interact with Ethernet Power Equipment Oleksij Rempel
2022-08-19 16:44 ` kernel test robot
2022-08-19 18:37 ` kernel test robot
2022-08-19 21:15 ` Andrew Lunn
2022-08-20 12:31 ` Oleksij Rempel
2022-08-20 3:08 ` Bagas Sanjaya
2022-08-20 18:16 ` Andrew Lunn
2022-08-21 4:39 ` Oleksij Rempel
2022-08-20 18:48 ` Andrew Lunn
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=20220823162257.GO10138@pengutronix.de \
--to=o.rempel@pengutronix.de \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).