Re: [PATCH v18 0/7] usb: dwc3: introduce Rockchip glue driver

From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	Igor Paunovic <royalnet026@gmail.com>,
	 linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-rockchip@lists.infradead.org,
	linux-phy@lists.infradead.org, kernel@collabora.com,
	 Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Subject: Re: [PATCH v18 0/7] usb: dwc3: introduce Rockchip glue driver
Date: Mon, 2 Nov 2026 00:46:01 +0100	[thread overview]
Message-ID: <aufM3PCuU9CM8zFo@venus> (raw)
In-Reply-To: <179353091270.2955.16595397888583885694.b4-reply@b4>

[-- Attachment #1.1: Type: text/plain, Size: 1743 bytes --]

Hi,

On Sun, Nov 01, 2026 at 04:31:52PM +0530, Manivannan Sadhasivam wrote:
> On 2026-10-21 20:05 +0200, Sebastian Reichel wrote:
> > The recent Rockchip platform have a combined PHY, which does USB3 and
> > DisplayPort as well as muxing the lines in arbitrary order. Changing its
> > enabled functionality requires a PHY reset and as the PHY provides a
> > clock to the DWC3 controller, this can result in an SError. Apart from
> > that the PHY might not start up correctly when the DWC3 PIPE interface
> > is running. This series prepares a Rockchip specific DWC3 glue driver to
> > help out with these problems. To become useful more patches are needed
> > on the Rockchip USBDP PHY side, which are send separately.
> > 
> > This was split from the USBDP cleanup series. v17 has a dependency on
> > the patches that have been merged to phy's for-next branch. There are
> > some additional Rockchip USBDP phy fixes, which depend on this series
> > (which is effectively also a fix).
> 
> What is the merge strategy for this series?

I see these options (ordered by my preference):

1: Vinod merges everything; the USB side is mostly a new driver
   and thus there is not much conflict potential

2: Vinod provides an immutable branch with the first two patches,
   USB tree merges the immutable branch and the remaining series.

3: Everything is merged through USB; this would block the final
   cleanup for USBDP from being applied for yet another cycle.

4: Vinod merges patches 1+2, USB patches are merged one cycle
   later and final USBDP patches are merged two cycles later.

P.S.: I will have to send another version for the correct Sashiko
feedback on the DWC3 side.

Greetings,

-- Sebastian

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 112 bytes --]

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy