[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260113002123-GYA19926@gentoo.org>
Date: Tue, 13 Jan 2026 08:21:23 +0800
From: Yixun Lan <dlan@...too.org>
To: Conor Dooley <conor@...nel.org>
Cc: Guodong Xu <guodong@...cstar.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Paul Walmsley <pjw@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Samuel Holland <samuel.holland@...ive.com>,
Anup Patel <anup@...infault.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, Lubomir Rintel <lkundrak@...sk>,
Yangyu Chen <cyy@...self.name>,
Paul Walmsley <paul.walmsley@...ive.com>,
Heinrich Schuchardt <xypron.glpk@....de>,
Kevin Meng Zhang <zhangmeng.kevin@...ux.spacemit.com>,
Andrew Jones <ajones@...tanamicro.com>, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
spacemit@...ts.linux.dev, linux-serial@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>,
Heinrich Schuchardt <heinrich.schuchardt@...onical.com>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v4 00/11] riscv: spacemit: Add SpacemiT K3 SoC and K3
Pico-ITX board
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
--
Yixun Lan (dlan)
Powered by blists - more mailing lists