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 5/5] arm64: tegra: Add Tegra264 SDMMC1 device tree node
Date: Fri, 24 Jul 2026 07:56:59 +0000 [thread overview]
Message-ID: <20260724075700.714261-6-pshete@nvidia.com> (raw)
In-Reply-To: <20260724075700.714261-1-pshete@nvidia.com>
Add device tree node for the Tegra264 SDMMC1 instance.
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
---
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 34 ++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
index 2d2cb1a3d95c..f1eafb6a3970 100644
--- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
@@ -3631,6 +3631,40 @@
status = "disabled";
};
+ mmc@c570000 {
+ compatible = "nvidia,tegra264-sdhci", "nvidia,tegra194-sdhci";
+ reg = <0x00 0x0c570000 0x0 0x10000>;
+ interrupts = <GIC_SPI 162 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&bpmp TEGRA264_CLK_SDMMC1>,
+ <&bpmp TEGRA264_CLK_SDMMC_LEGACY_TM>;
+ clock-names = "sdhci", "tmclk";
+ assigned-clocks = <&bpmp TEGRA264_CLK_SDMMC1>,
+ <&bpmp TEGRA264_CLK_PLLC4_MUXED>;
+ assigned-clock-parents = <&bpmp TEGRA264_CLK_PLLC4_MUXED>,
+ <&bpmp TEGRA264_CLK_PLLC4_OUT0>;
+ resets = <&bpmp TEGRA264_RESET_SDMMC1>;
+ reset-names = "sdhci";
+ interconnects = <&mc TEGRA264_MEMORY_CLIENT_SDMMC0R &emc>,
+ <&mc TEGRA264_MEMORY_CLIENT_SDMMC0W &emc>;
+ interconnect-names = "dma-mem", "write";
+ iommus = <&smmu2 TEGRA264_SID_SDMMC0>;
+ nvidia,pad-autocal-pull-up-offset-3v3-timeout = <0x07>;
+ nvidia,pad-autocal-pull-down-offset-3v3-timeout = <0x07>;
+ nvidia,pad-autocal-pull-up-offset-1v8-timeout = <0x06>;
+ nvidia,pad-autocal-pull-down-offset-1v8-timeout = <0x07>;
+ nvidia,pad-autocal-pull-up-offset-sdr104 = <0x00>;
+ nvidia,pad-autocal-pull-down-offset-sdr104 = <0x00>;
+ nvidia,default-tap = <0x6>;
+ nvidia,default-trim = <0x0>;
+ sd-uhs-sdr12;
+ sd-uhs-sdr25;
+ sd-uhs-sdr50;
+ sd-uhs-sdr104;
+ mmc-hs200-1_8v;
+ dma-coherent;
+ status = "disabled";
+ };
+
i2c0: i2c@c630000 {
compatible = "nvidia,tegra264-i2c";
reg = <0x00 0x0c630000 0x0 0x10000>;
--
2.17.1
prev parent reply other threads:[~2026-07-24 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 7:56 [PATCH 0/5] mmc: tegra: Add Tegra238 and Tegra264 SDHCI support Prathamesh Shete
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 ` Prathamesh Shete [this message]
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-6-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