From: Aapo Vienamo <avienamo@nvidia.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Mikko Perttunen <mperttunen@nvidia.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Aapo Vienamo <avienamo@nvidia.com>
Subject: [PATCH 0/7] Tegra SDHCI enable 1.8 V signaling on Tegar210 and Tegra186
Date: Fri, 20 Jul 2018 15:45:39 +0300 [thread overview]
Message-ID: <1532090746-15863-1-git-send-email-avienamo@nvidia.com> (raw)
Reconfigure pad voltages as part of mmc voltage switching on
controllers with adjustable voltages. Allow for reconfiguration of the
signaling voltage of SDMMC1 on Tegra210 P2597 and fix SDMMC4 signaling
voltage regulator configuration on Tegra210 P2180.
This series depends on the "Tegra PMC pinctrl pad configuration" series posted
earlier.
Aapo Vienamo (7):
dt-bindings: Document Tegra SDHCI pinctrl bindings
mmc: tegra: Reconfigure pad voltages during voltage switching
arm64: dts: Add Tegra210 sdmmc pinctrl voltage states
arm64: dts: Add Tegra186 sdmmc pinctrl voltage states
arm64: dts: tegra210-p2180: Allow ldo2 to go down to 1.8 V
arm64: dts: tegra210-p2180: Correct sdmmc4 vqmmc-supply
arm64: dts: tegra210-p2597: Remove no-1-8-v from sdmmc1
.../bindings/mmc/nvidia,tegra20-sdhci.txt | 22 ++++++
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 40 ++++++++++
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 12 +--
arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 1 -
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 27 +++++++
drivers/mmc/host/sdhci-tegra.c | 91 ++++++++++++++++++++--
6 files changed, 176 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2018-07-20 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 12:45 Aapo Vienamo [this message]
2018-07-20 12:45 ` [PATCH 1/7] dt-bindings: Document Tegra SDHCI pinctrl bindings Aapo Vienamo
2018-07-25 6:47 ` Mikko Perttunen
2018-07-20 12:45 ` [PATCH 2/7] mmc: tegra: Reconfigure pad voltages during voltage switching Aapo Vienamo
2018-07-25 6:41 ` Mikko Perttunen
2018-07-25 8:35 ` Aapo Vienamo
2018-07-20 12:45 ` [PATCH 3/7] arm64: dts: Add Tegra210 sdmmc pinctrl voltage states Aapo Vienamo
2018-07-21 0:14 ` kbuild test robot
2018-07-25 6:49 ` Mikko Perttunen
2018-07-20 12:45 ` [PATCH 4/7] arm64: dts: Add Tegra186 " Aapo Vienamo
2018-07-21 1:29 ` kbuild test robot
2018-07-25 6:50 ` Mikko Perttunen
2018-07-20 12:45 ` [PATCH 5/7] arm64: dts: tegra210-p2180: Allow ldo2 to go down to 1.8 V Aapo Vienamo
2018-07-25 6:50 ` Mikko Perttunen
2018-07-20 12:45 ` [PATCH 6/7] arm64: dts: tegra210-p2180: Correct sdmmc4 vqmmc-supply Aapo Vienamo
2018-07-25 6:53 ` Mikko Perttunen
2018-07-20 12:45 ` [PATCH 7/7] arm64: dts: tegra210-p2597: Remove no-1-8-v from sdmmc1 Aapo Vienamo
2018-07-25 6:58 ` Mikko Perttunen
2018-07-25 8:12 ` Aapo Vienamo
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=1532090746-15863-1-git-send-email-avienamo@nvidia.com \
--to=avienamo@nvidia.com \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@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).