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 CEFE3E75448 for ; Wed, 24 Dec 2025 11:49:17 +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=0HzlMMd8NIqZHLuJQTIx6MB5RnyKs4jKwnX93P5xID4=; b=RVSVfPnhL3yTSR ilBnEAnG6YGY/xK+D3hVeO3dbF3N6N6GLbYJmjwXkcYS0KyeBPJ+h5DPYqKHsJsVEAc+MyrNGItFQ 29PLa6UDNvrRLKOA0bcYfZDLmIwfMsW5GvZFzQzBuaSoXcMg8TED0alnlftjx31axsIheqX5VIIfg UYQkxj8hudJTOZqgKw/ahJUDFb+gfyWEwpUT5xO1SUCroUAsdiiOYfV8hlEgjrwEvDTdljZgVhUyz 2nWLB4vd38mnnhhmYguwaM07psKJMSHO6Mm/kb/kcjB/5YGihOWxNSij8BAoYkP7fRSS4RJiBmIWq b7bUXKfnxVSWGWJKMbmA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vYNMV-0000000GlZi-1dF4; Wed, 24 Dec 2025 11:49:03 +0000 Received: from woodpecker.gentoo.org ([140.211.166.183] helo=smtp.gentoo.org) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vYNMR-0000000GlZI-2n6p for linux-riscv@lists.infradead.org; Wed, 24 Dec 2025 11:49:02 +0000 Received: from localhost (unknown [116.232.18.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange secp256r1 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: dlan) by smtp.gentoo.org (Postfix) with ESMTPSA id 7430D341256; Wed, 24 Dec 2025 11:48:56 +0000 (UTC) Date: Wed, 24 Dec 2025 19:48:48 +0800 From: Yixun Lan To: Philipp Zabel Cc: Stephen Boyd , Michael Turquette , Alex Elder , Guodong Xu , Inochi Amaoto , Yao Zi , linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org, spacemit@lists.linux.dev Subject: Re: [PATCH 2/2] reset: spacemit: fix auxiliary device id Message-ID: <20251224114848-GYA1993014@gentoo.org> References: <20251220-06-k1-clk-common-v1-0-df28a0a91621@gentoo.org> <20251220-06-k1-clk-common-v1-2-df28a0a91621@gentoo.org> <20251220025926-GYA1962618@gentoo.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20251220025926-GYA1962618@gentoo.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20251224_034901_592301_B8F61BAD X-CRM114-Status: GOOD ( 17.99 ) 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 Philipp Zabel, I'd like to see your preference for this issue, see my comment below On 10:59 Sat 20 Dec , Yixun Lan wrote: > Hi Yao, > > On 02:40 Sat 20 Dec , Yao Zi wrote: > > On Sat, Dec 20, 2025 at 09:11:20AM +0800, Yixun Lan wrote: > > > Due to the auxiliary register procedure moved to ccu common module, > > > the auxiliary device id need to be adjusted, otherwise reset driver > > > will fail to probe. > > > > Does it mean the reset driver fails to probe with only PATCH 1 in the > > series applied? If so these two patches should probably be merged, or we > > will get unfunctional commits. > yes, it will fail with only patch 1 > > and no, I do not want to combine them together as they belong to > different subsystem. it shouldn't be a problem if they are accepted in > same merge window, or if people too picky to worry bisectable breakage, > then I would ask reset/clock maintainer an ack instead to make it go > via clock tree in one combined PR > I'd consider above approach is less optimal, would it ok if I create an immutable tag for this single patch, and send it to you? so can be shared by both clock and reset subsystem.. eventually reset driver should go via reset tree, and I also know Guodong is working on new reset driver to add support for incoming K3 SoC, which means potential conflicts or extra dependency.. -- Yixun Lan (dlan) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv