summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap1/board-h2-mmc.c
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2010-10-12 16:07:51 -0700
committerTony Lindgren <tony@atomide.com>2010-10-12 16:07:51 -0700
commit2a12400eed8be0d5790108cba3908a71d6bb9cae (patch)
tree01a5743ff70c41df24bbc608161cee3a8624f640 /arch/arm/mach-omap1/board-h2-mmc.c
parent4de43a6b4cf002e343cf39fa27a3f46c5dc19411 (diff)
omap: Fix spotty MMC voltages
As noted by Michał Mirosław <mirqus@gmail.com>, the voltages should cover the supported voltage range, or support only one voltage. As all these boards are using a GPIO to enable the power, chances are that only 3.3V cards are supported on these boards. Reported-by: Michał Mirosław <mirqus@gmail.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap1/board-h2-mmc.c')
-rw-r--r--arch/arm/mach-omap1/board-h2-mmc.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/arm/mach-omap1/board-h2-mmc.c b/arch/arm/mach-omap1/board-h2-mmc.c
index b30c4990744..f2fc43d8382 100644
--- a/arch/arm/mach-omap1/board-h2-mmc.c
+++ b/arch/arm/mach-omap1/board-h2-mmc.c
@@ -58,8 +58,7 @@ static struct omap_mmc_platform_data mmc1_data = {
.dma_mask = 0xffffffff,
.slots[0] = {
.set_power = mmc_set_power,
- .ocr_mask = MMC_VDD_28_29 | MMC_VDD_30_31 |
- MMC_VDD_32_33 | MMC_VDD_33_34,
+ .ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34,
.name = "mmcblk",
},
};