From: "Tamás Szűcs" <tszucs@protonmail.ch>
To: Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
JC Kuo <jckuo@nvidia.com>, Sameer Pujar <spujar@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Tamás Szűcs" <tszucs@protonmail.ch>
Subject: [PATCH v2 0/4] arm64: tegra: Xavier SDMMC changes
Date: Thu, 23 Jul 2020 23:09:28 +0200 [thread overview]
Message-ID: <20200723210932.8076-1-tszucs@protonmail.ch> (raw)
It turns out uSD card detection on the Jetson AGX Xavier is not working and
I/Os are limited to 3.3 V. SDIO is supported but not enabled. Also, the
on-board eMMC module is using HS200 only.
Changes in v2:
- fix board name in commit messages
- rebase on for-next
Kind regards,
Tamas
Tamás Szűcs (4):
arm64: tegra: Enable signal voltage switching on Tegra194 SDMMC1 and
SDMMC3
arm64: tegra: Fix CD on Jetson AGX Xavier SDMMC1
arm64: tegra: Configure SDIO cards on Jetson AGX Xavier SDMMC1
arm64: tegra: Enable HS400 on Tegra194 SDMMC4
.../arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 4 +-
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 46 +++++++++++++++++++
2 files changed, 49 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2020-07-23 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 21:09 Tamás Szűcs [this message]
2020-07-23 21:09 ` [PATCH v2 1/4] arm64: tegra: Enable signal voltage switching on Tegra194 SDMMC1 and SDMMC3 Tamás Szűcs
2020-07-23 21:09 ` [PATCH v2 2/4] arm64: tegra: Fix CD on Jetson AGX Xavier SDMMC1 Tamás Szűcs
2020-07-23 21:09 ` [PATCH v2 3/4] arm64: tegra: Configure SDIO cards " Tamás Szűcs
2020-07-23 21:09 ` [PATCH v2 4/4] arm64: tegra: Enable HS400 on Tegra194 SDMMC4 Tamás Szűcs
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=20200723210932.8076-1-tszucs@protonmail.ch \
--to=tszucs@protonmail.ch \
--cc=devicetree@vger.kernel.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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).