From: <jiajie.hao@mediatek.com>
To: <ulf.hansson@linaro.org>
Cc: <linus.walleij@linaro.org>, <chaotian.jing@mediatek.com>,
<yong.mao@mediatek.com>, <eddie.huang@mediatek.com>,
<srv_heupstream@mediatek.com>, <linux-mmc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@mediatek.com>
Subject: [PATCH] mmc: sdio: Fix sdio wait busy implement limitation
Date: Mon, 17 Apr 2017 16:09:30 +0800 [thread overview]
Message-ID: <1492416571-28843-1-git-send-email-jiajie.hao@mediatek.com> (raw)
The host may issue an I/O abort by writing to the CCCR at any time
during I/O read operation via CMD52. And host may need suspend
transcation during write busy stage in SDIO suspend/resume scenario.
>From other side, a card may accept CMD52 during data transfer phase.
Previous implement would block issuing above command in busy stage.
It cause function driver can't implement as proper way and has no
opportunity to do some coverage in error case via I/O abort etc.
We need bypass some necessary operation during busy check stage.
WARNING: multiple messages have this Message-ID (diff)
From: <jiajie.hao@mediatek.com>
To: ulf.hansson@linaro.org
Cc: linus.walleij@linaro.org, chaotian.jing@mediatek.com,
yong.mao@mediatek.com, eddie.huang@mediatek.com,
srv_heupstream@mediatek.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@mediatek.com
Subject: [PATCH] mmc: sdio: Fix sdio wait busy implement limitation
Date: Mon, 17 Apr 2017 16:09:30 +0800 [thread overview]
Message-ID: <1492416571-28843-1-git-send-email-jiajie.hao@mediatek.com> (raw)
The host may issue an I/O abort by writing to the CCCR at any time
during I/O read operation via CMD52. And host may need suspend
transcation during write busy stage in SDIO suspend/resume scenario.
>From other side, a card may accept CMD52 during data transfer phase.
Previous implement would block issuing above command in busy stage.
It cause function driver can't implement as proper way and has no
opportunity to do some coverage in error case via I/O abort etc.
We need bypass some necessary operation during busy check stage.
next reply other threads:[~2017-04-17 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 8:09 jiajie.hao [this message]
2017-04-17 8:09 ` [PATCH] mmc: sdio: Fix sdio wait busy implement limitation jiajie.hao
2017-04-17 8:09 ` jiajie.hao
2017-04-17 8:09 ` jiajie.hao
2017-04-17 8:36 ` 答复: " Jiajie Hao (郝加节)
2017-04-17 8:36 ` Jiajie Hao (郝加节)
2017-04-20 13:27 ` Ulf Hansson
2017-04-23 6:42 ` Jiajie Hao
2017-04-23 6:42 ` Jiajie Hao
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=1492416571-28843-1-git-send-email-jiajie.hao@mediatek.com \
--to=jiajie.hao@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=ulf.hansson@linaro.org \
--cc=yong.mao@mediatek.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.