From: Ulf Hansson <ulf.hansson@stericsson.com>
To: Yong Ding <yongd@marvell.com>
Cc: "cjb@laptop.org" <cjb@laptop.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"stefan.xk.nilsson@stericsson.com"
<stefan.xk.nilsson@stericsson.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"svenkatr@ti.com" <svenkatr@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc:sdio:retry CMD52/53 when error happens
Date: Tue, 15 May 2012 09:15:42 +0200 [thread overview]
Message-ID: <4FB2029E.3060107@stericsson.com> (raw)
In-Reply-To: <89813612683626448B837EE5A0B6A7CB1A2B9F19B7@SC-VEXCH4.marvell.com>
Hi Yong Ding,
On 05/15/2012 05:14 AM, Yong Ding wrote:
> Hi Ulf Hansson, Thanks for your comments.
>
> Such retry mechanism is a simple CMD-level or sdio-core-level retry
> which takes advantage of the mmc core internal retry. There is not
> any side effect, but with it, even those SDIO function driver's
> without its own retrying mechanism can benefit in some conditions.
I am not sure about that. It all depends on what kind of protocol the
SDIO func driver is handling and as well what SDIO hw that is connected.
For a WLAN interface you might end up in reading/writing the next
buffer, maybe messing up even more data. Have you considered this?
>
> Besides, for CMD52, it can be used during SDIO card
> initialization/detection phase. At that time, SDIO function driver
> hasn't started to work. Of course we can probably encounter CMD52
> error due to some reasons(eg, board-level schematic bad behavior),
> and such retry can be a potential workaround. Actually, we've
> encountered exactly such case in our development.
I realize that there is a need for this, but I am not sure we always
would like to have "retries" for every CMD52/53 request.
During SDIO initialization before SDIO func driver is started, retries
should be safe since there is no upper protocol to consider yet. Maybe
we should try to create a patch which only enables retries during SDIO
init sequence instead!?
Kind regards
Ulf Hansson
prev parent reply other threads:[~2012-05-15 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 8:39 [PATCH] mmc:sdio:retry CMD52/53 when error happens yongd
2012-05-14 11:57 ` S, Venkatraman
2012-05-14 12:57 ` Ulf Hansson
2012-05-15 3:14 ` Yong Ding
2012-05-15 7:15 ` Ulf Hansson [this message]
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=4FB2029E.3060107@stericsson.com \
--to=ulf.hansson@stericsson.com \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stefan.xk.nilsson@stericsson.com \
--cc=svenkatr@ti.com \
--cc=yongd@marvell.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