From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Zhang Yubing <yubing.zhang@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
Igor Paunovic <royalnet026@gmail.com>
Subject: Re: [PATCH v15 1/6] phy: rockchip: usbdp: Add phy reset notification support
Date: Mon, 28 Sep 2026 18:18:13 +0200 [thread overview]
Message-ID: <arqLbsCgz9vkr3JG@venus> (raw)
In-Reply-To: <zbqy5gqtmprapsqpodoohyxs6gml6swkie6fy7fxszfvtfgz6c@eae55gdmknaw>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Hello Mani,
On Sat, Sep 26, 2026 at 09:54:56AM +0200, Manivannan Sadhasivam wrote:
> On Tue, Sep 15, 2026 at 05:32:48PM +0200, Sebastian Reichel wrote:
> > To resolve issues with running into permanent "cmn ana lcpll lock
> > timeout" errors after a few device replugs, add support for reset
> > notifications, which will be handled by the DWC3 driver to gracefully
> > handle the PHY being disabled. This avoids corrupting the controller's
> > internal state and the PIPE interface between the USB3 controller and
> > the PHY, thus fixing the issue.
> >
> > Tested-by: Igor Paunovic <royalnet026@gmail.com> # Orange Pi 5 Plus
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> > ---
> > drivers/phy/rockchip/phy-rockchip-usbdp.c | 19 +++++++++++++++++--
> > 1 file changed, 17 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/phy/rockchip/phy-rockchip-usbdp.c b/drivers/phy/rockchip/phy-rockchip-usbdp.c
> > index e748acdd2d31..0f39982c70b1 100644
> > --- a/drivers/phy/rockchip/phy-rockchip-usbdp.c
> > +++ b/drivers/phy/rockchip/phy-rockchip-usbdp.c
> > @@ -1004,24 +1004,39 @@ static int rk_udphy_power_on(struct rk_udphy *udphy, u8 mode)
> > }
> >
> > if (udphy->status == UDPHY_MODE_NONE) {
> > + phy_notify_reset(udphy->phy_u3, PHY_NOTIFY_PRE_RESET);
> > +
> > + rk_udphy_u3_port_disable(udphy, true);
>
> This change is not described in the commit message.
Good catch. I'm not sure when that sneaked in. I will split it into
its own follow-up patch.
FWIW these two things are a little bit interleaved:
resetting the PHY results in disabled clocks, results in SError when
dwc3 driver tries to access its registers during the PHY reset. This
is worked around by the u3 port disabling, which reroutes the clock.
But doing that increases the chance a lot, that the PHY does not
start up properly again, which requires the reset notifier bits.
Greetings,
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-28 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 15:32 [PATCH v15 0/6] phy: rockchip: usbdp: Clean up the mess (part 3) Sebastian Reichel
2026-09-15 15:32 ` [PATCH v15 1/6] phy: rockchip: usbdp: Add phy reset notification support Sebastian Reichel
2026-09-26 7:54 ` Manivannan Sadhasivam
2026-09-28 16:18 ` Sebastian Reichel [this message]
2026-09-15 15:32 ` [PATCH v15 2/6] phy: rockchip: usbdp: Drop -EPROBE_DEFER hack Sebastian Reichel
2026-09-26 7:55 ` Manivannan Sadhasivam
2026-09-15 15:32 ` [PATCH v15 3/6] phy: rockchip: usbdp: Rename mode to hw_mode Sebastian Reichel
2026-09-26 7:57 ` Manivannan Sadhasivam
2026-09-15 15:32 ` [PATCH v15 4/6] phy: rockchip: usbdp: Fix power state handling Sebastian Reichel
2026-09-26 7:59 ` Manivannan Sadhasivam
2026-09-15 15:32 ` [PATCH v15 5/6] phy: rockchip: usbdp: Re-init PHY on mux change Sebastian Reichel
2026-09-26 8:00 ` Manivannan Sadhasivam
2026-09-15 15:32 ` [PATCH v15 6/6] phy: rockchip: usbdp: Add USB-C state without DP enabled Sebastian Reichel
2026-09-26 8:42 ` Manivannan Sadhasivam
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=arqLbsCgz9vkr3JG@venus \
--to=sebastian.reichel@collabora.com \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=royalnet026@gmail.com \
--cc=vkoul@kernel.org \
--cc=yubing.zhang@rock-chips.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®