From: Ohad Ben-Cohen <ohad@wizery.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: zhangfei gao <zhangfei.gao@gmail.com>,
Daniel Drake <dsd@laptop.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Mike Rapoport <mike@compulab.co.il>,
Zhangfei Gao <zgao6@marvell.com>
Subject: Re: MMC runtime PM patches break libertas probe
Date: Wed, 8 Jun 2011 17:34:01 +0300 [thread overview]
Message-ID: <BANLkTimZ+Emm6GrTztEaGnjRu92Pam13mQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=qR7bbsnzsCpV=b2C4Ha5Hdb94gQ@mail.gmail.com>
Hi Bing,
On Sat, Jun 4, 2011 at 1:52 AM, Ohad Ben-Cohen <ohad@wizery.com> wrote:
> On Sat, Jun 4, 2011 at 1:28 AM, Bing Zhao <bzhao@marvell.com> wrote:
>> "CMD5 Arg=0" refers to the very first CMD5 sent from host during initialization sequence.
>> This is required because our state machine always expects two CMD5 from host (5, 5, 3, 7, ...).
>
> Great, thanks for confirming this !
I have another question please.
Does the sd8686 require an SDIO I/O reset (CMD52 setting bit 3 of
address 0x6 of the CCCR) to it after powering it on ?
Daniel (cc'ed) is trying to power it off and back on, and it does seem
to work in the first time, without sending a reset. In the second
time, though, the card doesn't answer CMD5 anymore, unless Daniel is
sending it an SDIO I/O reset. I was wondering whether this is an
sd8686 requirement, or whether we have some other issue at hand.
Thanks,
Ohad.
next prev parent reply other threads:[~2011-06-08 14:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 14:29 MMC runtime PM patches break libertas probe Daniel Drake
2010-10-31 14:42 ` Ohad Ben-Cohen
2010-10-31 14:55 ` Daniel Drake
2010-10-31 15:08 ` Ohad Ben-Cohen
2010-10-31 15:10 ` Daniel Drake
2010-10-31 15:16 ` Ohad Ben-Cohen
2010-10-31 15:21 ` Daniel Drake
2010-10-31 15:21 ` Daniel Drake
2010-10-31 15:27 ` Ohad Ben-Cohen
2010-10-31 15:57 ` Daniel Drake
2010-10-31 16:16 ` Ohad Ben-Cohen
2010-10-31 16:24 ` Daniel Drake
2010-10-31 19:06 ` Ohad Ben-Cohen
2010-11-01 8:27 ` Ohad Ben-Cohen
2010-11-06 21:19 ` Daniel Drake
2010-11-07 1:48 ` Nicolas Pitre
2010-11-07 10:19 ` Daniel Drake
2010-11-07 15:12 ` Nicolas Pitre
2010-11-07 10:42 ` Ohad Ben-Cohen
2010-11-07 10:51 ` Daniel Drake
2010-11-07 13:17 ` Ohad Ben-Cohen
2010-11-16 13:22 ` Ohad Ben-Cohen
2010-11-16 14:29 ` Daniel Drake
2010-11-16 14:49 ` Ohad Ben-Cohen
2010-11-17 6:46 ` Mike Rapoport
2010-11-17 7:29 ` Ohad Ben-Cohen
2010-11-17 14:54 ` Nicolas Pitre
2010-11-16 17:17 ` Arnd Hannemann
2010-11-16 20:58 ` Ohad Ben-Cohen
2010-11-16 21:16 ` Arnd Hannemann
2010-11-16 22:26 ` Ohad Ben-Cohen
2011-05-29 16:21 ` Daniel Drake
2011-05-30 6:52 ` Ohad Ben-Cohen
2011-05-30 7:01 ` Daniel Drake
2011-05-30 7:32 ` Ohad Ben-Cohen
2011-05-30 11:04 ` zhangfei gao
2011-05-30 11:16 ` Ohad Ben-Cohen
2011-06-02 8:39 ` Bing Zhao
2011-06-02 18:25 ` Ohad Ben-Cohen
2011-06-03 22:28 ` Bing Zhao
2011-06-03 22:52 ` Ohad Ben-Cohen
2011-06-07 14:34 ` Arnd Hannemann
2011-06-07 14:45 ` Ohad Ben-Cohen
2011-06-08 14:34 ` Ohad Ben-Cohen [this message]
2011-06-10 2:02 ` zhangfei gao
2011-06-10 4:28 ` Ohad Ben-Cohen
2011-06-11 2:33 ` zhangfei gao
2011-06-11 9:03 ` Ohad Ben-Cohen
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=BANLkTimZ+Emm6GrTztEaGnjRu92Pam13mQ@mail.gmail.com \
--to=ohad@wizery.com \
--cc=bzhao@marvell.com \
--cc=dsd@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=zgao6@marvell.com \
--cc=zhangfei.gao@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;
as well as URLs for NNTP newsgroup(s).