From: Judith Mendez <jm@ti.com>
To: Judith Mendez <jm@ti.com>, Ulf Hansson <ulf.hansson@linaro.org>,
Nishanth Menon <nm@ti.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Josua Mayer <josua@solid-run.com>, <linux-mmc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Francesco Dolcini <francesco@dolcini.it>,
Hiago De Franco <hiagofranco@gmail.com>,
Moteen Shah <m-shah@ti.com>, <stable@vger.kernel.org>
Subject: [PATCH RESEND v3 1/3] dt-bindings: mmc: sdhci-am654: Add ti,suppress-v1p8-ena
Date: Tue, 22 Apr 2025 17:05:10 -0500 [thread overview]
Message-ID: <20250422220512.297396-2-jm@ti.com> (raw)
In-Reply-To: <20250422220512.297396-1-jm@ti.com>
Some Microcenter/Patriot SD cards and Kingston eMMC are failing init
across Sitara K3 boards. Init failure is due to the sequence when
V1P8_SIGNAL_ENA is set. The V1P8_SIGNAL_ENA has a timing component tied
to it where if set, switch to full-cycle timing happens. The failing
cards do not like change to full-cycle timing before changing bus
width, so add flag to sdhci-am654 binding to suppress V1P8_SIGNAL_ENA
before changing bus width. The switch to full-cycle timing should happen
with HIGH_SPEED_ENA after change of bus width.
Signed-off-by: Judith Mendez <jm@ti.com>
---
Documentation/devicetree/bindings/mmc/sdhci-am654.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/sdhci-am654.yaml b/Documentation/devicetree/bindings/mmc/sdhci-am654.yaml
index 676a74695389..0f92bbf8e13b 100644
--- a/Documentation/devicetree/bindings/mmc/sdhci-am654.yaml
+++ b/Documentation/devicetree/bindings/mmc/sdhci-am654.yaml
@@ -201,6 +201,11 @@ properties:
and the controller is required to be forced into Test mode
to set the TESTCD bit.
+ ti,suppress-v1p8-ena:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ When present, V1P8_SIGNAL_ENA shall be suppressed.
+
required:
- compatible
- reg
--
2.49.0
next prev parent reply other threads:[~2025-04-22 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 22:05 [PATCH RESEND v3 0/3] Add ti,suppress-v1p8-ena Judith Mendez
2025-04-22 22:05 ` Judith Mendez [this message]
2025-04-22 22:06 ` [PATCH RESEND v3 1/3] dt-bindings: mmc: sdhci-am654: " kernel test robot
2025-04-25 7:48 ` Krzysztof Kozlowski
2025-04-25 14:19 ` Judith Mendez
2025-04-22 22:05 ` [PATCH RESEND v3 2/3] mmc: sdhci_am654: Add sdhci_am654_start_signal_voltage_switch Judith Mendez
2025-04-22 22:05 ` [PATCH RESEND v3 3/3] arm64: dts: ti: k3-am62*: add ti,suppress-v1p8-ena Judith Mendez
2025-04-23 18:08 ` [PATCH RESEND v3 0/3] Add ti,suppress-v1p8-ena Nishanth Menon
2025-04-23 22:27 ` Judith Mendez
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=20250422220512.297396-2-jm@ti.com \
--to=jm@ti.com \
--cc=adrian.hunter@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=hiagofranco@gmail.com \
--cc=josua@solid-run.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--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