diff mbox series

configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR

Message ID 20240321092557.2939231-1-tejas.arvind.bhumkar@amd.com
State Superseded
Delegated to: Michal Simek
Headers show
Series configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR | expand

Commit Message

Bhumkar, Tejas Arvind March 21, 2024, 9:25 a.m. UTC
Disable CONFIG_SPI_FLASH_BAR, which activates 4-byte opcodes.

Signed-off-by: Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>
---
 configs/xilinx_zynqmp_kria_defconfig | 1 -
 1 file changed, 1 deletion(-)

Comments

Michal Simek March 21, 2024, 9:35 a.m. UTC | #1
On 3/21/24 10:25, Tejas Bhumkar wrote:
> Disable CONFIG_SPI_FLASH_BAR, which activates 4-byte opcodes.

Can you please be more specific?
There is a bigger story behind which should be also described.

The issue which this patch is addressing is that when image recovery application 
is running U-Boot SPL or FSBL with upstream u-boot is not able to work with the 
flash unless board is power off/on again.
It suggest that baremetal application is using flash in certain mode and U-Boot 
is another. That's why I want to know that this change actually does.
If that means that it uses the same mode as baremetal application or so.

M
diff mbox series

Patch

diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig
index 7cb8b62d32..7af8b27be9 100644
--- a/configs/xilinx_zynqmp_kria_defconfig
+++ b/configs/xilinx_zynqmp_kria_defconfig
@@ -155,7 +155,6 @@  CONFIG_MMC_HS200_SUPPORT=y
 CONFIG_MMC_SDHCI=y
 CONFIG_MMC_SDHCI_ZYNQ=y
 CONFIG_DM_MTD=y
-CONFIG_SPI_FLASH_BAR=y
 CONFIG_SPI_FLASH_STMICRO=y
 # CONFIG_SPI_FLASH_USE_4K_SECTORS is not set
 CONFIG_SPI_FLASH_MTD=y