public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Johan Jonker <jbx6244@gmail.com>
To: Kever Yang <kever.yang@rock-chips.com>,
	Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	xypron.glpk@gmx.de, U-Boot-Denx <u-boot@lists.denx.de>,
	Yifeng Zhao <yifeng.zhao@rock-chips.com>,
	jon.lin@rock-chips.com,
	"open list:ARM/Rockchip SoC support"
	<linux-rockchip@lists.infradead.org>,
	miquel.raynal@bootlin.com, michael@amarulasolutions.com,
	dario.binacchi@amarulasolutions.com
Subject: [PATCH v1 2/6] rockchip: spl: allow more boot devices
Date: Tue, 5 Jul 2022 15:04:28 +0200	[thread overview]
Message-ID: <a24d2b05-0102-2b79-aae2-d6ce851789e4@gmail.com> (raw)
In-Reply-To: <20220701094304.1846-1-jbx6244@yandex.com>

From: Johan Jonker <jbx6244@gmail.com>

Rockchip SoCs have more boot device options then currently
included in the function spl_boot_device().
Make this function generic for SPI and NAND.

Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---

This patch should replace a patch in the serie called:
[PATCH v1 02/17] rockchip: spl: allow more boot devices
https://lore.kernel.org/u-boot/20220508150825.21711-3-jbx6244@gmail.com/

Changed:
  replace #elseif by #elif
---
 arch/arm/mach-rockchip/spl.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-rockchip/spl.c b/arch/arm/mach-rockchip/spl.c
index ceef9d91..aab3804f 100644
--- a/arch/arm/mach-rockchip/spl.c
+++ b/arch/arm/mach-rockchip/spl.c
@@ -53,13 +53,16 @@ u32 spl_boot_device(void)
 {
 	u32 boot_device = BOOT_DEVICE_MMC1;
 
-#if defined(CONFIG_TARGET_CHROMEBOOK_JERRY) || \
+#if defined(CONFIG_SPI_BOOT) || \
+		defined(CONFIG_TARGET_CHROMEBOOK_JERRY) || \
 		defined(CONFIG_TARGET_CHROMEBIT_MICKEY) || \
 		defined(CONFIG_TARGET_CHROMEBOOK_MINNIE) || \
 		defined(CONFIG_TARGET_CHROMEBOOK_SPEEDY) || \
 		defined(CONFIG_TARGET_CHROMEBOOK_BOB) || \
 		defined(CONFIG_TARGET_CHROMEBOOK_KEVIN)
 	return BOOT_DEVICE_SPI;
+#elif defined(CONFIG_NAND_BOOT)
+	return BOOT_DEVICE_NAND;
 #endif
 	if (CONFIG_IS_ENABLED(ROCKCHIP_BACK_TO_BROM))
 		return BOOT_DEVICE_BOOTROM;
-- 
2.20.1


  parent reply	other threads:[~2022-07-05 13:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220701094304.1846-1-jbx6244@yandex.com>
2022-07-05 13:04 ` [PATCH v1 1/6] rockchip: block: add Rockchip IDB block device Johan Jonker
2022-07-05 14:17   ` Xavier Drudis Ferran
2022-07-06 21:09     ` Johan Jonker
2022-07-05 13:04 ` Johan Jonker [this message]
2022-07-05 13:04 ` [PATCH v1 3/6] rockchip: rk3066: add Rockchip IDB block device as boot action Johan Jonker
2022-07-05 13:04 ` [PATCH v1 4/6] arm: dts: rockchip: sync rk3066/rk3188 DT files from Linux Johan Jonker
2022-07-05 13:05 ` [PATCH v1 5/6] arm: dts: rockchip: enable nfc node in spl for rk3066 mk808 Johan Jonker
2022-07-05 13:05 ` [PATCH v1 6/6] rockchip: configs: mk808: add idb configs Johan Jonker

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=a24d2b05-0102-2b79-aae2-d6ce851789e4@gmail.com \
    --to=jbx6244@gmail.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=jon.lin@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=michael@amarulasolutions.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=yifeng.zhao@rock-chips.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