diff options
| author | Jack Rosenthal <jrosenth@chromium.org> | 2021-04-30 13:03:26 -0600 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2021-05-01 01:41:08 +0000 |
| commit | bf9979b91599ffc76018d60e780d19fa8d266ac0 (patch) | |
| tree | 56ca6031236d2af6b38944c373806a708e6adb7b /zephyr/Kconfig.flash | |
| parent | 3b156ad3993b99eb9ec056a1d4e60d04525faa77 (diff) | |
| download | chrome-ec-bf9979b91599ffc76018d60e780d19fa8d266ac0.tar.gz | |
zephyr: drop programmatic generation of binman device-tree input
Move the binman device-tree input into the Zephyr build system's DTS,
which allows overriding parts of the binman settings on a
board/project specific basis using device-tree.
In the process, we need to move the flash offset and size to
device-tree instead of Kconfig, because Kconfig is not including
during device-tree preprocessing. This is overall, a net-good change,
as this should never been Kconfig in the first place. This assumes
the existing Kconfig defaults of 512 KB of flash with 256 KB sections,
however can still be overridden via device-tree.
BUG=b:184388037
BRANCH=none
TEST=zmake testall
manually investigate the flash output for lazor using dump_fmap
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I424ea15454d5cd02947642116673bebcad3406cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2860987
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'zephyr/Kconfig.flash')
| -rw-r--r-- | zephyr/Kconfig.flash | 30 |
1 files changed, 0 insertions, 30 deletions
diff --git a/zephyr/Kconfig.flash b/zephyr/Kconfig.flash index e79732d928..89f8c10341 100644 --- a/zephyr/Kconfig.flash +++ b/zephyr/Kconfig.flash @@ -14,36 +14,6 @@ config PLATFORM_EC_SPI_FLASH_REGS registers, and (2) the inverse function to set the status registers based on the desired protection offset/length. -config PLATFORM_EC_PROTECTED_STORAGE_OFF - hex "Position of the RO image in Flash memory" - default 0x0 - help - Sets the position in flash memory where the RO image begins. This is - the address that will be used to start copying the image into RAM. - -config PLATFORM_EC_PROTECTED_STORAGE_SIZE - hex "Size of the RO image in Flash memory" - default 0x40000 - help - The total size of the RO image in flash memory. This will dictate the - ending position of the RO image being copied into RAM when combined - with PLATFORM_EC_PROTECTED_STORAGE_OFF. - -config PLATFORM_EC_WRITABLE_STORAGE_OFF - hex "Position of the RW image in Flash memory" - default 0x40000 - help - Sets the position in flash memory where the RW image begins. This is - the address that will be used to start copying the image into RAM. - -config PLATFORM_EC_WRITABLE_STORAGE_SIZE - hex "Size of the RW image in Flash memory" - default 0x40000 - help - The total size of the RW image in flash memory. This will dictate the - ending position of the RW image being copied into RAM when combined - with PLATFORM_EC_WRITABLE_STORAGE_OFF. - config PLATFORM_EC_CONSOLE_CMD_CHARGEN bool "Console command: chargen" depends on UART_INTERRUPT_DRIVEN |