[PATCH 7/8] riscv: dts: spacemit: add initial device tree of SpacemiT K3 SoC
Guodong Xu
guodong at riscstar.com
Mon Dec 22 01:27:04 PST 2025
On Sat, Dec 20, 2025 at 10:48 AM Yao Zi <me at ziyao.cc> wrote:
>
> On Fri, Dec 19, 2025 at 10:03:24AM +0800, Guodong Xu wrote:
> > Hi, Conor and Heinrich
> >
> > On Thu, Dec 18, 2025 at 8:56 AM Conor Dooley <conor at kernel.org> wrote:
> > >
> > > On Wed, Dec 17, 2025 at 09:07:14AM +0100, Heinrich Schuchardt wrote:
> > > > On 12/17/25 08:11, Guodong Xu wrote:
> > >
> > > > > Specifically, I must adhere to
> > > > > Documentation/devicetree/bindings/riscv/extensions.yaml (and cpus.yaml for
> > > > > properties like 'riscv,sv39' which stands for the extension Sv39). If I
> > > > > add extension strings that are not yet defined in these schemas, such as
> > > > > supm, running 'make dtbs_check W=3' fails with: 'supm' is not one of
> > > > > ['i', 'm', 'a', ...], followed by "Unevaluated properties are not allowed."
> > > >
> > > > If Documentation/devicetree/bindings/riscv/extensions.yaml is incomplete
> > > > with respect to ratified extensions, I guess the right approach is to amend
> > > > it and not to curtail the CPU description.
> > >
> > > Absolutely. If the cpu supports something that is not documented, then
> > > please document it rather than omit from the devicetree.
> >
>
> ...
>
> > Strictly describing the SpacemiT X100/K3 (or any core) as RVA23-compliant
> > requires adding these extensions that are currently missing from
> > the kernel bindings:
> > RVA23U64: Ziccif, Ziccamoa, Zicclsm, Za64rs
> > RVA23S64: Ss1p13, Ssccptr, Sstvecd, Sstvala, Sscounterenw, Ssu64xl,
> > Sha, Shcounterenw, Shvstvala, Shtvala, Shvstvecd, Shvsatpa, Shgatpa
> > Plus 'Supm', 'Zic64b', 'Ssstateen', 'B' where the kernel supports them but
>
> Please note B is just the abbreviation of "zba", "zbb", and "zbs", all
> of them have been documented in extensions.yaml.
>
Yes, Yao Zi. I'll include 'B' in my next version, and add the schema check.
Thanks.
BR,
Guodong Xu
> > they are not literally documented in yaml.
> >
> > Is this approach acceptable to you? If so, I will proceed with submitting them.
> >
> > Thank you very much.
> >
> > Best regards,
> > Guodong Xu
> >
>
> Regards,
> Yao Zi
More information about the linux-riscv
mailing list