From: E Shattow <e@freeshell.de>
To: u-boot@lists.u-boot-project.org, Yixun Lan <dlan@kernel.org>,
Tim Ouyang <tim609@andestech.com>,
Leo Liang <leo.liang@sifive.com>, Yao Zi <me@ziyao.cc>,
Tom Rini <trini@konsulko.com>
Cc: E Shattow <e@freeshell.de>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: [PATCH v2 1/3] riscv: dts: spacemit: k3: override reserved status of mimsic and maplic
Date: Mon, 2 Nov 2026 11:50:40 -0800 [thread overview]
Message-ID: <20261102195101.103363-2-e@freeshell.de> (raw)
In-Reply-To: <20261102195101.103363-1-e@freeshell.de>
S-Mode Linux boot stalls when probing peripherals unless M-Mode OpenSBI
has the enabled mimsic and maplic nodes. Override these nodes so Linux
can boot.
Reported-by: Yixun Lan <dlan@kernel.org>
Acked-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
Signed-off-by: E Shattow <e@freeshell.de>
---
arch/riscv/dts/spacemit-k3-u-boot.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/riscv/dts/spacemit-k3-u-boot.dtsi b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
index 352e85e7de87..278b36acc79f 100644
--- a/arch/riscv/dts/spacemit-k3-u-boot.dtsi
+++ b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
@@ -3,4 +3,8 @@
* Copyright (C) 2026 Yixun Lan <dlan@kernel.org>
*/
+/* Override reserved status of mimsic and maplic for OpenSBI */
+&mimsic { status = "okay"; };
+&maplic { status = "okay"; };
+
#include "spacemit-k3-binman.dtsi"
--
2.53.0
next prev parent reply other threads:[~2026-11-02 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 19:50 [PATCH v2 0/3] Spacemit K3 enable Linux boot E Shattow
2026-11-02 19:50 ` E Shattow [this message]
2026-11-02 19:50 ` [PATCH v2 2/3] riscv: dts: spacemit: k3: Drop guest properties from M-level IMSIC E Shattow
2026-11-02 19:50 ` [PATCH v2 3/3] configs: spacemit: k3: enable CONFIG_BOOTSTD_FULL E Shattow
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=20261102195101.103363-2-e@freeshell.de \
--to=e@freeshell.de \
--cc=dlan@kernel.org \
--cc=leo.liang@sifive.com \
--cc=me@ziyao.cc \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--cc=troy.mitchell@linux.spacemit.com \
--cc=u-boot@lists.u-boot-project.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