summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2022-08-11 19:34:48 -0600
committerTom Rini <trini@konsulko.com>2022-09-16 11:05:16 -0400
commit7f8967c2b82f9917987b69fbf43f8f591f3a8516 (patch)
tree952913642a31420f44746abc3f734e4fea04d1c5 /common
parent14d2c5d819bb9f011b518c5394af90c3d8e0d17f (diff)
downloadu-boot-7f8967c2b82f9917987b69fbf43f8f591f3a8516.tar.gz
u-boot-7f8967c2b82f9917987b69fbf43f8f591f3a8516.tar.bz2
u-boot-7f8967c2b82f9917987b69fbf43f8f591f3a8516.zip
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 'common')
-rw-r--r--common/spl/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/common/spl/Kconfig b/common/spl/Kconfig
index 70d97815f0..222472a6fb 100644
--- a/common/spl/Kconfig
+++ b/common/spl/Kconfig
@@ -792,7 +792,7 @@ config SPL_DM_MAILBOX
config SPL_MMC
bool "Support MMC"
depends on MMC
- select HAVE_BLOCK_DEVICE
+ select SPL_LEGACY_BLOCK
help
Enable support for MMC (Multimedia Card) within SPL. This enables
the MMC protocol implementation and allows any enabled drivers to
@@ -1318,7 +1318,7 @@ config SPL_THERMAL
config SPL_USB_HOST
bool "Support USB host drivers"
- select HAVE_BLOCK_DEVICE
+ select SPL_LEGACY_BLOCK
help
Enable access to USB (Universal Serial Bus) host devices so that
SPL can load U-Boot from a connected USB peripheral, such as a USB