From: Aapo Vienamo <avienamo@nvidia.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: <linux-mmc@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Aapo Vienamo <avienamo@nvidia.com>
Subject: [PATCH 0/2] Tegra SDHCI rerun pad calibration periodically
Date: Mon, 20 Aug 2018 12:23:31 +0300 [thread overview]
Message-ID: <1534757013-4524-1-git-send-email-avienamo@nvidia.com> (raw)
Hi all,
This series implements pad drive strength recalibration. The calibration
is rerun to compensate possible changes in temperature. The calibration
procedure is rerun as part of mmc_host_ops.request before
sdhci_request() is run. The calibration is executed only if the 100 ms
recalibration interval has passed.
This series depends on the "Tegra SDHCI add support for HS200 and UHS
signaling" series.
Aapo Vienamo (2):
mmc: sdhci: Export sdhci_request()
mmc: tegra: Implement periodic pad calibration
drivers/mmc/host/sdhci-tegra.c | 22 ++++++++++++++++++++++
drivers/mmc/host/sdhci.c | 3 ++-
drivers/mmc/host/sdhci.h | 1 +
3 files changed, 25 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2018-08-20 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 9:23 Aapo Vienamo [this message]
2018-08-20 9:23 ` [PATCH 1/2] mmc: sdhci: Export sdhci_request() Aapo Vienamo
2018-08-22 10:54 ` Adrian Hunter
2018-08-27 10:07 ` Ulf Hansson
2018-08-27 10:11 ` Thierry Reding
2018-08-20 9:23 ` [PATCH 2/2] mmc: tegra: Implement periodic pad calibration Aapo Vienamo
2018-08-22 10:56 ` Adrian Hunter
2018-08-31 14:00 ` Thierry Reding
2018-09-03 6:14 ` Ulf Hansson
2018-08-23 8:50 ` [PATCH 0/2] Tegra SDHCI rerun pad calibration periodically Thierry Reding
2018-08-27 9:55 ` 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=1534757013-4524-1-git-send-email-avienamo@nvidia.com \
--to=avienamo@nvidia.com \
--cc=adrian.hunter@intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).