From: Jonas Jelonek <jonas@jonasjelonek.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>,
Russell Senior <russell@personaltelco.net>,
Jonas Jelonek <jonas@jonasjelonek.de>
Subject: [PATCH net-next v2 1/3] dt-bindings: net: pse-pd: realtek,pse-mcu: add VMAIN supply
Date: Mon, 16 Nov 2026 11:52:22 +0000 [thread overview]
Message-ID: <20261116115224.1454885-2-jonas@jonasjelonek.de> (raw)
In-Reply-To: <20261116115224.1454885-1-jonas@jonasjelonek.de>
Describe the VMAIN supply at the MCU controller level. The rail feeds the
PoE subsystem as a whole rather than an individual PI. Its regulator power
budget defines the aggregate limit programmed into the MCU.
Require a finite regulator power budget dedicated to this MCU, representing
the PoE power allocation of the system. The rail is available independently
of the host driver, which uses the supply reference for budget accounting.
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
Reviewed-by: Kory Maincent <kory.maincent@bootlin.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
---
.../bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml b/Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml
index 526f8525bb4d..6acb5fb641c1 100644
--- a/Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml
+++ b/Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml
@@ -92,6 +92,15 @@ properties:
asserted.
maxItems: 1
+ vmain-supply:
+ description:
+ Regulator representing the PoE power allocation of the 44-57V VMAIN
+ supply. This MCU must be its only power-budget consumer. Its unclaimed
+ power budget is used to configure the MCU global PoE power budget. The
+ regulator must define a finite regulator-power-budget-milliwatt value.
+ The supply is available independently of the host driver and is used
+ for power-budget accounting only.
+
required:
- compatible
--
2.53.0
next prev parent reply other threads:[~2026-11-16 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 11:52 [PATCH net-next v2 0/3] net: pse-pd: realtek-pse-mcu: establish power management configuration Jonas Jelonek
2026-11-16 11:52 ` Jonas Jelonek [this message]
2026-11-16 11:52 ` [PATCH net-next v2 2/3] net: pse-pd: realtek-pse-mcu: ensure MCU does dynamic power management Jonas Jelonek
2026-11-16 11:52 ` [PATCH net-next v2 3/3] net: pse-pd: realtek-pse-mcu: configure global power budget Jonas Jelonek
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=20261116115224.1454885-2-jonas@jonasjelonek.de \
--to=jonas@jonasjelonek.de \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=russell@personaltelco.net \
--cc=sander@svanheule.net \
/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®