public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Yangyu Chen <cyy@cyyself.name>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>,
	ajones@ventanamicro.com, alex@ghiti.fr, alistair.francis@wdc.com,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	bjorn@kernel.org, "Conor Dooley" <conor.dooley@microchip.com>,
	cooper.qu@linux.alibaba.com, dbarboza@ventanamicro.com,
	"Qingfang Deng" <dqfext@gmail.com>,
	eric.huang@linux.alibaba.com, heiko@sntech.de,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	philipp.tomsich@vrull.eu, samuel.holland@sifive.com,
	zhiwei_liu@linux.alibaba.com, "Guo Ren" <guoren@kernel.org>
Subject: Re: [PATCH v3 2/2] riscv: T-Head: Test availability bit before enabling MAE errata
Date: Mon, 8 Apr 2024 10:06:55 +0100	[thread overview]
Message-ID: <20240408-semisweet-class-39239c279adc@spud> (raw)
In-Reply-To: <tencent_D6D1043732E63644A4B1838F4210499BCF05@qq.com>


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

On Mon, Apr 08, 2024 at 04:21:24PM +0800, Yangyu Chen wrote:
> 
> So the solution might be to have some property like `xtheadmae` and test
> th.sxstatus whether it has MAEE bit set when we have this in ISA string in
> the DT rather than have MAE enabled for sure if `xtheadmae` exists as
> discussed before. This will require changing the DT.

Yeah, I think I don't mind what you propose, as long as we define in the
binding that "xtheadmae" means the hardware supports it ***AND*** the bit
in the CSR. That's easier on firmware and taps into the existing
support in the kernel. I think it's more consistent with how we handle
the standard extensions to do it that way than to assume "xtheadmae"
being present means that it is enabled.

> However, since the
> C908, the first core released by T-Head that supports MAE with non-zero
> arch_id and imp_id hasn't merged to mainline yet. It's time to add this
> dt-binding and some code to probe it. I can have it tested on K230
> recently. Whatever, this patch can go first.

I don't think adding something like this should block merging the
initial c908 support though, can easily be follow-up work. I'll apply
the k230 stuff Wednesday if nothing has come in on it by then.

Cheers,
Conor.

[-- 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:[~2024-04-08  9:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 21:32 [PATCH v3 0/2] RISC-V: Test th.sxstatus.MAEE bit before enabling MAEE Christoph Müllner
2024-04-07 21:32 ` [PATCH v3 1/2] riscv: thead: Rename T-Head PBMT to MAE Christoph Müllner
2024-04-07 21:32 ` [PATCH v3 2/2] riscv: T-Head: Test availability bit before enabling MAE errata Christoph Müllner
2024-04-08  1:58   ` Yangyu Chen
2024-04-08  6:00     ` Christoph Müllner
2024-04-08  7:36       ` Yangyu Chen
2024-04-08  7:55         ` Christoph Müllner
2024-04-08  8:10           ` Conor Dooley
2024-04-08  8:21             ` Yangyu Chen
2024-04-08  9:06               ` Conor Dooley [this message]
2024-04-25 23:00 ` [PATCH v3 0/2] RISC-V: Test th.sxstatus.MAEE bit before enabling MAEE patchwork-bot+linux-riscv

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=20240408-semisweet-class-39239c279adc@spud \
    --to=conor@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=alistair.francis@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@kernel.org \
    --cc=christoph.muellner@vrull.eu \
    --cc=conor.dooley@microchip.com \
    --cc=cooper.qu@linux.alibaba.com \
    --cc=cyy@cyyself.name \
    --cc=dbarboza@ventanamicro.com \
    --cc=dqfext@gmail.com \
    --cc=eric.huang@linux.alibaba.com \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=samuel.holland@sifive.com \
    --cc=zhiwei_liu@linux.alibaba.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