From: Prathamesh Shete <pshete@nvidia.com>
To: <ulfh@kernel.org>, <adrian.hunter@intel.com>,
<thierry.reding@kernel.org>, <jonathanh@nvidia.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<pshete@nvidia.com>
Subject: [PATCH 0/5] mmc: tegra: Add Tegra238 and Tegra264 SDHCI support
Date: Fri, 24 Jul 2026 07:56:54 +0000 [thread overview]
Message-ID: <20260724075700.714261-1-pshete@nvidia.com> (raw)
Add SDHCI support for the Tegra238 and Tegra264 SoCs.
The series documents the compatible strings and adds the corresponding
SoC data. It also adds the Tegra264 SDMMC1 device tree node.
Prathamesh Shete (5):
dt-bindings: mmc: tegra: Document Tegra238 SDHCI
mmc: sdhci-tegra: Add Tegra238 SoC data
dt-bindings: mmc: tegra: Document Tegra264 SDHCI
mmc: sdhci-tegra: Add Tegra264 SoC data
arm64: tegra: Add Tegra264 SDMMC1 device tree node
.../bindings/mmc/nvidia,tegra20-sdhci.yaml | 6 ++++
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 34 +++++++++++++++++++
drivers/mmc/host/sdhci-tegra.c | 30 ++++++++++++++++
3 files changed, 70 insertions(+)
--
2.17.1
next reply other threads:[~2026-07-24 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 7:56 Prathamesh Shete [this message]
2026-07-24 7:56 ` [PATCH 1/5] dt-bindings: mmc: tegra: Document Tegra238 SDHCI Prathamesh Shete
2026-07-24 7:56 ` [PATCH 2/5] mmc: sdhci-tegra: Add Tegra238 SoC data Prathamesh Shete
2026-07-24 7:56 ` [PATCH 3/5] dt-bindings: mmc: tegra: Document Tegra264 SDHCI Prathamesh Shete
2026-07-24 7:56 ` [PATCH 4/5] mmc: sdhci-tegra: Add Tegra264 SoC data Prathamesh Shete
2026-07-24 7:56 ` [PATCH 5/5] arm64: tegra: Add Tegra264 SDMMC1 device tree node Prathamesh Shete
2026-07-24 8:15 ` sashiko-bot
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=20260724075700.714261-1-pshete@nvidia.com \
--to=pshete@nvidia.com \
--cc=adrian.hunter@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=ulfh@kernel.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