From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 72CFEC61DC4 for ; Thu, 27 Aug 2026 16:13:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=B/EKi4WT6qbZUg4iVrk+/Jsbx1Av4yEAtb+SyBe61u4=; b=4FqenIQ3FkZVpp k4YvishMRo4SnHDRWWXWeS6R513cdMJsezsUkVhL/7WAT+Q3qrYpkctC6EAzbkRuU+c5XIOYyp7tC L18JyRoewU4UdEcP4UF5ezq+D99Sl+GccTGFOvxtsk9/zuWZrD/M1ETQTxVSEsrpZ7mm2jlhOYPeO RRNchXUsQqttYaPEXBCI/cvRIee3pNfUVH5SbesUoCrNAsug1yulIdykCmlM+bn0SSYzrbu2TaMUM 7OLfPpaGwROXgX3AsMGjPg6k3aYNduUU/Wzeas/s0lg0DoLJ3naxf9hQEmWTNiqIk0j9H4A3U3iiL soAlbmDI4uPziEk79AjA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wzcis-00000004IX5-1JEc; Thu, 27 Aug 2026 16:13:02 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wzcio-00000004IWi-3TvQ; Thu, 27 Aug 2026 16:12:59 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id F0195600D3; Thu, 27 Aug 2026 16:12:57 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D3BBD1F000E9; Thu, 27 Aug 2026 16:12:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787847177; bh=bW5p7sg37lG2e7fiC+a/D7ld9RprkWkK8hWMZ55d2KQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=WaHaCd9Nu9G4ArFwXjQgTuCAqV3k/KIa6ykHqQucoty/1nkrunZyB0pBKCdvzyJ/A Ls2T/PweYhD5O5dc0IvmDhpc//CpGRjKLtQwXvnZNApHJ4+San/oHDey2lgt8tYYIQ Wl/fwE5FKLGY6pU3hYawPK45QoE5PUIg3rk3/jnNZMhHyJV9ywEJ5AV1LRaCeZRnLS JvoBdUyNriec390XSIhLPFBHvHh2vJDRF5on5TaUqE9NlaPNDlyiO3ESQku7P8DKS4 WL3MMZH6HwQ5IIyFw5XW4oKVAs8A0ItiLN3J3PrRrwL93PdmPUTbsJcgt3xEOX6yot ycpe+kcOu0hag== Date: Thu, 27 Aug 2026 21:42:53 +0530 From: Vinod Koul To: Manivannan Sadhasivam Cc: Sebastian Reichel , Neil Armstrong , Heiko Stuebner , Frank Wang , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Thinh Nguyen , Greg Kroah-Hartman , Philipp Zabel , Andy Yan , Dmitry Baryshkov , Yubing Zhang , Alexey Charkov , Igor Paunovic , linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, kernel@collabora.com, devicetree@vger.kernel.org, linux-usb@vger.kernel.org, Sashiko , William Wu Subject: Re: [PATCH v14 00/38] phy: rockchip: usbdp: Clean up the mess Message-ID: References: <20260813-rockchip-usbdp-cleanup-v14-0-b5ad9c68fa11@collabora.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: linux-rockchip@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Upstream kernel work for Rockchip platforms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+linux-rockchip=archiver.kernel.org@lists.infradead.org On 19-08-26, 05:31, Manivannan Sadhasivam wrote: > On Tue, Aug 18, 2026 at 11:42:50PM +0200, Sebastian Reichel wrote: > > Hello Mani, > > > > On Tue, Aug 18, 2026 at 11:27:07AM +0200, Manivannan Sadhasivam wrote: > > > On Thu, Aug 13, 2026 at 10:51:43PM +0200, Sebastian Reichel wrote: > > > > This series does a major overhaul of the Rockchip USBDP driver. The > > > > initial main goal was to add USB-C DP AltMode support to the RK3576 > > > > and RK3588 and this series still prepares the PHY driver for exactly > > > > that. But in addition to that I uncovered a huge amount of issues, > > > > that are fixed along the way. Some of the more interesting ones are: > > > > > > > > * Currently the driver might trigger a fatal SError on USB-C hotplug, > > > > since re-initializing the PHY stops the clocks going to DWC3. If > > > > the DWC3 driver tries to access its registers at the same time the > > > > system will crash. > > > > * The DWC3 hardware can get into a buggy state when the PHY is > > > > disabled, which results in the PHY not coming up properly again. > > > > * Swithcing the USB-C connector orientation during hotplug breaks > > > > USB3 speed, as the PHY is not being re-initialized. > > > > * The code always enables DP mode when USB-C is involved. > > > > * The driver has some locking issues uncovered by Sashiko. > > > > > > > > In addition to these bigger ones, Sashiko also found a bunch of > > > > minor problems, which are mostly harmless, but were fixed while > > > > going at it. > > > > > > 38 patches for a single series is too much to review. Please > > > consider splitting it up into multiple series not exceeding ~10 > > > patches per series. Thanks! > > > > So let me summarize: > > > > - Vinod wants Sashiko feedback to be acted upon > > This is fine. > > > - linux-phy does not want series with dependencies ( [0] ) > > This is not something I expected. I read the reply from Vladimir in [0], and > he seems to be sharing the limitation of the build tool of linux-phy. But I > don't think that's a big deal. Every subsystem allows sending dependent series > as long as the dependency is clearly described in the cover letter and now with > b4. So I don't see why linux-phy should be different. If you combine all patches > in one series, it makes it impossible for a human reviewer to review it > thoroughly. > > @vinod: Can you share your view on splitting the series with dependency? I build locally when I apply and if there is a dependency on fixes, cover letter mentioning, I do merge fixes. So not sure from a process pov where the gap might be. Builders are helpful for review and checking sanity :-) I would say it would be helpful, if it was split. I can pick fixes now and get that in for rc. While the rest can go into next -- ~Vinod _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip