public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Bhavya Kapoor <b-kapoor@ti.com>,
	Dasnavis Sabiya <sabiya.d@ti.com>, Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH 4/7] arm64: dts: ti: k3-j721s2-main: Enable support for SDR104 speed mode
Date: Thu, 11 Apr 2024 17:52:54 -0500	[thread overview]
Message-ID: <20240411225257.383889-5-jm@ti.com> (raw)
In-Reply-To: <20240411225257.383889-1-jm@ti.com>

From: Bhavya Kapoor <b-kapoor@ti.com>

According to TRM for J721S2, SDR104 speed mode is supported by the SoC
but its capabilities were masked in device tree. Remove sdhci-caps-mask
to enable support for SDR104 speed mode for SD card in J721S2 SoC.

[+] Refer to : section 12.3.6.1.1 MMCSD Features, in J721S2 TRM
- https://www.ti.com/lit/zip/spruj28

Fixes: b8545f9d3a54 ("arm64: dts: ti: Add initial support for J721S2 SoC")
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
---
 arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 2 --
 1 file changed, 2 deletions(-)

diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
index 3cb06a7e4117f..9ed6949b40e9d 100644
--- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
@@ -768,8 +768,6 @@ main_sdhci1: mmc@4fb0000 {
 		ti,clkbuf-sel = <0x7>;
 		ti,trm-icp = <0x8>;
 		dma-coherent;
-		/* Masking support for SDR104 capability */
-		sdhci-caps-mask = <0x00000003 0x00000000>;
 		status = "disabled";
 	};
 
-- 
2.43.2


  parent reply	other threads:[~2024-04-11 22:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 22:52 [PATCH 0/7] MMC updates for TI K3 platforms Judith Mendez
2024-04-11 22:52 ` [PATCH 1/7] arm64: dts: ti: k3-am65-main: Update sdhci properties Judith Mendez
2024-04-11 22:52 ` [PATCH 2/7] arm64: dts: ti: k3-am65-main: Remove unused properties in sdhci nodes Judith Mendez
2024-04-11 22:52 ` [PATCH 3/7] arm64: dts: ti: k3-am62a: Enable UHS mode support for SD cards Judith Mendez
2024-04-11 22:52 ` Judith Mendez [this message]
2024-04-11 22:52 ` [PATCH 5/7] arm64: dts: ti: k3-j784s4-main: Enable support for UHS mode Judith Mendez
2024-04-11 22:52 ` [PATCH 6/7] arm64: dts: ti: k3-am69-sk: Remove HS400 mode support for eMMC Judith Mendez
2024-04-12  4:53   ` Kumar, Udit
2024-04-12 22:14     ` Judith Mendez
2024-04-11 22:52 ` [PATCH 7/7] arm64: dts: ti: k3-j784s4-evm: " Judith Mendez
2024-04-12  4:52   ` Kumar, Udit
2024-04-12 22:14     ` Judith Mendez
2024-04-12 13:46 ` [PATCH 0/7] MMC updates for TI K3 platforms Rob Herring

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=20240411225257.383889-5-jm@ti.com \
    --to=jm@ti.com \
    --cc=b-kapoor@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=sabiya.d@ti.com \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.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