From: Oleksij Rempel <o.rempel@pengutronix.de>
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>,
Donald Hunter <donald.hunter@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Dent Project <dentproject@linuxfoundation.org>,
kernel@pengutronix.de, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v3 1/7] net: ethtool: pse-pd: Expand C33 PSE status with class, power and extended state
Date: Mon, 17 Jun 2024 21:55:25 +0200 [thread overview]
Message-ID: <ZnCUrUm69gmbGWQq@pengutronix.de> (raw)
In-Reply-To: <20240617154712.76fa490a@kmaincent-XPS-13-7390>
On Mon, Jun 17, 2024 at 03:47:12PM +0200, Kory Maincent wrote:
> > According to 33.2.4.7
> > State diagrams we have CLASSIFICATION_EVAL function which evaluates
> > results of classification.
> > In case of class_num_events = 1, we have only tpdc_timer. In case of
> > error, will we get some timer related error?
> >
> > In case of class_num_events = 2, if i see it correctly, PSE is doing
> > double classification and if results do not match, PSE will go to faul
> > state. See CLASS_EV2->(mr_pd_class_detected != temp_var) case.
> >
> > Is it what we have here?
>
> Mmh not really indeed, maybe we can put it in error_condition substate?
I'm not sure how this error can help user, if even we do not understand
what is says. May be map everything what is not clear right not to
unsupported error value. This give us some time to communicate with
vendor and prevent us from making pointless UAPi?
> > The difference between open and underload is probably:
> > - open: Iport = 0, detection state
> > - underload: Iport < Imin (or Ihold?), Iport can be 0. related to powered/MPS
> > state.
>
> Should I put it under MPS substate then?
If my understand is correct, then yes. Can you test it? Do you have PD
with adjustable load?
> > May be you will need to contact Microchip directly. Usually it helps :)
>
> Lets keep it like that for now?
let's map it to unsupported error for now
> > > +enum ethtool_c33_pse_ext_substate_pd_dll_power_type {
> > > +
> > > ETHTOOL_C33_PSE_EXT_SUBSTATE_PD_DLL_POWER_TYPE_NON_802_3AF_AT_DEVICE = 1,
> > > +};
> >
> > Here i was potentially wrong. LLDP stage is after power up, and this
> > values was probably set on early stage of signature detection. How can
> > we detect a device which is not conform to the 802.3AF/AT standard? Is
> > it something pre-802.3AF/AT, micorosemi specific vendor specific signature?
>
> Don't really know.
Same here, if we do not really know what it is, make it unsupported error value
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 |
next prev parent reply other threads:[~2024-06-17 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 14:33 [PATCH net-next v3 0/7] net: pse-pd: Add new PSE c33 features Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 1/7] net: ethtool: pse-pd: Expand C33 PSE status with class, power and extended state Kory Maincent
2024-06-15 11:22 ` Oleksij Rempel
2024-06-17 13:47 ` Kory Maincent
2024-06-17 19:55 ` Oleksij Rempel [this message]
2024-06-21 16:29 ` Kory Maincent
2024-06-22 5:06 ` Oleksij Rempel
2024-06-25 9:18 ` Kory Maincent
2024-06-25 10:33 ` Oleksij Rempel
2024-06-25 11:59 ` Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 2/7] netlink: specs: Expand the PSE netlink command with C33 new features Kory Maincent
2024-06-17 8:01 ` Donald Hunter
2024-06-14 14:33 ` [PATCH net-next v3 3/7] net: pse-pd: pd692x0: Expand ethtool status message Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 4/7] net: pse-pd: Add new power limit get and set c33 features Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 5/7] net: ethtool: Add new power limit get and set features Kory Maincent
2024-06-15 15:59 ` Oleksij Rempel
2024-06-15 18:28 ` Oleksij Rempel
2024-06-16 6:07 ` Oleksij Rempel
2024-06-17 16:14 ` Kory Maincent
2024-06-17 19:57 ` Oleksij Rempel
2024-06-14 14:33 ` [PATCH net-next v3 6/7] netlink: specs: Expand the PSE netlink command with C33 pw-limit attributes Kory Maincent
2024-06-17 8:03 ` Donald Hunter
2024-06-17 9:53 ` Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 7/7] net: pse-pd: pd692x0: Enhance with new current limit and voltage read callbacks 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=ZnCUrUm69gmbGWQq@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=dentproject@linuxfoundation.org \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).