From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 016462F39B8; Wed, 14 Jan 2026 20:26:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768422389; cv=none; b=M5J7JrhjNCTostz6lzTXw6ndPitrsVbw/+1MKNzc6ZVdhg2VVEgOYxrFayysHCrc+P96keSYOQPvUoi76E0OmThbPYjFMlaDgZG3F4pU2jC1D0pcSl+a/rOWWM2FvLP48R4gCwRSgNHaZdX4MQvN+3ndUwrNmj5GoSHQ9qCz8kw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768422389; c=relaxed/simple; bh=vqV4X8FhiR5xcn/VfYKZH7uJhedDHMIagvNMHSYct+o=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=LCGIkPQXABmCXfGsaDDRFjqxPa7HDXtDrZia8u9ujrymjSQgCnLQXfFCncZ7VmYk07Qbbz093xou2J7mZAem69BIwgzfjJFeAkzcQHkLATkP4AX6qXaPhkOhcuYxAvWImzPmWd8SLnwnJ904786GkpXifrFiUr32MIz2SyBcjUY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BowvJ5Lt; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BowvJ5Lt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6922FC4CEF7; Wed, 14 Jan 2026 20:26:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768422388; bh=vqV4X8FhiR5xcn/VfYKZH7uJhedDHMIagvNMHSYct+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BowvJ5Lt+EveWVyK2CKuOM6zhOHt/rj8qJW3wbmmFExumGGn+L3pSZ6vRMI2Wt9R1 /ud9nrrtreTFJaKypzi9j/r7wGYvV0Awa10GSqZw8elT9DTgk+LD1a12ecBfRg5gHl lK0PsQ3jc2moVL0/Ioxx4friGsCGt1/dM66EIsyLgJKY81WndC9jC+yr+ElqABzC/Z kztZVOxYBPTjMN72eXYdsjssThesXNusNZRJLvN10d7y4g1XPZyvIudBItRScOrFV5 2XzuMtbEm+2pn7Xc/GvB9PjAIZ/knzTcSOuXJqoWF3yGw2QiVPZDu2yWasA5lkdiM+ 7pSDs5jon0VxQ== Date: Wed, 14 Jan 2026 14:26:27 -0600 From: Rob Herring To: Yixun Lan Cc: Conor Dooley , Paul Walmsley , Guodong Xu , Krzysztof Kozlowski , Conor Dooley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Daniel Lezcano , Thomas Gleixner , Samuel Holland , Anup Patel , Greg Kroah-Hartman , Jiri Slaby , Lubomir Rintel , Yangyu Chen , Paul Walmsley , Heinrich Schuchardt , Kevin Meng Zhang , Andrew Jones , devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, spacemit@lists.linux.dev, linux-serial@vger.kernel.org, Krzysztof Kozlowski , Heinrich Schuchardt , Conor Dooley Subject: Re: [PATCH v4 00/11] riscv: spacemit: Add SpacemiT K3 SoC and K3 Pico-ITX board Message-ID: <20260114202627.GA3155416-robh@kernel.org> References: <20260110-k3-basic-dt-v4-0-d492f3a30ffa@riscstar.com> <20260112-shrivel-sarcastic-36d9acd2d96a@spud> <20260113002123-GYA19926@gentoo.org> <20260113-swarm-mama-cbd7d0546578@spud> <20260114021405-GYB25466@gentoo.org> Precedence: bulk X-Mailing-List: linux-serial@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260114021405-GYB25466@gentoo.org> On Wed, Jan 14, 2026 at 10:14:05AM +0800, Yixun Lan wrote: > > On 22:17 Tue 13 Jan , Conor Dooley wrote: > > On Tue, Jan 13, 2026 at 08:21:23AM +0800, Yixun Lan wrote: > > > Hi Conor, > > > > > > On 21:45 Mon 12 Jan , Conor Dooley wrote: > > > > On Sat, Jan 10, 2026 at 01:18:12PM +0800, Guodong Xu wrote: > > > > > > > > > Hi, Conor > > > > > > > > > > For the binding riscv/extensions.ymal, here's what changed in v3 (no > > > > > change in v4): > > > > > > > > > > 1. Dropped the patch of adding "supm" into extensions.yaml. At the same > > > > > time, I will start another patchset which implements the strategy > > > > > outlined by Conor in Link [2] and by Samuel in Link [3]. > > > > > > > > Okay, that seems reasonable to separate out. > > > > > > > > > > > > > > 2. Dropped the dependency checks for "sha" on "h", "shcounterenw", and > > > > > 6 others. "sha" implies these extensions, and it should be allowed > > > > > to be declared independently. Like "a" implies "zaamo" and "zalrsc". > > > > > > > > > > 3. Enchanced the dependency check of "ziccamoa" on "a". Specifically, > > > > > - added the dependency check of "ziccamoa" on "zaamo" or on "a". > > > > > - added the dependency check of "za64rs" on "zalrsc" or on "a". > > > > > - added the dependency check of "ziccrse" on "zalrsc" or "a". > > > > > The commit message of this patch is updated too, to better explain the > > > > > relationship between "ziccamoa", "za64rs", "ziccrse" and "a". > > > > > > > > > > 4. Enhanced checking dependency of "b" and "zba", "zbb", "zbs", making the > > > > > dependency check in both directions, as discussed in [4]. Since "b" > > > > > was ratified much later than its component extensions (zba/zbb/zbs), > > > > > existing software and kernels expect these explicit strings. This > > > > > bidirectional check ensures cores declaring "b" remain compatible > > > > > with older software that only recognizes zba/zbb/zbs. > > > > > > > > This I asked about in the relevant patch, I would like to know what your > > > > plan for adding the "b"s is. > > > > > > > .. > > > > Spacemit folks, I assume you weren't planning on taking the > > > > extensions.yaml stuff via your tree? If you weren't, I'll grab it once > > > > the question about b is answered. > > > > > > sure, please take extension stuff which are patches 6-9, for 1-5, it's > > > all about adding support for SpacemiT K3 SoC, to avoid petential conflicts, > > > I wouldn't mind if you also taking them? then I can handle the rest 10,11 for DT > > > > Stuff for spacemit is either for you or for the relevant subsystem > > maintainers. You're probably safe enough taking the > > timer/interrupt-controller stuff if the maintainers don't apply it in a > > reasonable period, it's not abnormal for those in particular to go via > > the platform maintainer in my experience. Just be clear that you have > > done so. I'm only interested in taking 6-9. > Hi Conor, > Ok, I got, thank you! > > Hi Paul Walmsley, > I assume you're responsible for more general riscv stuff with your > effective maintainer hat, so do you mind if I take patches 1-5 via SpacemiT > SoC tree? I think the potential conflicts should be low and easy to fix. > Or, in the other hand, just let me know which patches you would like > to take, then I will handle the rest. Thanks Paul would generally only ever take patch 1. You can take 1-5. The timer and interrupt-controller bindings tend to not get picked up by the subsystem unless there are driver changes too. Rob