From: Alistair Buxton <a.j.buxton@gmail.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Cory Maccarrone <darkstar6262@gmail.com>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3] mmc-omap: Add support for 16-bit and 32-bit registers
Date: Mon, 23 Nov 2009 13:54:22 +0000 [thread overview]
Message-ID: <3d374d00911230554w496921dcvb721ebf0cfff9869@mail.gmail.com> (raw)
In-Reply-To: <20091123132555.GA12983@localhost.localdomain>
2009/11/23 Ladislav Michl <Ladislav.Michl@seznam.cz>:
> And sorry to ask again. This very driver works reliable and there are no
> timeouts like this
> mmci-omap mmci-omap.0: command timeout (CMD8)
> mmci-omap mmci-omap.0: command timeout (CMD5)
> mmci-omap mmci-omap.0: command timeout (CMD5)
> mmci-omap mmci-omap.0: command timeout (CMD5)
> mmci-omap mmci-omap.0: command timeout (CMD5)
> mmci-omap mmci-omap.0: command timeout (CMD55)
> mmci-omap mmci-omap.0: command timeout (CMD55)
> mmci-omap mmci-omap.0: command timeout (CMD55)
> mmci-omap mmci-omap.0: command timeout (CMD55)
> while detecting MMC card on OMAP730? (because I can see them on 5910). This question
> is unrelated to your patch.
>
Yes, this driver (after patching) works reliably on OMAP7XX. The
CMD5/8 timeouts seem normal and non-fatal. CMD55 is the "init" command
that has to work. We had an old problem causing output just like what
you report - it turned out we missed a GPIO to power up the MMC card.
--
Alistair Buxton
a.j.buxton@gmail.com
next prev parent reply other threads:[~2009-11-23 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 21:16 [PATCH v3] mmc-omap: Add support for 16-bit and 32-bit registers Cory Maccarrone
2009-11-23 13:25 ` Ladislav Michl
2009-11-23 13:54 ` Alistair Buxton [this message]
2009-11-23 15:32 ` Cory Maccarrone
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=3d374d00911230554w496921dcvb721ebf0cfff9869@mail.gmail.com \
--to=a.j.buxton@gmail.com \
--cc=darkstar6262@gmail.com \
--cc=ladis@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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