Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Xu Lu <luxu.kernel@bytedance.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, ajones@ventanamicro.com,
	brs@rivosinc.com, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	apw@canonical.com, joe@perches.com
Subject: Re: [PATCH 2/4] dt-bindings: riscv: Add Zalasr ISA extension description
Date: Mon, 1 Sep 2025 19:44:59 +0100	[thread overview]
Message-ID: <20250901-caravan-traps-9fb18046b458@spud> (raw)
In-Reply-To: <20250901113022.3812-3-luxu.kernel@bytedance.com>


[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]

On Mon, Sep 01, 2025 at 07:30:20PM +0800, Xu Lu wrote:
> Add description for the Zalasr ISA extension
> 
> Signed-off-by: Xu Lu <luxu.kernel@bytedance.com>
> ---
>  Documentation/devicetree/bindings/riscv/extensions.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
> index ede6a58ccf534..6b8c21807a2da 100644
> --- a/Documentation/devicetree/bindings/riscv/extensions.yaml
> +++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
> @@ -248,6 +248,11 @@ properties:
>              ratified at commit e87412e621f1 ("integrate Zaamo and Zalrsc text
>              (#1304)") of the unprivileged ISA specification.
>  
> +        - const: zalasr

This is out of order, no? zalrsc would come after zalasr.

> +          description: |
> +            The standard Zalasr extension for load-acquire/store-release as frozen
> +            at commit 194f0094 ("Version 0.9 for freeze") of riscv-zalasr.
> +
>          - const: zawrs
>            description: |
>              The Zawrs extension for entering a low-power state or for trapping
> -- 
> 2.20.1
> 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-09-01 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 11:30 [PATCH 0/4] riscv: Add Zalasr ISA exntesion support Xu Lu
2025-09-01 11:30 ` [PATCH 1/4] riscv: add ISA extension parsing for Zalasr Xu Lu
2025-09-01 11:30 ` [PATCH 2/4] dt-bindings: riscv: Add Zalasr ISA extension description Xu Lu
2025-09-01 18:44   ` Conor Dooley [this message]
2025-09-01 11:30 ` [PATCH 3/4] riscv: Instroduce Zalasr instructions Xu Lu
2025-09-01 11:30 ` [PATCH 4/4] riscv: Use Zalasr for smp_load_acquire/smp_store_release Xu Lu

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=20250901-caravan-traps-9fb18046b458@spud \
    --to=conor@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=apw@canonical.com \
    --cc=brs@rivosinc.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joe@perches.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=luxu.kernel@bytedance.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@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