From: Tony Lindgren <tony@atomide.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: MMC broken on beagleboard with current git
Date: Fri, 26 Sep 2008 14:13:52 +0300 [thread overview]
Message-ID: <20080926111351.GA8736@atomide.com> (raw)
In-Reply-To: <20080926074208.GC7962@atomide.com>
* Tony Lindgren <tony@atomide.com> [080926 10:40]:
> * Steve Sakoman <sakoman@gmail.com> [080925 18:24]:
> > On Thu, Sep 25, 2008 at 3:39 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > > Hmm, I don't understand how it could work on 3430sdp...
> > >
> > > Looks like board-omap3beagle.c calls hsmmc_init() just like
> > > board-3430sdp.c. Maybe timings have changed and you need
> > > a longer delay somewhere during the init?
> >
> > I can confirm that mmc is also broken on Overo. I'll spend some time
> > today investigating.
>
> I'll double check on omap3430sdp.
Hmm, MMC does not seem to work any longer on 3430sdp either. I guess I
have broken it, sorry.
I've also confirmed that undoing c434c15d28c82d92e55897bd265c423e9ab69362
makes it work again.
I swear it was working when I last tested it.. I'll try to debug it
further, but I may not get to it for real until on Monday.
I still suspect some timing change caused by the init changes..
Tony
next prev parent reply other threads:[~2008-09-26 11:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 8:41 MMC broken on beagleboard with current git Koen Kooi
2008-09-25 8:51 ` Tony Lindgren
2008-09-25 9:23 ` Koen Kooi
2008-09-25 9:47 ` Tony Lindgren
2008-09-25 10:24 ` Koen Kooi
2008-09-25 10:39 ` Tony Lindgren
2008-09-25 15:24 ` Steve Sakoman
2008-09-26 7:42 ` Tony Lindgren
2008-09-26 11:13 ` Tony Lindgren [this message]
2008-09-28 12:46 ` Tony Lindgren
2008-09-30 12:58 ` Tony Lindgren
2008-09-30 13:22 ` Felipe Balbi
2008-09-30 13:35 ` Tony Lindgren
2008-09-30 13:43 ` Felipe Balbi
2008-09-30 13:24 ` Felipe Contreras
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=20080926111351.GA8736@atomide.com \
--to=tony@atomide.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.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