All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Judith Mendez <jm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: dts: am654: Add 650ms power off delay for proper MMC power cycle
Date: Tue, 8 Sep 2026 12:49:34 -0500	[thread overview]
Message-ID: <20260908174934.pbbvtrfhlnjinipu@constable> (raw)
In-Reply-To: <e8abc328-578e-48cb-a469-1e3edec6780a@ti.com>

On 12:29-20260908, Judith Mendez wrote:
> Hi Nishanth,
> 
> On 9/8/26 12:16, Nishanth Menon wrote:
> > On 12:06-20260908, Judith Mendez wrote:
> > > The AM65x EVM MMC1 VDD rail discharges slowly through RC circuit.
> > > SD spec (section 6.4.1.3) requires VDD < 0.5V for minimum 1ms during
> > > power cycle. Measured discharge time on this board is ~632.97ms to
> > > reach < 0.5V threshold.
> > > 
> > > During boot, MMC power cycles between boot stages. Without power off
> > > delay, VDD doesn't fully discharge. Card retains 1.8V signaling state
> > > from previous stages. When U-Boot initializes, card no longer asserts
> > > S18A in ACMD41 response (already switched to 1.8V). Host misinterprets
> > > card state and forces 1.8V anyway, falling into a bad state and causing
> > > a boot failure.
> > > 
> > > Add power-off-delay-us = 650000 (650ms) to ensure proper VDD discharge
> > > during power cycles, allowing card to fully reset state between boot
> > > stages.
> > > 
> > > Signed-off-by: Judith Mendez <jm@ti.com>
> > 
> > Fixes ?
> 
> Fix is really for u-boot, don't think I can point to a u-boot
> commit here can I?

You'd face the same problem if you are starting from a different boot
media and then enable MMC in linux kernel, right? what was described in
the patch sounds like a discharge latency of the evm. This was missed in
the original commit?

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource


  reply	other threads:[~2026-09-08 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 17:06 [PATCH] mmc: dts: am654: Add 650ms power off delay for proper MMC power cycle Judith Mendez
2026-09-08 17:15 ` sashiko-bot
2026-09-08 17:16 ` Nishanth Menon
2026-09-08 17:29   ` Judith Mendez
2026-09-08 17:49     ` Nishanth Menon [this message]
2026-09-08 18:13       ` Judith Mendez
2026-09-09 10:36         ` Nishanth Menon
2026-09-09 15:36           ` 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=20260908174934.pbbvtrfhlnjinipu@constable \
    --to=nm@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jm@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.