| Message ID | 1363365540-23001-2-git-send-email-pawel.moll@arm.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Fri, Mar 15, 2013 at 04:38:59PM +0000, Pawel Moll wrote: > As the MMCI driver obtains some of the platform data from > a regulator (described by the device tree), the framework must > be present - otherwise device's initialisation will fail. More description is required here. How does it fail. Please describe the problem fully. MMCI should work without regulator support.
diff --git a/arch/arm/mach-vexpress/Kconfig b/arch/arm/mach-vexpress/Kconfig index 52d315b..46ab88d 100644 --- a/arch/arm/mach-vexpress/Kconfig +++ b/arch/arm/mach-vexpress/Kconfig @@ -17,6 +17,7 @@ config ARCH_VEXPRESS select NO_IOPORT select PLAT_VERSATILE select PLAT_VERSATILE_CLCD + select REGULATOR if MMC_ARMMMCI select REGULATOR_FIXED_VOLTAGE if REGULATOR select VEXPRESS_CONFIG help
As the MMCI driver obtains some of the platform data from a regulator (described by the device tree), the framework must be present - otherwise device's initialisation will fail. Signed-off-by: Pawel Moll <pawel.moll@arm.com> --- arch/arm/mach-vexpress/Kconfig | 1 + 1 file changed, 1 insertion(+)