From: Andrew Lunn <andrew@lunn.ch>
To: Robert Marko <robert.marko@sartura.hr>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, lxu@maxlinear.com,
hkallweit1@gmail.com, linux@armlinux.org.uk, lgirdwood@gmail.com,
broonie@kernel.org, michael@walle.cc, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
lrosu@maxlinear.com, luka.perkov@sartura.hr
Subject: Re: [PATCH net-next v3 3/5] net: phy: mxl-gpy: release MxL86211C Super Isolate
Date: Tue, 20 Oct 2026 14:48:33 +0200 [thread overview]
Message-ID: <21892f3a-8e0a-4c72-938c-b2e77b9f0dbf@lunn.ch> (raw)
In-Reply-To: <20261020093655.344585-3-robert.marko@sartura.hr>
On Tue, Oct 20, 2026 at 11:35:36AM +0200, Robert Marko wrote:
> The MxL86211C can be strapped into Super Isolate mode, leaving the PHY
> halted after reset until software releases it.
>
> Release Super Isolate before gpy_probe() reads the firmware version. Do it
> again in config_init, where optional VDDP setup is reapplied after each
> hardware reset.
This needs expanding a bit. All reset actions by the core should
happen before probe. So why is releasing isolate in probe not
sufficient?
If the MDIO bus voltages are lost, what else is lost? Should
phy_init_hw() be called again?
Andrew
next prev parent reply other threads:[~2026-10-20 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:35 [PATCH net-next v3 1/5] dt-bindings: net: maxlinear: add MxL86211C VDDP supply Robert Marko
2026-10-20 9:35 ` [PATCH net-next v3 2/5] net: phy: mxl-gpy: " Robert Marko
2026-10-20 12:39 ` Andrew Lunn
2026-10-20 12:49 ` Robert Marko
2026-10-20 12:56 ` Andrew Lunn
2026-10-20 9:35 ` [PATCH net-next v3 3/5] net: phy: mxl-gpy: release MxL86211C Super Isolate Robert Marko
2026-10-20 12:48 ` Andrew Lunn [this message]
2026-10-20 13:04 ` Robert Marko
2026-10-20 14:06 ` Andrew Lunn
2026-10-20 9:35 ` [PATCH net-next v3 4/5] dt-bindings: net: maxlinear: add MxL86211C lane mapping support Robert Marko
2026-10-20 9:35 ` [PATCH net-next v3 5/5] net: phy: mxl-gpy: support MxL86211C lane mapping Robert Marko
2026-10-21 1:32 ` [PATCH net-next v3 1/5] dt-bindings: net: maxlinear: add MxL86211C VDDP supply Jakub Kicinski
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=21892f3a-8e0a-4c72-938c-b2e77b9f0dbf@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lrosu@maxlinear.com \
--cc=luka.perkov@sartura.hr \
--cc=lxu@maxlinear.com \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.marko@sartura.hr \
--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
all inboxes | Powered by JetHome®