From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Ze Huang <huang.ze@linux.dev>
Cc: Junzhong Pan <panjunzhong@linux.spacemit.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] phy: k1-usb: add disconnect function support
Date: Thu, 12 Feb 2026 11:24:00 +0000 [thread overview]
Message-ID: <aY24UOvYsnh_7ZCO@pie> (raw)
In-Reply-To: <20260212-11-k3-usb2-phy-v1-2-43578592405d@kernel.org>
On Thu, Feb 12, 2026 at 09:38:55AM +0800, Yixun Lan wrote:
> A disconnect status BIT of USB2 PHY need to be cleared, otherwise
> it will fail to work properly during next connection when devices
> connect to roothub directly.
This sounds like a bug. Does it affect K1 SoC as well? If so, I think
it deserves a Fixes tag and backporting.
> Signed-off-by: Yixun Lan <dlan@kernel.org>
Best regards,
Yao Zi
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Ze Huang <huang.ze@linux.dev>
Cc: Junzhong Pan <panjunzhong@linux.spacemit.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] phy: k1-usb: add disconnect function support
Date: Thu, 12 Feb 2026 11:24:00 +0000 [thread overview]
Message-ID: <aY24UOvYsnh_7ZCO@pie> (raw)
In-Reply-To: <20260212-11-k3-usb2-phy-v1-2-43578592405d@kernel.org>
On Thu, Feb 12, 2026 at 09:38:55AM +0800, Yixun Lan wrote:
> A disconnect status BIT of USB2 PHY need to be cleared, otherwise
> it will fail to work properly during next connection when devices
> connect to roothub directly.
This sounds like a bug. Does it affect K1 SoC as well? If so, I think
it deserves a Fixes tag and backporting.
> Signed-off-by: Yixun Lan <dlan@kernel.org>
Best regards,
Yao Zi
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Ze Huang <huang.ze@linux.dev>
Cc: Junzhong Pan <panjunzhong@linux.spacemit.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] phy: k1-usb: add disconnect function support
Date: Thu, 12 Feb 2026 11:24:00 +0000 [thread overview]
Message-ID: <aY24UOvYsnh_7ZCO@pie> (raw)
In-Reply-To: <20260212-11-k3-usb2-phy-v1-2-43578592405d@kernel.org>
On Thu, Feb 12, 2026 at 09:38:55AM +0800, Yixun Lan wrote:
> A disconnect status BIT of USB2 PHY need to be cleared, otherwise
> it will fail to work properly during next connection when devices
> connect to roothub directly.
This sounds like a bug. Does it affect K1 SoC as well? If so, I think
it deserves a Fixes tag and backporting.
> Signed-off-by: Yixun Lan <dlan@kernel.org>
Best regards,
Yao Zi
next prev parent reply other threads:[~2026-02-12 11:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 1:38 [PATCH 0/3] phy: spacemit: Add USB2 PHY support for K3 SoC Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 1:38 ` [PATCH 1/3] dt-bindings: phy: spacemit: k3: add USB2 PHY support Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 12:03 ` Krzysztof Kozlowski
2026-02-12 12:03 ` Krzysztof Kozlowski
2026-02-12 12:03 ` Krzysztof Kozlowski
2026-02-12 1:38 ` [PATCH 2/3] phy: k1-usb: add disconnect function support Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 11:24 ` Yao Zi [this message]
2026-02-12 11:24 ` Yao Zi
2026-02-12 11:24 ` Yao Zi
2026-02-12 14:43 ` Yixun Lan
2026-02-12 14:43 ` Yixun Lan
2026-02-12 14:43 ` Yixun Lan
2026-02-12 1:38 ` [PATCH 3/3] phy: k1-usb: k3: add USB2 PHY support Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 1:38 ` Yixun Lan
2026-02-12 11:30 ` Yao Zi
2026-02-12 11:30 ` Yao Zi
2026-02-12 11:30 ` Yao Zi
2026-02-12 14:35 ` Yixun Lan
2026-02-12 14:35 ` Yixun Lan
2026-02-12 14:35 ` Yixun Lan
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=aY24UOvYsnh_7ZCO@pie \
--to=me@ziyao.cc \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=huang.ze@linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=panjunzhong@linux.spacemit.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.