public inbox for opensbi@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Anup Patel <apatel@ventanamicro.com>
Cc: Atish Patra <atishp@rivosinc.com>,
	Anup Patel <anup@brainfault.org>,
	 opensbi@lists.infradead.org
Subject: Re: [PATCH] lib: Allow custom CSRs in csr_read_num() and csr_write_num()
Date: Tue, 30 Sep 2025 10:47:17 -0500	[thread overview]
Message-ID: <20250930-110b0b58ebc9ec8c19d727f5@orel> (raw)
In-Reply-To: <20250930153216.89853-1-apatel@ventanamicro.com>

On Tue, Sep 30, 2025 at 09:02:16PM +0530, Anup Patel wrote:
> Some of the platforms use platform specific CSR access functions for
> configuring implementation specific CSRs (such as PMA registers).
> 
> Extend the common csr_read_num() and csr_write_num() to allow custom
> CSRs so that platform specific CSR access functions are not needed.
> 
> Signed-off-by: Anup Patel <apatel@ventanamicro.com>
> ---
>  include/sbi/riscv_encoding.h       |  34 ++++++++
>  lib/sbi/riscv_asm.c                | 135 ++++++++++++++++++-----------
>  platform/generic/andes/andes_pma.c |  90 ++-----------------
>  platform/generic/mips/p8700.c      |  76 +---------------
>  4 files changed, 127 insertions(+), 208 deletions(-)
>

Reviewed-by: Andrew Jones <ajones@ventanamicro.com>

-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

  reply	other threads:[~2025-09-30 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 15:32 [PATCH] lib: Allow custom CSRs in csr_read_num() and csr_write_num() Anup Patel
2025-09-30 15:47 ` Andrew Jones [this message]
2025-10-21 14:12 ` Anup Patel

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=20250930-110b0b58ebc9ec8c19d727f5@orel \
    --to=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@rivosinc.com \
    --cc=opensbi@lists.infradead.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