Madhusudhan Chikkature | 1 Apr 2010 02:25
Picon
Favicon

[PATCH] Disable the non working eMMC on Zoom2/3

From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
Date: Wed, 31 Mar 2010 12:29:19 -0400
Subject: [PATCH] Zoom2/3: Disable MMC2

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.

Signed-off-by: Madhusudhan Chikkature <madhu.cr <at> ti.com>
---
 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
 <at>  <at>  -102,10 +102,6  <at>  <at>  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 = {
 <at>  <at>  -121,21 +117,6  <at>  <at>  static struct regulator_init_data zoom_vmmc1 = {
(Continue reading)

Madhusudhan Chikkature | 1 Apr 2010 02:29
Picon
Favicon

[PATCH]OMAP HSMMC: Fix a bug in card remove scenario

From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
Date: Wed, 31 Mar 2010 19:31:24 -0400
Subject: [PATCH] OMAP HSMMC:Fix a bug in card removal scenario

The reset of data lines when the card is removed from the cage results
in a failure.The failure is seen if the card is removed from the cage
when TC is pending after a CMD with data received CC.The reset logic leaves
the controller in a state where niether a TC is received nor DTO.

The rest code can be safely removed here since it is taken care in the IRQ
handler.

Signed-off-by: Madhusudhan Chikkature <madhu.cr <at> ti.com>
---
 drivers/mmc/host/omap_hsmmc.c |    9 ++-------
 1 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index 83f0aff..e9caf69 100644
--- a/drivers/mmc/host/omap_hsmmc.c
+++ b/drivers/mmc/host/omap_hsmmc.c
 <at>  <at>  -1179,15 +1179,10  <at>  <at>  static void omap_hsmmc_detect(struct work_struct *work)
 		carddetect = -ENOSYS;
 	}

-	if (carddetect) {
+	if (carddetect)
 		mmc_detect_change(host->mmc, (HZ * 200) / 1000);
-	} else {
-		mmc_host_enable(host->mmc);
(Continue reading)

Ghorai, Sukumar | 1 Apr 2010 06:03
Picon
Favicon

RE: [PATCH] Disable the non working eMMC on Zoom2/3

Madhu,

> -----Original Message-----
> From: linux-omap-owner <at> vger.kernel.org [mailto:linux-omap-
> owner <at> vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> Sent: 2010-04-01 05:56
> To: tony <at> atomide.com
> Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> 
> From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
> 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.

> 
> Signed-off-by: Madhusudhan Chikkature <madhu.cr <at> ti.com>
> ---
>  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
(Continue reading)

Hans J. Koch | 1 Apr 2010 14:52
Picon

Is anyone working on SD/MMC driver for i.MX35 ?

I need to get the MMC interface of an i.MX35 to work in the near future.
To avoid duplicate work, I'd like to know if anybody already started
work on this.

Any hints?

Thanks,
Hans

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Madhusudhan | 1 Apr 2010 19:04
Picon
Favicon

RE: [PATCH] Disable the non working eMMC on Zoom2/3


> -----Original Message-----
> From: Ghorai, Sukumar [mailto:s-ghorai <at> ti.com]
> Sent: Wednesday, March 31, 2010 11:03 PM
> To: Chikkature Rajashekar, Madhusudhan; tony <at> atomide.com
> Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
> 
> Madhu,
> 
> > -----Original Message-----
> > From: linux-omap-owner <at> vger.kernel.org [mailto:linux-omap-
> > owner <at> vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> > Sent: 2010-04-01 05:56
> > To: tony <at> atomide.com
> > Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> > Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> >
> > From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
> > 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.
(Continue reading)

Ghorai, Sukumar | 1 Apr 2010 20:34
Picon
Favicon

RE: [PATCH] Disable the non working eMMC on Zoom2/3

Madhusudhan,

> -----Original Message-----
> From: Chikkature Rajashekar, Madhusudhan
> Sent: 2010-04-01 22:35
> To: Ghorai, Sukumar; tony <at> atomide.com
> Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
> 
> 
> 
> > -----Original Message-----
> > From: Ghorai, Sukumar [mailto:s-ghorai <at> ti.com]
> > Sent: Wednesday, March 31, 2010 11:03 PM
> > To: Chikkature Rajashekar, Madhusudhan; tony <at> atomide.com
> > Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
> >
> > Madhu,
> >
> > > -----Original Message-----
> > > From: linux-omap-owner <at> vger.kernel.org [mailto:linux-omap-
> > > owner <at> vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> > > Sent: 2010-04-01 05:56
> > > To: tony <at> atomide.com
> > > Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> > > Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> > >
> > > From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
> > > Date: Wed, 31 Mar 2010 12:29:19 -0400
(Continue reading)

Nishanth Menon | 1 Apr 2010 23:59
Picon
Favicon
Gravatar

Re: [PATCH] Disable the non working eMMC on Zoom2/3

Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following:

>>>> -----Original Message-----
>>>> From: linux-omap-owner <at> vger.kernel.org [mailto:linux-omap-
>>>> owner <at> vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
>>>> Sent: 2010-04-01 05:56
>>>> To: tony <at> atomide.com
>>>> Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
>>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3
>>>>
>>>> From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
>>>> 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.
> 
(Continue reading)

Andrew Morton | 2 Apr 2010 00:30

Re: [Bugme-new] [Bug 15656] New: System sluggish when using ENE SD card reader


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 31 Mar 2010 11:09:28 GMT
bugzilla-daemon <at> bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=15656
> 
>            Summary: System sluggish when using ENE SD card reader
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.33 and earlier
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: MMC/SD
>         AssignedTo: drivers_mmc-sd <at> kernel-bugs.osdl.org
>         ReportedBy: theholyettlz <at> googlemail.com
>         Regression: No
> 
> 
> My system becomes incredibly sluggish (jerky X cursor, choppy audio) when
> accessing an SD card with my notebook's built-in ENE card reader. The kernel
> was compiled with full pre-emption enabled.
> 
> >From lspci -nn:
(Continue reading)

Madhusudhan | 2 Apr 2010 00:58
Picon
Favicon

RE: [PATCH] Disable the non working eMMC on Zoom2/3


> -----Original Message-----
> From: Nishanth Menon [mailto:nm <at> ti.com]
> Sent: Thursday, April 01, 2010 4:59 PM
> To: Ghorai, Sukumar
> Cc: Chikkature Rajashekar, Madhusudhan; tony <at> atomide.com; linux-
> omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3
> 
> Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following:
> 
> >>>> -----Original Message-----
> >>>> From: linux-omap-owner <at> vger.kernel.org [mailto:linux-omap-
> >>>> owner <at> vger.kernel.org] On Behalf Of Chikkature Rajashekar,
> Madhusudhan
> >>>> Sent: 2010-04-01 05:56
> >>>> To: tony <at> atomide.com
> >>>> Cc: linux-omap <at> vger.kernel.org; linux-mmc <at> vger.kernel.org
> >>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> >>>>
> >>>> From: Madhusudhan Chikkature <madhu.cr <at> ti.com>
> >>>> 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
(Continue reading)

akpm | 2 Apr 2010 01:27

+ omap-hsmmc-fix-a-bug-in-card-remove-scenario.patch added to -mm tree


The patch titled
     omap hsmmc: fix a bug in card remove scenario
has been added to the -mm tree.  Its filename is
     omap-hsmmc-fix-a-bug-in-card-remove-scenario.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: omap hsmmc: fix a bug in card remove scenario
From: Madhusudhan Chikkature <madhu.cr <at> ti.com>

The reset of data lines when the card is removed from the cage results in
a failure.The failure is seen if the card is removed from the cage when TC
is pending after a CMD with data received CC.The reset logic leaves the
controller in a state where niether a TC is received nor DTO.

The rest code can be safely removed here since it is taken care in the IRQ
handler.
(Continue reading)


Gmane