aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap1/board-h2-mmc.c
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2012-04-18 05:43:18 -0400
committerRussell King <rmk+kernel@arm.linux.org.uk>2012-07-31 07:06:23 -0400
commit8a23fa1b95b2e3878c16dcc4e18976bc46dd970b (patch)
treed784f31a7633726edb93a79865995419aecb2456 /arch/arm/mach-omap1/board-h2-mmc.c
parent4e078fbd581a92fa26ba2def4ac8f2a633cdcb5b (diff)
ARM: omap: remove mmc platform data dma_mask and initialization
DMAengine uses the DMA engine device structure when mapping/unmapping memory for DMA, so the MMC devices do not need their DMA masks initialized (this reflects hardware: the MMC device is not the device doing DMA.) Tested-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/mach-omap1/board-h2-mmc.c')
-rw-r--r--arch/arm/mach-omap1/board-h2-mmc.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/mach-omap1/board-h2-mmc.c b/arch/arm/mach-omap1/board-h2-mmc.c
index da0e37d40823..e1362ce48497 100644
--- a/arch/arm/mach-omap1/board-h2-mmc.c
+++ b/arch/arm/mach-omap1/board-h2-mmc.c
@@ -54,7 +54,6 @@ static struct omap_mmc_platform_data mmc1_data = {
54 .nr_slots = 1, 54 .nr_slots = 1,
55 .init = mmc_late_init, 55 .init = mmc_late_init,
56 .cleanup = mmc_cleanup, 56 .cleanup = mmc_cleanup,
57 .dma_mask = 0xffffffff,
58 .slots[0] = { 57 .slots[0] = {
59 .set_power = mmc_set_power, 58 .set_power = mmc_set_power,
60 .ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34, 59 .ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34,