From: Kory Maincent <kory.maincent@bootlin.com>
To: Jonas Jelonek <jonas@jonasjelonek.de>,
Oleksij Rempel <o.rempel@pengutronix.de>,
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>
Subject: Re: [PATCH net-next 4/4] net: pse-pd: realtek-pse-mcu: avoid global disable on teardown
Date: Wed, 4 Nov 2026 10:45:18 +0100 [thread overview]
Message-ID: <5fba2b22-a7b6-4c9e-96e3-1ea41b984ba8@bootlin.com> (raw)
In-Reply-To: <20261103220312.860629-5-jonas@jonasjelonek.de>
On 11/3/26 23:03, Jonas Jelonek wrote:
> The driver installs a global-disable cleanup action when it enables a
> previously disabled MCU. Consequently, driver teardown stops all ports
> only when the MCU was disabled at probe, making the behavior depend on
> the initial firmware state.
>
> Leave the MCU globally enabled on teardown so an independently powered
> controller can continue autonomous delivery. This also allows persistent
> supply constraints to keep the rail powered without an explicit global
> disable command stopping the ports.
No SoB?
Also this patch is not related to power management. Please send it
standalone.
IMHO this should de send as a fix because we don't want to have a remove
behavior change according to the Linux version.
With all this change you can add my Reviewed-by.
> ---
> drivers/net/pse-pd/realtek-pse-mcu-core.c | 13 -------------
> 1 file changed, 13 deletions(-)
>
> diff --git a/drivers/net/pse-pd/realtek-pse-mcu-core.c b/drivers/net/pse-pd/realtek-pse-mcu-core.c
> index a90e19fb90e0..ab57c348436c 100644
> --- a/drivers/net/pse-pd/realtek-pse-mcu-core.c
> +++ b/drivers/net/pse-pd/realtek-pse-mcu-core.c
> @@ -894,13 +894,6 @@ static void rtpse_mcu_cleanup_vmain(void *data)
> regulator_disable(pse->vmain);
> }
>
> -static void rtpse_mcu_global_disable(void *data)
> -{
> - struct rtpse_mcu_ctrl *pse = data;
> -
> - rtpse_mcu_set_global_state(pse, false);
> -}
> -
> int rtpse_mcu_register(struct rtpse_mcu_ctrl *pse)
> {
> const struct rtpse_mcu_match_data *match;
> @@ -994,12 +987,6 @@ int rtpse_mcu_register(struct rtpse_mcu_ctrl *pse)
> if (ret && ret != -EOPNOTSUPP)
> return dev_err_probe(pse->dev, ret,
> "failed to enable PSE system\n");
> - if (!ret) {
> - ret = devm_add_action_or_reset(pse->dev,
> - rtpse_mcu_global_disable, pse);
> - if (ret)
> - return ret;
> - }
> }
>
> /*
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-11-04 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:03 [PATCH net-next 0/4] net: pse-pd: realtek-pse-mcu: establish power management configuration Jonas Jelonek
2026-11-03 22:03 ` [PATCH net-next 1/4] net: pse-pd: realtek-pse-mcu: ensure MCU does dynamic power management Jonas Jelonek
2026-11-04 10:02 ` Kory Maincent
2026-11-03 22:03 ` [PATCH net-next 2/4] dt-bindings: net: pse-pd: realtek,pse-mcu: add VMAIN supply Jonas Jelonek
2026-11-04 10:04 ` Kory Maincent
2026-11-04 21:49 ` Rob Herring (Arm)
2026-11-03 22:03 ` [PATCH net-next 3/4] net: pse-pd: realtek-pse-mcu: configure global power budget Jonas Jelonek
2026-11-04 11:32 ` Kory Maincent
2026-11-04 12:20 ` Jonas Jelonek
2026-11-04 12:36 ` Kory Maincent
2026-11-04 12:51 ` Jonas Jelonek
2026-11-03 22:03 ` [PATCH net-next 4/4] net: pse-pd: realtek-pse-mcu: avoid global disable on teardown Jonas Jelonek
2026-11-04 9:45 ` Kory Maincent [this message]
2026-11-04 9:51 ` 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=5fba2b22-a7b6-4c9e-96e3-1ea41b984ba8@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=jonas@jonasjelonek.de \
--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®