From: "Radim Krčmář" <radim.krcmar@oss.qualcomm.com>
To: "Andrew Jones" <andrew.jones@oss.qualcomm.com>,
<opensbi@lists.infradead.org>
Cc: "Anup Patel" <anup.patel@oss.qualcomm.com>,
"Atish Patra" <atish.patra@linux.dev>,
"Daniel Henrique Barboza" <daniel.barboza@oss.qualcomm.com>,
"Sunil V L" <sunilvl@oss.qualcomm.com>,
"opensbi" <opensbi-bounces@lists.infradead.org>
Subject: Re: [PATCH] lib: sbi: Fix hw a/d updating defaults
Date: Thu, 02 Apr 2026 16:56:43 +0200 [thread overview]
Message-ID: <DHIR92KV91LY.2IYTK8T6RQAJC@oss.qualcomm.com> (raw)
In-Reply-To: <20260401220845.190680-1-andrew.jones@oss.qualcomm.com>
2026-04-01T17:08:45-05:00, Andrew Jones <andrew.jones@oss.qualcomm.com>:
> The Svade dt-binding description states that Svadu should only
> be enabled at boot time when only Svadu is present in the DT.
> Ensure that's the case. Also, when only Svadu is supported,
> disable FWFT.PTE_AD_HW_UPDATING, as we need both to support
> toggling.
Does Svadu without Svade mean that both menvcfg.ADUE or henvcfg.ADUE are
read-only 1 (the ISA is vague enough to permit this), or is it just an
awkward way to configure the default, so HS mode must assume that
henvcfg.ADUE=0 will be Svade?
Svade is mandatory in RVA profiles, so the corner-case case it not
anything I expect to see...
Reviewed-by: Radim Krčmář <radim.krcmar@oss.qualcomm.com>
Thanks.
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2026-04-02 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 22:08 [PATCH] lib: sbi: Fix hw a/d updating defaults Andrew Jones
2026-04-02 14:56 ` Radim Krčmář [this message]
2026-04-02 16:24 ` Andrew Jones
2026-04-02 18:33 ` Radim Krčmář
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=DHIR92KV91LY.2IYTK8T6RQAJC@oss.qualcomm.com \
--to=radim.krcmar@oss.qualcomm.com \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup.patel@oss.qualcomm.com \
--cc=atish.patra@linux.dev \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=opensbi-bounces@lists.infradead.org \
--cc=opensbi@lists.infradead.org \
--cc=sunilvl@oss.qualcomm.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