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 1865CFED2F5 for ; Fri, 13 Mar 2026 00:24:11 +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=DunpFRfCZ7cs01lvguRHaAKlo2TAU0h+LuxJNIcFSM8=; b=SCStebB+h9Ukbe sGzN8WYNlUKnrqbpmJ0ddLRuGIo/dd+S18w/mWcvRb8VasYIKtVXkfokCpLRU0FFPhR8JlZ8SkxAE OUuHv8oXhIMvvPGPBzr0CbO7vznw0bFcA1R/q1rChY28UhBZqEuSQ4NUwL8yTBADzbBlBbpf0r5yY h90lVPllH+ooHUvOEfxVUqU9sGzmfdkdjavt6RdDtU3p1Vf9r6KvuMNdRKsyZj3Itr3xzB5xxK2bl ryvVrYs6OqcAXGjPEPFrd7ZFZn3+mmWl7PIsdOPVlBGYvtxEtxfVoiAo9Jc4NGTRPxj0jHDmKl8xg 2BSC6H49X2rlB6Hov/uw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1w0qJv-0000000Futu-1JO5; Fri, 13 Mar 2026 00:24:03 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1w0qJr-0000000Fut2-3aAB for linux-riscv@lists.infradead.org; Fri, 13 Mar 2026 00:24:01 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id D8AD74033B; Fri, 13 Mar 2026 00:23:58 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6D183C4CEF7; Fri, 13 Mar 2026 00:23:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773361438; bh=GUdwY2Du7QdcArJbkRJOuPYgueFjUjS8kp8TVA2xanU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lVqfBwDQMgF5VH4QMuRtpy5s3xb2J8QBsmspLowwipidnNd9FdoJ4yi5JZxi2gQ93 Y8x8YjLIhWR2/1ANQRUSA1nABCY4SKyk0iONe8u8tFH5CnVvCJXnPqyTKzS4bR7Tt0 WsU0jKLkapnoBqx9g82kiNTPn8/k0u/l/VOo2WsEKmb9PZQ3noNhHqiM2Mrxb+FRQI pV7DQ3dWiYsF1zlHv+h8IAkSR9HcVl8sbOdmeSd9pPkaDptI+d5iuAoA9FyxDAqXVj oI0ahzlPXJN+6xRqP3Z84O9+HitWS2pwnKTy+R2h04SX1NjChpwToaTQxnfqhNspjV pBXEIj5Sm89MQ== Date: Fri, 13 Mar 2026 08:23:56 +0800 From: Yixun Lan To: Conor Dooley Cc: Philipp Zabel , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Junzhong Pan , Guodong Xu , devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, spacemit@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: soc: spacemit: k3: Decouple composite reset lines Message-ID: <20260313002356-GKJ302167@kernel.org> References: <20260312-01-k3-reset-usb-pci-v1-0-022b24b7340f@kernel.org> <20260312-01-k3-reset-usb-pci-v1-1-022b24b7340f@kernel.org> <0abfd76f49e5cedf7bfc84eb4d9a0a1d7543f6f8.camel@pengutronix.de> <20260312112858-GKH302167@kernel.org> <20260312-legume-unstitch-129b278e14d6@spud> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260312-legume-unstitch-129b278e14d6@spud> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260312_172359_981496_1E57B133 X-CRM114-Status: GOOD ( 26.93 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org Hi Conor, On 17:30 Thu 12 Mar , Conor Dooley wrote: > On Thu, Mar 12, 2026 at 07:28:58PM +0800, Yixun Lan wrote: > > Hi Philipp, > > > > On 12:09 Thu 12 Mar , Philipp Zabel wrote: > > > On Do, 2026-03-12 at 10:34 +0000, Yixun Lan wrote: > > > > Instead of grouping several different reset lines into one composite > > > > reset, decouple them to individual ones which make it more aligned > > > > with underlying hardware. > > > > > > > > The DWC3 USB host controller in K3 SoC has three reset lines - AHB, VCC, > > > > PHY. The PCIe controller also has three reset lines - DBI, Slave, Master. > > > > > > > > Signed-off-by: Yixun Lan > > > > --- > > > > include/dt-bindings/reset/spacemit,k3-resets.h | 42 ++++++++++++++++++++------ > > > > 1 file changed, 32 insertions(+), 10 deletions(-) > > > > > > > > diff --git a/include/dt-bindings/reset/spacemit,k3-resets.h b/include/dt-bindings/reset/spacemit,k3-resets.h > > > > index 79ac1c22b7b5..c12f8bd32047 100644 > > > > --- a/include/dt-bindings/reset/spacemit,k3-resets.h > > > > +++ b/include/dt-bindings/reset/spacemit,k3-resets.h > > > > @@ -97,11 +97,7 @@ > > > > #define RESET_APMU_SDH0 13 > > > > #define RESET_APMU_SDH1 14 > > > > #define RESET_APMU_SDH2 15 > > > > -#define RESET_APMU_USB2 16 > > > > -#define RESET_APMU_USB3_PORTA 17 > > > > -#define RESET_APMU_USB3_PORTB 18 > > > > -#define RESET_APMU_USB3_PORTC 19 > > > > -#define RESET_APMU_USB3_PORTD 20 > > > > > > This is backwards incompatible. > > > Are there any device trees using the APMU resets yet? > > > If not, I wonder if we should just renumber all APMU resets into a > > > contiguous range and try to get it into v7.0 as a fix. > > > > > No, there is currently no consumers, so I could rework them into a contiguous > > version, thanks for the suggestion > > Only as long as it goes into 7.0, IMO, as a fix. > Yes, that's the plan In this case, I would change my mind to add a Fixes tag explicitly(shouldn't hurt!) > > > Also, this breaks bisectability. > > > reset-spacemit-k3.c will fail to compile between patches 1 and 2. > > > > > I've tried a first version to squash the two patches, but got a checkpatch.pl complait > > for binding should follow into a separate patch. > > > > I can combine these two patches into one, is this Ok for you? > > Be very very very clear about why they're going together, otherwise you'll > get yelled at! Ok, will add comment for this, thanks for the tip. -- Yixun Lan (dlan) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv