Madhusudhan, > -----Original Message----- > From: Chikkature Rajashekar, Madhusudhan > Sent: 2010-04-01 22:35 > To: Ghorai, Sukumar; tony@xxxxxxxxxxx > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-mmc@xxxxxxxxxxxxxxx > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > > -----Original Message----- > > From: Ghorai, Sukumar [mailto:s-ghorai@xxxxxx] > > Sent: Wednesday, March 31, 2010 11:03 PM > > To: Chikkature Rajashekar, Madhusudhan; tony@xxxxxxxxxxx > > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-mmc@xxxxxxxxxxxxxxx > > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > Madhu, > > > > > -----Original Message----- > > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > > owner@xxxxxxxxxxxxxxx] On Behalf Of Chikkature Rajashekar, Madhusudhan > > > Sent: 2010-04-01 05:56 > > > To: tony@xxxxxxxxxxx > > > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-mmc@xxxxxxxxxxxxxxx > > > Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > > > From: Madhusudhan Chikkature <madhu.cr@xxxxxx> > > > Date: Wed, 31 Mar 2010 12:29:19 -0400 > > > Subject: [PATCH] Zoom2/3: Disable MMC > > > > > > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > > > writes to fail since the card size is not detected correctly by the > MMC > > > core. Disable the MMC2 support for Zoom2/3. > > > > > > [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the > exact > > problem. Because we never face any issue for eMMC in ZOOM3. Because we > > have the same eMMC device in 3630-SDP and could have the same problem. > > > > On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached. > > Hence the failures which are reported by people on the list. I had already > bought this problem up on the list previously and was discussed, right? > From the log you can also see that a 16GB device is detected as a 1GB. [Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is working fine. And I feel outside TI people having production board only. And 16GB eMMC device is a very good size to work with different things. Otherwise we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all these information in different page/ link looks very misleading information, if really having such problem. I the mean time I will check this in Pilot board too and think you checked in pilot board only. > > Regards, > Madhu > > > > > > > Signed-off-by: Madhusudhan Chikkature <madhu.cr@xxxxxx> > > > --- > > > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 ----------------- > -- > > -- > > > ----- > > > 1 files changed, 0 insertions(+), 30 deletions(-) > > > > > > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c > > > b/arch/arm/mach-omap2/board-zoom-peripherals.c > > > index 6b39849..ac791d2 100644 > > > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c > > > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c > > > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply > > > zoom_vsim_supply = { > > > .supply = "vmmc_aux", > > > }; > > > > > > -static struct regulator_consumer_supply zoom_vmmc2_supply = { > > > - .supply = "vmmc", > > > -}; > > > - > > > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */ > > > static struct regulator_init_data zoom_vmmc1 = { > > > .constraints = { > > > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = { > > > .consumer_supplies = &zoom_vmmc1_supply, > > > }; > > > > > > -/* VMMC2 for MMC2 card */ > > > -static struct regulator_init_data zoom_vmmc2 = { > > > - .constraints = { > > > - .min_uV = 1850000, > > > - .max_uV = 1850000, > > > - .apply_uV = true, > > > - .valid_modes_mask = REGULATOR_MODE_NORMAL > > > - | REGULATOR_MODE_STANDBY, > > > - .valid_ops_mask = REGULATOR_CHANGE_MODE > > > - | REGULATOR_CHANGE_STATUS, > > > - }, > > > - .num_consumer_supplies = 1, > > > - .consumer_supplies = &zoom_vmmc2_supply, > > > -}; > > > - > > > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */ > > > static struct regulator_init_data zoom_vsim = { > > > .constraints = { > > > @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = > { > > > .gpio_wp = -EINVAL, > > > .power_saving = true, > > > }, > > > - { > > > - .name = "internal", > > > - .mmc = 2, > > > - .wires = 8, > > > - .gpio_cd = -EINVAL, > > > - .gpio_wp = -EINVAL, > > > - .nonremovable = true, > > > - .power_saving = true, > > > - }, > > > {} /* Terminator */ > > > }; > > > > > > @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev, > > > */ > > > zoom_vmmc1_supply.dev = mmc[0].dev; > > > zoom_vsim_supply.dev = mmc[0].dev; > > > - zoom_vmmc2_supply.dev = mmc[1].dev; > > > > > > return 0; > > > } > > > @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = > { > > > .keypad = &zoom_kp_twl4030_data, > > > .codec = &zoom_codec_data, > > > .vmmc1 = &zoom_vmmc1, > > > - .vmmc2 = &zoom_vmmc2, > > > .vsim = &zoom_vsim, > > > > > > }; > > > -- > > > 1.6.3.3 > > > > > > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-omap" > in > > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
