summaryrefslogtreecommitdiff
path: root/configs/bcm968380gerg_ram_defconfig
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2022-08-12 04:34:48 +0300
committerTom Rini <trini@konsulko.com>2022-09-16 18:05:16 +0300
commit7f8967c2b82f9917987b69fbf43f8f591f3a8516 (patch)
tree952913642a31420f44746abc3f734e4fea04d1c5 /configs/bcm968380gerg_ram_defconfig
parent14d2c5d819bb9f011b518c5394af90c3d8e0d17f (diff)
downloadu-boot-7f8967c2b82f9917987b69fbf43f8f591f3a8516.tar.xz
blk: Rename HAVE_BLOCK_DEVICE
This option is fact really related to SPL. For U-Boot proper we always use driver model for block devices, so CONFIG_BLK is enabled if block devices are in use. It is only for SPL that we have two cases: - SPL_BLK is enabled, in which case we use driver model and blk-uclass.c - SPL_BLK is not enabled, in which case (if we need block devices) we must use blk_legacy.c Rename the symbol to SPL_LEGACY_BLOCK to make this clear. This is different enough from BLK and SPL_BLK that there should be no confusion. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'configs/bcm968380gerg_ram_defconfig')
-rw-r--r--configs/bcm968380gerg_ram_defconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/configs/bcm968380gerg_ram_defconfig b/configs/bcm968380gerg_ram_defconfig
index a0924689e4..55d74266b7 100644
--- a/configs/bcm968380gerg_ram_defconfig
+++ b/configs/bcm968380gerg_ram_defconfig
@@ -42,7 +42,7 @@ CONFIG_CMD_NAND=y
CONFIG_SYS_RELOC_GD_ENV_ADDR=y
# CONFIG_NET is not set
# CONFIG_DM_DEVICE_REMOVE is not set
-CONFIG_HAVE_BLOCK_DEVICE=y
+CONFIG_SPL_LEGACY_BLOCK=y
CONFIG_BCM6345_GPIO=y
CONFIG_LED=y
CONFIG_LED_BCM6328=y