All of lore.kernel.org
 help / color / mirror / Atom feed
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, 7 Apr 2010 04:49:39 -0700	[thread overview]
Message-ID: <20100407114938.GF7153@atomide.com> (raw)
In-Reply-To: <009a01cad1ee$e3bbae70$544ff780@am.dhcp.ti.com>

* Madhusudhan <madhu.cr@ti.com> [100401 15:54]:

<snip>

> > 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?

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.
 
> 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.

There's arm kernel parameter for ATAG_REVISION that can be passed from
bootloader and then the board-*.c code can initialize things accordingly
based on the board revision.

Regards,

Tony


> > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2
> 

  reply	other threads:[~2010-04-07 11:49 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 [this message]
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=20100407114938.GF7153@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.