From: "Stefan O'Rear" <sorear@fastmail.com>
To: "Conor Dooley" <conor@kernel.org>,
"Samuel Holland" <samuel.holland@sifive.com>
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes v2 2/4] dt-bindings: riscv: Add ratified privileged ISA versions
Date: Tue, 13 Feb 2024 12:42:37 -0500 [thread overview]
Message-ID: <31024f04-e3e0-4bf9-beca-ebcd4f6fe51b@app.fastmail.com> (raw)
In-Reply-To: <20240213-limping-ether-adbdc205ebc6@spud>
On Tue, Feb 13, 2024, at 12:03 PM, Conor Dooley wrote:
> On Mon, Feb 12, 2024 at 07:37:33PM -0800, Samuel Holland wrote:
>> The baseline for the RISC-V privileged ISA is version 1.10. Using
>> features from newer versions of the privileged ISA requires the
>> supported version to be reported by platform firmware, either in the ISA
>> string (where the binding already accepts version numbers) or in the
>> riscv,isa-extensions property. So far two newer versions are ratified.
>>
>> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
>> ---
>>
>> Changes in v2:
>> - New patch for v2
>>
>> .../devicetree/bindings/riscv/extensions.yaml | 20 +++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
>> index 63d81dc895e5..7faf22df01af 100644
>> --- a/Documentation/devicetree/bindings/riscv/extensions.yaml
>> +++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
>> @@ -121,6 +121,16 @@ properties:
>> version of the privileged ISA specification.
>>
>> # multi-letter extensions, sorted alphanumerically
>
>> + - const: sm1p11
>
> Why are we beholden to this "1p11" format of RVI's? We have free choice
> of characters here, what's stopping us using "machine-v1.11", for
> example?
>
> Thanks,
> Conor.
I'd prefer to use names that are at least somewhat recognizable, e.g. in
the profiles spec, rather than making up something from whole cloth.
-s
>
>> + description:
>> + The standard Machine ISA v1.11, as ratified in the 20190608
>> + version of the privileged ISA specification.
>> +
>> + - const: sm1p12
>> + description:
>> + The standard Machine ISA v1.12, as ratified in the 20211203
>> + version of the privileged ISA specification.
>> +
>> - const: smaia
>> description: |
>> The standard Smaia supervisor-level extension for the advanced
>> @@ -134,6 +144,16 @@ properties:
>> added by other RISC-V extensions in H/S/VS/U/VU modes and as
>> ratified at commit a28bfae (Ratified (#7)) of riscv-state-enable.
>>
>> + - const: ss1p11
>> + description:
>> + The standard Supervisor ISA v1.11, as ratified in the 20190608
>> + version of the privileged ISA specification.
>> +
>> + - const: ss1p12
>> + description:
>> + The standard Supervisor ISA v1.12, as ratified in the 20211203
>> + version of the privileged ISA specification.
>> +
>> - const: ssaia
>> description: |
>> The standard Ssaia supervisor-level extension for the advanced
>> --
>> 2.43.0
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
> Attachments:
> * signature.asc
next prev parent reply other threads:[~2024-02-13 17:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 3:37 [PATCH -fixes v2 0/4] riscv: cbo.zero fixes Samuel Holland
2024-02-13 3:37 ` [PATCH -fixes v2 1/4] riscv: Fix enabling cbo.zero when running in M-mode Samuel Holland
2024-02-13 3:37 ` [PATCH -fixes v2 2/4] dt-bindings: riscv: Add ratified privileged ISA versions Samuel Holland
2024-02-13 8:50 ` Krzysztof Kozlowski
2024-02-13 14:25 ` Andrew Jones
2024-02-15 13:14 ` Conor Dooley
2024-02-16 15:41 ` Stefan O'Rear
2024-02-13 17:03 ` Conor Dooley
2024-02-13 17:07 ` Conor Dooley
2024-02-13 17:42 ` Stefan O'Rear [this message]
2024-02-13 18:00 ` Samuel Holland
2024-02-13 3:37 ` [PATCH -fixes v2 3/4] riscv: Add ISA extension parsing for Sm and Ss Samuel Holland
2024-02-13 15:14 ` Andrew Jones
2024-02-13 17:52 ` Stefan O'Rear
2024-02-13 18:18 ` Samuel Holland
2024-02-13 18:07 ` Conor Dooley
2024-02-13 20:22 ` Samuel Holland
2024-02-13 20:43 ` Stefan O'Rear
2024-02-13 23:15 ` Conor Dooley
2024-02-18 15:00 ` Samuel Holland
2024-02-18 17:02 ` Conor Dooley
2024-02-13 3:37 ` [PATCH -fixes v2 4/4] riscv: Save/restore envcfg CSR during CPU suspend Samuel Holland
2024-02-13 14:49 ` Andrew Jones
2024-02-13 17:53 ` Stefan O'Rear
2024-02-18 14:09 ` Samuel Holland
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=31024f04-e3e0-4bf9-beca-ebcd4f6fe51b@app.fastmail.com \
--to=sorear@fastmail.com \
--cc=ajones@ventanamicro.com \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=samuel.holland@sifive.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