From: dgilmore at redhat.com <dgilmore@redhat.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] ARM: mvebu: helios4 adjust env sizes to enable SPI to work
Date: Sun, 6 Dec 2020 19:36:00 -0600 [thread overview]
Message-ID: <20201207013603.330578-1-dgilmore@redhat.com> (raw)
From: Dennis Gilmore <dennis@ausil.us>
mirror the clearfog setup to enable SPI to work
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
---
arch/arm/mach-mvebu/Kconfig | 1 +
board/kobol/helios4/Kconfig | 24 ++++++++++++++++++++++++
configs/helios4_defconfig | 2 --
3 files changed, 25 insertions(+), 2 deletions(-)
create mode 100644 board/kobol/helios4/Kconfig
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 0d8e0922a2..66fd771dff 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -293,5 +293,6 @@ config SECURED_MODE_CSK_INDEX
depends on SECURED_MODE_IMAGE
source "board/solidrun/clearfog/Kconfig"
+source "board/kobol/helios4/Kconfig"
endif
diff --git a/board/kobol/helios4/Kconfig b/board/kobol/helios4/Kconfig
new file mode 100644
index 0000000000..cad51c1cf0
--- /dev/null
+++ b/board/kobol/helios4/Kconfig
@@ -0,0 +1,24 @@
+menu "Helios4 configuration"
+ depends on TARGET_HELIOS4
+
+config ENV_SIZE
+ hex "Environment Size"
+ default 0x10000
+
+config ENV_OFFSET
+ hex "Environment offset"
+ default 0xF0000
+
+config ENV_SECT_SIZE
+ hex "Environment Sector-Size"
+ # Use SPI or SATA flash erase block size of 4 KiB
+ default 0x1000 if MVEBU_SPL_BOOT_DEVICE_SPI || MVEBU_SPL_BOOT_DEVICE_SATA
+ # Use optimistic 64 KiB erase block, will vary between actual media
+ default 0x10000 if MVEBU_SPL_BOOT_DEVICE_MMC || MVEBU_SPL_BOOT_DEVICE_UART
+
+config SYS_SPI_U_BOOT_OFFS
+ hex "address of u-boot payload in SPI flash"
+ default 0x20000
+ depends on MVEBU_SPL_BOOT_DEVICE_SPI
+
+endmenu
diff --git a/configs/helios4_defconfig b/configs/helios4_defconfig
index eceb85f082..bdc6f43554 100644
--- a/configs/helios4_defconfig
+++ b/configs/helios4_defconfig
@@ -9,8 +9,6 @@ CONFIG_SYS_MALLOC_F_LEN=0x2000
CONFIG_NR_DRAM_BANKS=2
CONFIG_TARGET_HELIOS4=y
CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC=y
-CONFIG_ENV_SIZE=0x2000
-CONFIG_ENV_OFFSET=0xFE000
CONFIG_DM_GPIO=y
CONFIG_SPL_TEXT_BASE=0x40000030
CONFIG_SPL_SERIAL_SUPPORT=y
--
2.28.0
next reply other threads:[~2020-12-07 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 1:36 dgilmore at redhat.com [this message]
2020-12-07 1:36 ` [PATCH 2/4] ARM: mvebu: helios4 dts changes to enable SPI dgilmore at redhat.com
2020-12-07 5:36 ` Baruch Siach
2020-12-07 1:36 ` [PATCH 3/4] ARM: mvebu: ClearFog make sure that SATA and UART images are buildable dgilmore at redhat.com
2020-12-07 1:36 ` [PATCH 4/4] ARM: mvebu: fixup building a SPI image for db-mv784mp-gp dgilmore at redhat.com
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=20201207013603.330578-1-dgilmore@redhat.com \
--to=dgilmore@redhat.com \
--cc=u-boot@lists.denx.de \
/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