From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Sean Anderson <sean.anderson@seco.com>,
Anup Patel <anup@brainfault.org>,
Andrew Jones <ajones@ventanamicro.com>,
palmer@dabbelt.com, Paul Walmsley <paul.walmsley@sifive.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alistair Francis <alistair.francis@wdc.com>,
Anup Patel <apatel@ventanamicro.com>,
Atish Patra <atishp@atishpatra.org>,
Jessica Clarke <jrtc27@jrtc27.com>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
linux-riscv@lists.infradead.org, qemu-riscv@nongnu.org,
u-boot@lists.denx.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: riscv: deprecate riscv,isa
Date: Tue, 13 Jun 2023 07:28:34 -0600 [thread overview]
Message-ID: <CAL_Jsq+CJ-mEcEujd5Sk4SLvgTfUX1A7NRXYcMDqkoViDYxTXw@mail.gmail.com> (raw)
In-Reply-To: <20230612-relic-fetal-1beeae3455aa@spud>
On Mon, Jun 12, 2023 at 3:23 PM Conor Dooley <conor@kernel.org> wrote:
>
> Rob,
> Before I press on with more versions...
>
> On Thu, Jun 08, 2023 at 08:30:28PM +0100, Conor Dooley wrote:
> > On Thu, Jun 08, 2023 at 01:15:37PM -0600, Rob Herring wrote:
> > > On Tue, May 30, 2023 at 03:12:12PM +0100, Conor Dooley wrote:
> > > > On Thu, May 18, 2023 at 10:42:34PM +0100, Conor Dooley wrote:
> > > > > On Thu, May 18, 2023 at 02:30:53PM -0400, Sean Anderson wrote:
> > > >
> > > > > >
> > > > > > Why not just have something like
> > > > > >
> > > > > > mycpu {
> > > > > > ...
> > > > > > riscv,isa {
> > > > > > i;
> > > > > > m;
> > > > > > a;
> > > > > > zicsr;
> > > > > > ...
> > >
> > > I prefer property names be globally unique. The tools are geared towards
> > > that too. That's largely a symptom of having 0 type information in the
> > > DT.
> > >
> > > For example if you had an extension called 'reg', it would be a problem.
> >
> > Per the current ISA rules, that'd not be valid. But then again, I do
> > have trust issues & it's not like "reg" is the only property name in DT
> > land.
>
> ...you say "prefer" here. Is that a NAK, or a "you keep the pieces"?
Don't do the above node.
Rob
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-13 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 8:58 [PATCH v1] dt-bindings: riscv: deprecate riscv,isa Conor Dooley
2023-05-18 10:31 ` Andrew Jones
2023-05-18 11:15 ` Conor Dooley
2023-05-18 11:25 ` Conor Dooley
2023-05-18 13:43 ` Anup Patel
2023-05-18 14:06 ` Conor Dooley
2023-05-18 14:41 ` Palmer Dabbelt
2023-05-18 17:06 ` Conor Dooley
2023-05-18 18:30 ` Sean Anderson
2023-05-18 21:42 ` Conor Dooley
2023-05-30 14:12 ` Conor Dooley
2023-06-08 19:15 ` Rob Herring
2023-06-08 19:30 ` Conor Dooley
2023-06-12 21:23 ` Conor Dooley
2023-06-13 13:28 ` Rob Herring [this message]
2023-06-13 14:11 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL_Jsq+CJ-mEcEujd5Sk4SLvgTfUX1A7NRXYcMDqkoViDYxTXw@mail.gmail.com \
--to=robh@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jrtc27@jrtc27.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qemu-riscv@nongnu.org \
--cc=rick@andestech.com \
--cc=sean.anderson@seco.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).