summaryrefslogtreecommitdiff
path: root/drivers/mmc/Kconfig
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-06-12 23:30:22 -0600
committerSimon Glass <sjg@chromium.org>2016-07-11 14:06:44 -0600
commit8ca51e51c182699ebc64b10660db3e03cb43cb54 (patch)
tree4078d4757aa016c16beaaecc1bc9dc7836a0bb4e /drivers/mmc/Kconfig
parent7d1c8d99fd12ad1e879533075b87c908462c1fd3 (diff)
downloadu-boot-imx-8ca51e51c182699ebc64b10660db3e03cb43cb54.zip
u-boot-imx-8ca51e51c182699ebc64b10660db3e03cb43cb54.tar.gz
u-boot-imx-8ca51e51c182699ebc64b10660db3e03cb43cb54.tar.bz2
dm: mmc: Add a way to use driver model for MMC operations
The driver model conversion for MMC has moved in small steps. The first step was to have an MMC device (CONFIG_DM_MMC). The second was to use a child block device (CONFIG_BLK). The final one is to use driver model for MMC operations (CONFIG_DM_MMC_OP). Add support for this. The immediate priority is to make all boards that use DM_MMC also use those other two options. This will allow them to be removed. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/mmc/Kconfig')
-rw-r--r--drivers/mmc/Kconfig9
1 files changed, 9 insertions, 0 deletions
diff --git a/drivers/mmc/Kconfig b/drivers/mmc/Kconfig
index c80efc3..b9662f9 100644
--- a/drivers/mmc/Kconfig
+++ b/drivers/mmc/Kconfig
@@ -16,6 +16,15 @@ config DM_MMC
appear as block devices in U-Boot and can support filesystems such
as EXT4 and FAT.
+config DM_MMC_OPS
+ bool "Support MMC controller operations using Driver Model"
+ depends on DM_MMC
+ help
+ Driver model provides a means of supporting device operations. This
+ option moves MMC operations under the control of driver model. The
+ option will be removed as soon as all DM_MMC drivers use it, as it
+ will the only supported behaviour.
+
config MSM_SDHCI
bool "Qualcomm SDHCI controller"
depends on DM_MMC