From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: pshete@nvidia.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, p.zabel@pengutronix.de,
linux-mmc@vger.kernel.org, anrao@nvidia.com,
smangipudi@nvidia.com, kyarlagadda@nvidia.com
Subject: [PATCH 0/4] mmc: sdhci: Tidy reset handling
Date: Mon, 26 Sep 2022 22:20:18 +0300 [thread overview]
Message-ID: <20220926192022.85660-1-adrian.hunter@intel.com> (raw)
Hi
When reviewing the patch "mmc: sdhci-tegra: Issue CMD and DAT resets
together" currently on the mailing list:
https://lore.kernel.org/linux-mmc/20220926094906.14537-3-pshete@nvidia.com/
it seemed like some small tidy up was needed first. Hence these patches.
In particular, patch 4 "mmc: sdhci: Centralize CMD and DATA reset handling"
should enable the proposed quirk from the sdhci-tegra patch to be
implemented in a more consistent way.
Adrian Hunter (4):
mmc: sdhci: Separate out sdhci_reset_for_all()
mmc: sdhci: Remove misleading comment about resets
mmc: sdhci: Get rid of SDHCI_QUIRK_RESET_CMD_DATA_ON_IOS
mmc: sdhci: Centralize CMD and DATA reset handling
drivers/mmc/host/sdhci-pci-core.c | 23 ++++++++++-
drivers/mmc/host/sdhci.c | 84 ++++++++++++++++++++++++---------------
drivers/mmc/host/sdhci.h | 2 -
3 files changed, 73 insertions(+), 36 deletions(-)
Regards
Adrian
next reply other threads:[~2022-09-26 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 19:20 Adrian Hunter [this message]
2022-09-26 19:20 ` [PATCH 1/4] mmc: sdhci: Separate out sdhci_reset_for_all() Adrian Hunter
2022-09-26 19:20 ` [PATCH 2/4] mmc: sdhci: Remove misleading comment about resets Adrian Hunter
2022-09-26 19:20 ` [PATCH 3/4] mmc: sdhci: Get rid of SDHCI_QUIRK_RESET_CMD_DATA_ON_IOS Adrian Hunter
2022-09-27 15:22 ` Thierry Reding
2022-09-28 8:11 ` Ulf Hansson
2022-09-26 19:20 ` [PATCH 4/4] mmc: sdhci: Centralize CMD and DATA reset handling Adrian Hunter
2022-09-27 12:13 ` [PATCH 0/4] mmc: sdhci: Tidy " 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=20220926192022.85660-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=anrao@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pshete@nvidia.com \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--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