From: "Madhusudhan" <madhu.cr@ti.com>
To: 'Tony Lindgren' <tony@atomide.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, 5 May 2010 20:35:51 -0500 [thread overview]
Message-ID: <00a501caecbc$761ded40$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <20100505182727.GA29604@atomide.com>
> -----Original Message-----
> From: Tony Lindgren [mailto:tony@atomide.com]
> Sent: Wednesday, May 05, 2010 1:27 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
>
> * Madhusudhan <madhu.cr@ti.com> [100430 09:52]:
> > <snip>
> >
> > > > >
> > > > > > 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
> >
> > This means that some production boards still have this issue with eMMC.
> So
> > my patch disables the support for MMC2 on zoom boards. Would you
> consider
> > that?
>
> But is it also broken on zoom2?
>
Yes.
> And what about this "Simulate multi mmc card as one big" patch?
>
Did not get you, what patch are you referring to?
Regards,
Madhu
> Regards,
>
> Tony
next prev parent reply other threads:[~2010-05-06 1:35 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
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 [this message]
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='00a501caecbc$761ded40$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 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.