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

[Tony Lindgren <tony@atomide.com>]

* Madhusudhan <madhu.cr@ti.com> [100428 12:30]:
> 
> 
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > Sent: Wednesday, April 28, 2010 2:23 PM
> > To: Madhusudhan
> > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org;
> > linux-mmc@vger.kernel.org
> > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3
> > 
> > * Tony Lindgren <tony@atomide.com> [100427 11:16]:
> > > * Madhusudhan <madhu.cr@ti.com> [100408 10:07]:
> > > > > >
> > > > > > Tony, do you care to just look up the serial number of your board?
> > > > >
> > > > > Sorry for the delay in replying, I've been travelling for a few
> > weeks
> > > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A
> > board,
> > > > > which seems to be production in the table above.
> > > > >
> > > >
> > > > That means we can not assume all production units have a working eMMC.
> > > > Would you mind sharing your bootup log? When this device is detected
> > > > something like below is a clear issue.
> > > >
> > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB
> > > > mmcblk1: p1 p2
> > 
> > For the eMMC I seem to have that:
> > 
> > [    0.978363] mmc1: new high speed MMC card at address 0001
> > [    0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB
> > [    0.989105]  mmcblk1: unknown partition table
> > ...
> > 
> > zoom:~# fdisk -l /dev/mmcblk1
> > [  120.306396] mmcblk1: retrying using single block read
> > [  120.503692] mmcblk1: retrying using single block read
> > [  120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr
> > 8, card status 0x900
> > [  120.691894] end_request: I/O error, dev mmcblk1, sector 2097144
> > [  120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr
> > 7, card status 0x900
> > ...
> > 
> > > Hmm, finally got around looking into this again. Looks like the mmc
> > > is now working on my zoom3 with the current Linus' tree at commit
> > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that
> > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc?
> > >
> > > This is with the debug_ll patch applied:
> > >
> > > https://patchwork.kernel.org/patch/87532/
> > 
> > For the microSD card, turns out the card I used was flakey. So
> > that should explain some of the problems. I'm almost certain
> > I tried with two different cards earlier though. In any case,
> > let's assume the problem is only the eMMC.
> > 
> Sorry, I did not get a complete picture. Your earlier email said that with
> Linus tree eMMC on your Zoom3 is working. Is that correct?

Nope, now the microSD is working, eMMC is not working.
 
> IMHO, an omap level fix can not solve the problem with eMMC because as I can
> see from the log you provided above that a 16G device is detected as 1G.
> This is certainly due to the issue I mentioned earlier. 

OK

Tony