U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
	"E Shattow" <e@freeshell.de>,
	"Anirudh Srinivasan" <asrinivasan@oss.tenstorrent.com>
Cc: <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>,
	"Guodong Xu" <guodong.xu@oss.qualcomm.com>
Subject: Re: [PATCH v1 1/3] riscv: dts: spacemit: k3: override reserved status of mimsic and maplic
Date: Thu, 29 Oct 2026 14:39:31 +0800	[thread overview]
Message-ID: <DMH46SAKH62G.3B9ZKSF91RX33@linux.spacemit.com> (raw)
In-Reply-To: <DMH42XA23X2U.VK02RL7ED7O2@linux.spacemit.com>

[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]

On Thu Oct 29, 2026 at 2:34 PM +08, Troy Mitchell wrote:
> On Thu Oct 29, 2026 at 6:35 AM +08, E Shattow wrote:
>> Hi Anirudh, CC: Troy Mitchell, Guodong Xu
I realized after sending that you CC'd the wrong Guodong email.
I've corrected it here.

>>
>> On 10/28/26 15:01, Anirudh Srinivasan wrote:
>>> On Wed, Oct 28, 2026 at 11:45:05AM -0700, E Shattow wrote:
>>>> Linux boot stalls when probing peripherals unless OpenSBI has the
>>>> enabled mimsic and maplic nodes. Override these nodes so Linux can boot.
>>>>
>>>> Reported-by: Yixun Lan <dlan@kernel.org>
>>>> 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"; };
>>> 
>>> This should be fixed in the DT in linux. I guess you could carry this
>>> patch till it is fixed in linux.
> I think status = "reserved" in k3.dtsi is correct and should stay.
> The DT spec defines "reserved" as a device that is operational
> but should not be used, typically because it is controlled by
> another software component such as platform firmware.
>
> That is exactly the case for the M-level IMSIC and APLIC.
>>> 
>>>> +
>>>>  #include "spacemit-k3-binman.dtsi"
>>>> -- 
>>>> 2.53.0
>>>>
>>
>> The upstream commit that adds these nodes as reserved status is:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=56f37e391a626
>>
>> Quote, "...Also add M-mode APLIC (maplic) and IMSIC (mimsic) nodes to
>> represent the hardware topology and ready for potential firmware usage."
>>
>> When the mainline OpenSBI series lands adding SpacemiT K3 support:
>>
>> https://lore.kernel.org/opensbi/20261028-spacemit-k3-v6-0-01d984f60941@linux.spacemit.com/
>>
>> ...then I think we could send this upstream?
> Acked-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
>
>>
>> Thanks for the review, -E


-- 
Troy Mitchell


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

  reply	other threads:[~2026-10-29 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 18:45 [PATCH v1 0/3] Spacemit K3 enable Linux boot E Shattow
2026-10-28 18:45 ` [PATCH v1 1/3] riscv: dts: spacemit: k3: override reserved status of mimsic and maplic E Shattow
2026-10-28 22:01   ` Anirudh Srinivasan
2026-10-28 22:35     ` E Shattow
2026-10-29  6:34       ` Troy Mitchell
2026-10-29  6:39         ` Troy Mitchell [this message]
2026-10-29 14:22         ` Anirudh Srinivasan
2026-10-29 16:34           ` E Shattow
2026-10-28 18:45 ` [PATCH v1 2/3] riscv: dts: spacemit: k3: adopt override to drop M-level IMSIC guest props E Shattow
2026-10-28 18:45 ` [PATCH v1 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=DMH46SAKH62G.3B9ZKSF91RX33@linux.spacemit.com \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=dlan@kernel.org \
    --cc=e@freeshell.de \
    --cc=guodong.xu@oss.qualcomm.com \
    --cc=leo.liang@sifive.com \
    --cc=me@ziyao.cc \
    --cc=tim609@andestech.com \
    --cc=trini@konsulko.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