From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-mmc@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH 0/3] mmc: avoid vicious circle when retuning
Date: Thu, 24 Jun 2021 17:16:13 +0200 [thread overview]
Message-ID: <20210624151616.38770-1-wsa+renesas@sang-engineering.com> (raw)
See patch 1 for a description of the problem. This series implements the
alternative approach suggested by Adrian (thanks!). It also adds some
documentation and a minor cleanup which I came up with while working on
the fix. Patch 1 can go to stable as is, the rest built on top of that.
This series fixes the performance issue which we saw when injecting CRC
errors on Renesas R-Car Gen3 hardware.
Looking forward to comments!
Wolfram Sang (3):
mmc: core: clear flags before allowing to retune
mmc: host: add kdoc for mmc_retune_{en|dis}able
mmc: host: factor out clearing the retune state
drivers/mmc/core/core.c | 6 ++++--
drivers/mmc/core/host.c | 13 +++++++++++--
drivers/mmc/core/host.h | 6 ++++++
3 files changed, 21 insertions(+), 4 deletions(-)
--
2.30.2
next reply other threads:[~2021-06-24 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 15:16 Wolfram Sang [this message]
2021-06-24 15:16 ` [PATCH 1/3] mmc: core: clear flags before allowing to retune Wolfram Sang
2021-06-24 15:16 ` [PATCH 2/3] mmc: host: add kdoc for mmc_retune_{en|dis}able Wolfram Sang
2021-06-24 15:16 ` [PATCH 3/3] mmc: host: factor out clearing the retune state Wolfram Sang
2021-06-24 16:06 ` [PATCH 0/3] mmc: avoid vicious circle when retuning Adrian Hunter
2021-06-25 9:31 ` Yoshihiro Shimoda
2021-06-29 15:08 ` Ulf Hansson
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=20210624151616.38770-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=adrian.hunter@intel.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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).