summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorAisheng.Dong <b29396@freescale.com>2011-01-13 10:27:28 +0800
committerAisheng.Dong <b29396@freescale.com>2011-01-13 11:06:58 +0800
commite804faabbb64fd93095ddc0affa3d8a59600d9ea (patch)
tree345277f66e8f60e8e6329b94f42d317ec440b79a /arch
parentfb9b09d08c0157f8e9d470f5ce8b4d50cebc988a (diff)
ENGR00137489 mx50 rdp: specify the regulator in esdhc2 platform data
By defining the regulator name in the esdhc platform data, the esdhc driver will dynamically check and set a proper voltage for the card. This can fix the issue that SD32 can not work well on mx50 rdp board because the default voltage of VSD seems can not meet its requirement. This is only a workaround. The root cause may be related to HW, board degsin or WiFi card. Signed-off-by: Aisheng.Dong <b29396@freescale.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/mach-mx5/mx50_rdp.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/mach-mx5/mx50_rdp.c b/arch/arm/mach-mx5/mx50_rdp.c
index f6ca52ce7453..c7029e8a1e8d 100644
--- a/arch/arm/mach-mx5/mx50_rdp.c
+++ b/arch/arm/mach-mx5/mx50_rdp.c
@@ -1036,6 +1036,7 @@ static struct mxc_mmc_platform_data mmc2_data = {
.status = sdhc_get_card_det_status,
.wp_status = sdhc_write_protect,
.clock_mmc = "esdhc_clk",
+ .power_mmc = "VSD"
};
static struct mxc_mmc_platform_data mmc3_data = {