From: Kory Maincent <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Michal Kubecek <mkubecek@suse.cz>
Cc: Kyle Swenson <kyle.swenson@est.tech>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kory Maincent <kory.maincent@bootlin.com>
Subject: [PATCH ethtool-next v2 0/2] Add support for new features in C33 PSE
Date: Mon, 07 Oct 2024 14:18:48 +0200 [thread overview]
Message-ID: <20241007-feature_poe_power_cap-v2-0-cbd1aa1064df@bootlin.com> (raw)
From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
This series adds support for several new features to the C33 PSE commands:
- Get the Class negotiated between the Powered Device and the PSE
- Get Extended state and substate
- Get the Actual power
- Configure the power limit
- Get the Power limit ranges available
It also updates the manual accordingly.
Example:
$ ethtool --set-pse eth1 c33-pse-avail-pw-limit 18000
$ ethtool --show-pse eth1
PSE attributes for eth1:
Clause 33 PSE Admin State: enabled
Clause 33 PSE Power Detection Status: disabled
Clause 33 PSE Extended State: Group of mr_mps_valid states
Clause 33 PSE Extended Substate: Port is not connected
Clause 33 PSE Available Power Limit: 18000
Clause 33 PSE Power Limit Ranges:
range:
min 15000
max 18100
range:
min 30000
max 38000
range:
min 60000
max 65000
range:
min 90000
max 97500
This series requisites the c33 PSE documentation support patch sent
mainline:
https://lore.kernel.org/r/20240911-fix_missing_doc-v2-1-e2eade6886b9@bootlin.com
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Changes in v2:
- Add missing c33-pse-avail-pw-limit help usage.
- Remove patch 2 which gets merged.
- Link to v1: https://lore.kernel.org/r/20240912-feature_poe_power_cap-v1-0-499e3dd996d7@bootlin.com
---
Kory Maincent (2):
ethtool: pse-pd: Expand C33 PSE with several new features
ethtool.8: Add documentation for new C33 PSE features
ethtool.8.in | 36 ++++++++
ethtool.c | 1 +
netlink/pse-pd.c | 275 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 312 insertions(+)
---
base-commit: 96aad731275fb4e48e01da697882241e6a0cc198
change-id: 20240709-feature_poe_power_cap-56bd976dd237
Best regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next reply other threads:[~2024-10-07 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 12:18 Kory Maincent [this message]
2024-10-07 12:18 ` [PATCH ethtool-next v2 1/2] ethtool: pse-pd: Expand C33 PSE with several new features Kory Maincent
2024-10-07 12:18 ` [PATCH ethtool-next v2 2/2] ethtool.8: Add documentation for new C33 PSE features Kory Maincent
2024-10-09 9:30 ` [PATCH ethtool-next v2 0/2] Add support for new features in C33 PSE patchwork-bot+netdevbpf
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=20241007-feature_poe_power_cap-v2-0-cbd1aa1064df@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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
all inboxes | Powered by JetHome®