From: Ludovic Barre <ludovic.Barre@st.com>
To: Ulf Hansson <ulf.hansson@linaro.org>, Rob Herring <robh+dt@kernel.org>
Cc: srinivas.kandagatla@linaro.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mmc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Ludovic Barre <ludovic.barre@st.com>
Subject: [PATCH 0/2] mmc: add unstuck function if host is in deadlock state
Date: Fri, 11 Oct 2019 15:15:00 +0200 [thread overview]
Message-ID: <20191011131502.29579-1-ludovic.Barre@st.com> (raw)
From: Ludovic Barre <ludovic.barre@st.com>
As discussed in this thread: https://patchwork.kernel.org/patch/10786421/
After a request, the host could be in deadlock state, and waiting
for a specific action to unstuck the hardware block before
resending a new command. This series adds mmc_hw_unstuck
callback (structure mmc_host_ops) before resending a new command
(call in mmc_blk_mq_rw_recovery, mmc_wait_for_req_done).
Ludovic Barre (2):
mmc: add unstuck function if host is in deadlock state
mmc: mmci: add unstuck feature
drivers/mmc/core/block.c | 11 +++++++++++
drivers/mmc/core/core.c | 35 +++++++++++++++++++++++++++++++++--
drivers/mmc/host/mmci.c | 23 +++++++++++++++++++++--
include/linux/mmc/core.h | 1 +
include/linux/mmc/host.h | 7 +++++++
5 files changed, 73 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-11 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 13:15 Ludovic Barre [this message]
2019-10-11 13:15 ` [PATCH 1/2] mmc: add unstuck function if host is in deadlock state Ludovic Barre
2019-10-21 13:35 ` Ulf Hansson
2019-11-13 16:54 ` Ludovic BARRE
2019-11-14 14:49 ` Ulf Hansson
2019-10-11 13:15 ` [PATCH 2/2] mmc: mmci: add unstuck feature Ludovic Barre
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=20191011131502.29579-1-ludovic.Barre@st.com \
--to=ludovic.barre@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).