From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: vexpress: Enable regulator framework when MMCI is in use
Date: Mon, 18 Mar 2013 18:00:55 +0000 [thread overview]
Message-ID: <1363629655-28917-1-git-send-email-pawel.moll@arm.com> (raw)
In-Reply-To: <20130315181614.GY4977@n2100.arm.linux.org.uk>
The MMCI driver, when used with a Device Tree described device, relies
on the "vmmc" voltage regulator supply to set the OCR register voltage bits,
using MMC core's mmc_regulator_get_supply() function.
Without the regulator framework present there are no valid operating
voltages reported and the device initialisation fails:
mmci-pl18x 1c050000.mmci: mmc0: PL180 manf 41 rev0 at 0x1c050000 irq 41,42 (pio)
mmc0: host doesn't support card's voltages
mmc0: error -22 whilst initialising MMC card
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
---
arch/arm/mach-vexpress/Kconfig | 1 +
1 file changed, 1 insertion(+)
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
--
1.7.10.4
next prev parent reply other threads:[~2013-03-18 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 16:38 [PATCH 0/2] Versatile Express fixes Pawel Moll
2013-03-15 16:38 ` [PATCH 1/2] ARM: vexpress: Enable regulator framework when MMCI is in use Pawel Moll
2013-03-15 18:16 ` Russell King - ARM Linux
2013-03-18 18:00 ` Pawel Moll [this message]
2013-03-18 18:03 ` [PATCH v2 " Russell King - ARM Linux
2013-03-18 18:16 ` Pawel Moll
2013-03-18 18:54 ` Russell King - ARM Linux
2013-03-18 21:40 ` Arnd Bergmann
2013-03-19 7:46 ` Ulf Hansson
2013-03-15 16:39 ` [PATCH 2/2] ARM: vexpress: Remove A9 compatible value for V2P-CA5s PMU node Pawel Moll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363629655-28917-1-git-send-email-pawel.moll@arm.com \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).