public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andes <uboot@andestech.com>
To: <u-boot@lists.denx.de>
Cc: <bmeng.cn@gmail.com>, <lukas.auer@aisec.fraunhofer.de>,
	<anup@brainfault.org>, <atishp@atishpatra.org>,
	<xypron.glpk@gmx.de>, <nikita.shubin@maquefel.me>,
	<seanga2@gmail.com>, <ycliang@andestech.com>,
	<rick@andestech.com>, <rickchen36@gmail.com>
Subject: [PATCH 2/2] riscv: ae350: Disable AVAILABLE_HARTS
Date: Wed, 21 Sep 2022 14:34:55 +0800	[thread overview]
Message-ID: <20220921063455.7814-2-uboot@andestech.com> (raw)
In-Reply-To: <20220921063455.7814-1-uboot@andestech.com>

From: Rick Chen <rick@andestech.com>

Disable AVAILABLE_HARTS mechanism to make sure that all harts
can boot to Kernel shell successfully.

Signed-off-by: Rick Chen <rick@andestech.com>
---
 configs/ae350_rv32_spl_defconfig | 1 +
 configs/ae350_rv64_spl_defconfig | 1 +
 2 files changed, 2 insertions(+)

diff --git a/configs/ae350_rv32_spl_defconfig b/configs/ae350_rv32_spl_defconfig
index 9b79cc41b5..1cc98a2653 100644
--- a/configs/ae350_rv32_spl_defconfig
+++ b/configs/ae350_rv32_spl_defconfig
@@ -48,3 +48,4 @@ CONFIG_SYS_NS16550=y
 CONFIG_SPI=y
 CONFIG_ATCSPI200_SPI=y
 # CONFIG_BINMAN_FDT is not set
+# CONFIG_AVAILABLE_HARTS is not set
diff --git a/configs/ae350_rv64_spl_defconfig b/configs/ae350_rv64_spl_defconfig
index 4c33ca2383..4318300300 100644
--- a/configs/ae350_rv64_spl_defconfig
+++ b/configs/ae350_rv64_spl_defconfig
@@ -49,3 +49,4 @@ CONFIG_SYS_NS16550=y
 CONFIG_SPI=y
 CONFIG_ATCSPI200_SPI=y
 # CONFIG_BINMAN_FDT is not set
+# CONFIG_AVAILABLE_HARTS is not set
-- 
2.17.1


  reply	other threads:[~2022-09-21  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  6:34 [PATCH 1/2] riscv: Introduce AVAILABLE_HARTS Andes
2022-09-21  6:34 ` Andes [this message]
2022-09-22  3:33   ` [PATCH 2/2] riscv: ae350: Disable AVAILABLE_HARTS Leo Liang
2022-09-22  3:32 ` [PATCH 1/2] riscv: Introduce AVAILABLE_HARTS Leo Liang

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=20220921063455.7814-2-uboot@andestech.com \
    --to=uboot@andestech.com \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=bmeng.cn@gmail.com \
    --cc=lukas.auer@aisec.fraunhofer.de \
    --cc=nikita.shubin@maquefel.me \
    --cc=rick@andestech.com \
    --cc=rickchen36@gmail.com \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=ycliang@andestech.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