[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1907301544560.4874@viisi.sifive.com>
Date: Tue, 30 Jul 2019 15:58:13 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Anup Patel <anup@...infault.org>
cc: Anup Patel <Anup.Patel@....com>, Albert Ou <aou@...s.berkeley.edu>,
Alan Kao <alankao@...estech.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Johan Hovold <johan@...nel.org>,
Atish Patra <Atish.Patra@....com>,
Palmer Dabbelt <palmer@...ive.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Allison Randal <allison@...utok.net>
Subject: Re: [PATCH 3/4] RISC-V: Support case insensitive ISA string
parsing.
On Sat, 27 Jul 2019, Anup Patel wrote:
> On Sat, Jul 27, 2019 at 1:46 PM Paul Walmsley <paul.walmsley@...ive.com> wrote:
> >
> > On Sat, 27 Jul 2019, Anup Patel wrote:
> >
> > > If your only objection is uppercase letter not agreeing with YMAL
> > > schema then why not fix the YMAL schema to have regex for RISC-V ISA
> > > string?
> >
> > I don't agree with you that the specification compels software to
> > accept arbitrary case combinations in the riscv,isa DT string.
>
> DT describes HW and HW follows RISC-V spec.
The RISC-V specification doesn't specify anything about how the DT data is
to describe the hardware.
> Enforcing software choices in DT YMAL schema is not correct approach.
That's the point of the DT YAML schemas.
- Paul
Powered by blists - more mailing lists