From: Conor Dooley <conor@kernel.org>
To: Jessica Clarke <jrtc27@jrtc27.com>
Cc: "Anup Patel" <apatel@ventanamicro.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
conor+dt@kernel.org, "Heiko Stübner" <heiko@sntech.de>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Greg Favor" <gfavor@ventanamicro.com>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Andrew Waterman" <andrew@sifive.com>,
cyy@cyyself.name, "Conor Dooley" <conor.dooley@microchip.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Atish Patra" <atishp@atishpatra.org>,
"Krste Asanovic" <krste@sifive.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
"Mark Himelstein" <markhimelstein@riscv.org>,
"Andrew Jones" <ajones@ventanamicro.com>
Subject: Re: [RFC 0/6] Deprecate riscv,isa DT property?
Date: Sat, 13 May 2023 22:54:44 +0100 [thread overview]
Message-ID: <20230513-starlit-editor-058e609c10e4@spud> (raw)
In-Reply-To: <12BD8A89-CC3C-4C67-A501-7BB6BAD2EF59@jrtc27.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Sat, May 13, 2023 at 10:34:15PM +0100, Jessica Clarke wrote:
> On 13 May 2023, at 08:47, Anup Patel <apatel@ventanamicro.com> wrote:
> > For DT, users can either use "riscv,isa" DT property or use boolean
> > DT properties.
>
> Can we please not gratuitously have two ways of doing the same thing.
My intention, iff this goes ahead, is to deprecate that property, not
have some 'you can use "riscv,isa" or boolean, whichever you choose'
situation.
Obviously for backwards compatibility reasons parsing it as a fallback
would have be kept in Linux, so in theory a DT based Linux system "can
use either". It would be up to other platforms to decide whether they
would also like to do such a thing.
> I say this as a non-Linux OS that has to deal with whatever Linux
> decides to do with device trees. It is a total nuisance when you flip
> flop on things and we have to follow suit. Please consider the breakage
> very carefully.
I think I said it in my cover & in a later message, that I sent it here
only for first thoughts and my intention is to "send a non-RFC version
of this that also CCs the likes of QEMU, U-Boot & the BSD folk".
It's clearly not something that could be done unilaterally.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-13 21:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 18:16 [RFC 0/6] Deprecate riscv,isa DT property? Conor Dooley
2023-05-08 18:16 ` [RFC 1/6] dt-bindings: riscv: clarify what an unversioned extension means Conor Dooley
2023-05-13 17:46 ` Krzysztof Kozlowski
2023-05-08 18:16 ` [RFC 2/6] dt-bindings: riscv: add riscv,isa-extension-* property and incompatible example Conor Dooley
2023-05-13 17:50 ` Krzysztof Kozlowski
2023-05-13 18:00 ` Conor Dooley
2023-05-08 18:16 ` [RFC 3/6] RISC-V: deprecate riscv,isa & replace it with per-extension properties Conor Dooley
2023-05-08 18:16 ` [RFC 4/6] RISC-V: add support for riscv,isa-base property Conor Dooley
2023-05-08 18:16 ` [RFC 5/6] RISC-V: drop a needless check in print_isa_ext() Conor Dooley
2023-05-08 18:16 ` [RFC 6/6] riscv: dts: microchip: use new riscv,isa-extension-* properties for mpfs Conor Dooley
2023-05-11 21:27 ` [RFC 0/6] Deprecate riscv,isa DT property? Atish Patra
2023-05-11 21:47 ` Conor Dooley
2023-05-11 22:34 ` Atish Patra
2023-05-11 22:38 ` Conor Dooley
2023-05-12 18:01 ` Palmer Dabbelt
2023-05-12 19:40 ` Conor Dooley
2023-05-12 22:05 ` Conor Dooley
2023-05-12 23:20 ` Atish Patra
2023-05-12 23:52 ` Conor Dooley
2023-05-12 23:55 ` Palmer Dabbelt
2023-05-13 0:09 ` Conor Dooley
2023-05-13 0:38 ` Palmer Dabbelt
2023-05-13 7:47 ` Anup Patel
2023-05-13 21:34 ` Jessica Clarke
2023-05-13 21:54 ` Conor Dooley [this message]
2023-05-15 4:38 ` Sunil V L
2023-05-15 7:52 ` Conor Dooley
2023-05-12 18:08 ` Palmer Dabbelt
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=20230513-starlit-editor-058e609c10e4@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=andrew@sifive.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=gfavor@ventanamicro.com \
--cc=heiko@sntech.de \
--cc=jrtc27@jrtc27.com \
--cc=krste@sifive.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-riscv@lists.infradead.org \
--cc=markhimelstein@riscv.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=robh+dt@kernel.org \
/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).