[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-9e03f021-961d-44f3-81c1-9c09abd3662b@palmer-ri-x1c9a>
Date: Thu, 22 Jun 2023 12:43:13 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: Conor Dooley <conor@...nel.org>
CC: Conor Dooley <conor.dooley@...rochip.com>,
Paul Walmsley <paul.walmsley@...ive.com>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org,
Alistair Francis <Alistair.Francis@....com>,
ajones@...tanamicro.com, apatel@...tanamicro.com,
atishp@...shpatra.org, jrtc27@...c27.com, rick@...estech.com,
ycliang@...estech.com, oleksii.kurochko@...il.com,
linux-riscv@...ts.infradead.org, qemu-riscv@...gnu.org,
u-boot@...ts.denx.de, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: riscv: deprecate riscv,isa
On Thu, 22 Jun 2023 11:59:32 PDT (-0700), Conor Dooley wrote:
> On Thu, Jun 22, 2023 at 11:25:35AM -0700, Palmer Dabbelt wrote:
>
>> Reviewed-by: Palmer Dabbelt <palmer@...osinc.com>
>> Acked-by: Palmer Dabbelt <palmer@...osinc.com>
>>
>> I'm not wed to any particular encoding for the properties, IMO that's more
>> of a decision for the DT folks. IMO the important bit is to just get away
>> from ISA strings and move towards some tightly-specified properties that
>> indicate how the HW actually behaves.
>
> I'm going to resubmit with Rob's list of strings. I'll keep your tags,
> since the spirit of the patch will be the same, with enforced meanings
> for each extension.
Works for me, thanks.
>
> Cheers,
> Conor.
Powered by blists - more mailing lists