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 5229BD31A05 for ; Wed, 14 Jan 2026 02:14:30 +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=2ueA5LxUEZn0SFqdFhHaAxa6oDiC1E3qxiGlelkzMa8=; b=dXqto0V7v8LLrL RDlX2USOLqONy9iPNtL9Ew3dZqLPdI0T8n+LSvdu4gDqx2Qqmvii9MEv75zzmter5c1kOVKzq/Axr yKHC/UyMVl7mx9V0EOFYtBiZ2GRhZpVh6JI2hdwVk9yPFDtC1+Gk6zDpsro5j3JJCYlWbKjijt5w/ 9idYhlqoA6UGkpRcpWIUKM5YsPTeOWz5py3O1Kd0OM4lN++DXHSJrke2+WQhOjQYtXUsYTt3dv+hv bDYD5AC3WLb+MVyFYD05+DVhxJD09QcIrb3IBFget4QzCYbYITJYcSqCzP9WxAUXNVa8zVwPUdMiG 4f0PAE1cbBCyDbD06oLQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vfqOl-00000007z0o-2T52; Wed, 14 Jan 2026 02:14:15 +0000 Received: from woodpecker.gentoo.org ([2001:470:ea4a:1:5054:ff:fec7:86e4] helo=smtp.gentoo.org) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vfqOi-00000007z0T-3fj0 for linux-riscv@lists.infradead.org; Wed, 14 Jan 2026 02:14:14 +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 DA74C341030; Wed, 14 Jan 2026 02:14:09 +0000 (UTC) Date: Wed, 14 Jan 2026 10:14:05 +0800 From: Yixun Lan To: Conor Dooley , Paul Walmsley Cc: Guodong Xu , Rob Herring , 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: <20260114021405-GYB25466@gentoo.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> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260113-swarm-mama-cbd7d0546578@spud> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260113_181412_958405_21613D0F X-CRM114-Status: GOOD ( 30.51 ) 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 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 -- Yixun Lan (dlan) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv