From: "Madhusudhan" <madhu.cr@ti.com>
To: 'Nishanth Menon' <nm@ti.com>, "'Ghorai, Sukumar'" <s-ghorai@ti.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
Date: Thu, 1 Apr 2010 17:58:48 -0500 [thread overview]
Message-ID: <009a01cad1ee$e3bbae70$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <4BB51740.2060802@ti.com>
> -----Original Message-----
> From: Nishanth Menon [mailto:nm@ti.com]
> Sent: Thursday, April 01, 2010 4:59 PM
> To: Ghorai, Sukumar
> Cc: Chikkature Rajashekar, Madhusudhan; tony@atomide.com; linux-
> omap@vger.kernel.org; linux-mmc@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@vger.kernel.org [mailto:linux-omap-
> >>>> owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar,
> Madhusudhan
> >>>> Sent: 2010-04-01 05:56
> >>>> To: tony@atomide.com
> >>>> Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org
> >>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> >>>>
> >>>> From: Madhusudhan Chikkature <madhu.cr@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.
> >
> > [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.
> >
> Ref [1] I believe tony has the brand new zoom board - I think your
> assumption here might be flawed..
>
Wait, I just looked up the serial number on the board. The one I was using
is a pilot version where this problem exists.
I happen to get an other board which is production unit with ser # 1013089
Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2
which is correct and works fine.
http://omappedia.org/wiki/Zoom_Resources
There is a table here which could help.
Tony, do you care to just look up the serial number of your board?
But again there are several boards out there which could have this
non-working eMMC. So what do we do?? It does not make sense to keep
something enabled which does not work.
Regards,
Madhu
> --
> Regards,
> Nishanth Menon
> Ref:
> [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2
next prev parent reply other threads:[~2010-04-01 22:58 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 [this message]
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
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='009a01cad1ee$e3bbae70$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-ghorai@ti.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).