From: Tony Lindgren <tony@atomide.com>
To: Madhusudhan <madhu.cr@ti.com>
Cc: 'Nishanth Menon' <nm@ti.com>,
"'Ghorai, Sukumar'" <s-ghorai@ti.com>,
linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3
Date: Wed, 28 Apr 2010 12:23:22 -0700 [thread overview]
Message-ID: <20100428192322.GG7225@atomide.com> (raw)
In-Reply-To: <20100427182111.GE7225@atomide.com>
* 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.
Regards,
Tony
next prev parent reply other threads:[~2010-04-28 19:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 0:25 [PATCH] Disable the non working eMMC on Zoom2/3 Madhusudhan Chikkature
2010-04-01 4:03 ` Ghorai, Sukumar
2010-04-01 17:04 ` Madhusudhan
2010-04-01 18:34 ` Ghorai, Sukumar
2010-04-01 21:59 ` Nishanth Menon
2010-04-01 22:58 ` Madhusudhan
2010-04-07 11:49 ` Tony Lindgren
2010-04-08 17:11 ` Madhusudhan
2010-04-27 18:21 ` Tony Lindgren
2010-04-28 19:23 ` Tony Lindgren [this message]
2010-04-28 19:34 ` Madhusudhan
2010-04-28 19:45 ` Tony Lindgren
2010-04-30 16:57 ` Madhusudhan
2010-05-05 18:27 ` Tony Lindgren
2010-05-06 1:35 ` Madhusudhan
2010-05-06 15:30 ` Tony Lindgren
2010-05-07 21:25 ` Madhusudhan
2010-06-22 11:20 ` zhangfei gao
2010-06-22 11:43 ` Ghorai, Sukumar
2010-06-24 10:55 ` zhangfei gao
2010-06-24 12:04 ` Ghorai, Sukumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100428192322.GG7225@atomide.com \
--to=tony@atomide.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=nm@ti.com \
--cc=s-ghorai@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.