From: Greg Malysa <malysagreg@gmail.com>
To: u-boot@lists.denx.de
Cc: adsp-linux@analog.com, Greg Malysa <malysagreg@gmail.com>,
Philip Molloy <Philip.Molloy@analog.com>,
Arturs Artamonovs <arturs.artamonovs@analog.com>,
Ian Roberts <ian.roberts@timesys.com>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Philip Molloy <philip.molloy@analog.com>,
Tom Rini <trini@konsulko.com>,
Utsav Agarwal <utsav.agarwal@analog.com>,
Vasileios Bimpikas <vasileios.bimpikas@analog.com>
Subject: [PATCH 02/12] mach-sc5xx: Rename SC_BOOT_MODE
Date: Thu, 11 Dec 2025 03:03:53 -0500 [thread overview]
Message-ID: <20251211080414.5363-3-malysagreg@gmail.com> (raw)
In-Reply-To: <20251211080414.5363-1-malysagreg@gmail.com>
The symbol SC_BOOT_MODE was named incorrectly and inconsistently with
its usage. The selected boot mode is set only by hardware and cannot be
adjusted through software (apart from the use of FORCE_BMODE to instruct
the boot rom to ignore the hardware setting when loading uboot proper,
but this cannot change how SPL is loaded).
This symbol actually controlled the BCODE (easily confused with BMODE,
shorthand for boot mode), so this renames it to SC_BCODE and updates the
help text to reflect its actual usage: the BCODE is an SoC- and boot
mode-specific setting that affects how the boot rom configures QSPI or
OSPI in order to read an LDR file from the associated peripheral.
Reported-by: Philip Molloy <Philip.Molloy@analog.com>
Signed-off-by: Greg Malysa <malysagreg@gmail.com>
---
(no changes since v2)
Changes in v2:
- New
arch/arm/mach-sc5xx/Kconfig | 14 ++++++++------
arch/arm/mach-sc5xx/config.mk | 2 +-
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-sc5xx/Kconfig b/arch/arm/mach-sc5xx/Kconfig
index 70c7e5e0631..170177f4e10 100644
--- a/arch/arm/mach-sc5xx/Kconfig
+++ b/arch/arm/mach-sc5xx/Kconfig
@@ -153,14 +153,16 @@ config ADI_IMAGE
The image built by the ADI ADSP Linux build system.
Is one of tiny, minimal, full.
-config SC_BOOT_MODE
- int "SC5XX boot mode select"
+config SC_BCODE
+ int "SC5XX SPI BCODE select"
default 1
- range 0 7
+ range 0 15
help
- Mode 0: do nothing, just idle
- Mode 1: boot ldr out of serial flash
- Mode 7: boot ldr over uart
+ This sets the BCODE option for the generated LDR file. The BCODE
+ is only used in SPI boots (QSPI/OSPI) but is set with no impact
+ in other boot modes so that one LDR file may be reused from any
+ boot media. The interpretation of this value is SoC and boot mode
+ specific, so you must refer to the HRM to interpret it.
config SC_BOOT_SPI_BUS
int "sc5xx spi boot bus"
diff --git a/arch/arm/mach-sc5xx/config.mk b/arch/arm/mach-sc5xx/config.mk
index 266d2e3a777..b4eb1c42810 100644
--- a/arch/arm/mach-sc5xx/config.mk
+++ b/arch/arm/mach-sc5xx/config.mk
@@ -14,5 +14,5 @@ endif
INPUTS-y += u-boot.ldr
-LDR_FLAGS += --bcode=$(CONFIG_SC_BOOT_MODE)
+LDR_FLAGS += --bcode=$(CONFIG_SC_BCODE)
LDR_FLAGS += --use-vmas
--
2.49.1
next prev parent reply other threads:[~2025-12-11 8:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 8:03 [PATCH 00/12] sc5xx: Add complete board support for all ADI SC5xx boards Greg Malysa
2025-12-11 8:03 ` [PATCH 01/12] mach-sc5xx: Introduce Kconfig symbols for image addresses Greg Malysa
2025-12-11 8:03 ` Greg Malysa [this message]
2025-12-11 8:03 ` [PATCH 03/12] mach-sc5xx: Kconfig: Make EZKIT and EZLITE carriers mutually exclusive Greg Malysa
2025-12-11 8:03 ` [PATCH 04/12] mach-sc5xx: Add preliminary support for binman Greg Malysa
2025-12-11 8:03 ` [PATCH 05/12] docker: add Analog Devices tools to docker image Greg Malysa
2025-12-11 8:03 ` [PATCH 06/12] board: adi: Add SOMCRR infrastructure Greg Malysa
2025-12-11 8:03 ` [PATCH 07/12] board: adi: Add support for SC573-ezkit Greg Malysa
2025-12-11 8:03 ` [PATCH 08/12] board: adi: Add support for SC589 boards Greg Malysa
2025-12-11 8:04 ` [PATCH 09/12] board: adi: Add support for SC584-ezkit Greg Malysa
2025-12-11 8:04 ` [PATCH 10/12] board: adi: Add support for SC598 Greg Malysa
2025-12-11 8:04 ` [PATCH 11/12] board: adi: Add support for SC594 Greg Malysa
2025-12-11 8:04 ` [PATCH 12/12] MAINTAINERS: Update ADI entries for new boards Greg Malysa
2026-01-23 22:33 ` [PATCH 00/12] sc5xx: Add complete board support for all ADI SC5xx boards Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2025-11-18 6:39 Greg Malysa
2025-11-18 6:39 ` [PATCH 02/12] mach-sc5xx: Rename SC_BOOT_MODE Greg Malysa
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=20251211080414.5363-3-malysagreg@gmail.com \
--to=malysagreg@gmail.com \
--cc=Philip.Molloy@analog.com \
--cc=adsp-linux@analog.com \
--cc=arturs.artamonovs@analog.com \
--cc=ian.roberts@timesys.com \
--cc=nathan.morrison@timesys.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=utsav.agarwal@analog.com \
--cc=vasileios.bimpikas@analog.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