public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Christoph Stoidner <C.Stoidner@phytec.de>
Cc: Peng Fan <peng.fan@nxp.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: AW: [PATCH] mmc: Fix missing 1 ms delay after mmc power up
Date: Tue, 18 Nov 2025 12:56:33 +0800	[thread overview]
Message-ID: <aRv8gc0FNwulrsRm@nxa18884-linux> (raw)
In-Reply-To: <DB9P195MB1212DC55E27674A4194719C497CEA@DB9P195MB1212.EURP195.PROD.OUTLOOK.COM>

On Mon, Nov 10, 2025 at 08:46:39PM +0000, Christoph Stoidner wrote:
>Hi Peng, thanks for your feedback.
>
>> Hi Christoph
>> 
>> Thanks for your patch.
>> 
>> > Subject: [PATCH] mmc: Fix missing 1 ms delay after mmc power up
>...
>> > +     udelay(2000);
>> 
>> Per spec,
>> From Figure 6-4: Power-up Diagram of Card
>> the 1ms is voltageSupply ramp up time, so I am thinking the fix
>> should be in your regulator side, saying startup-delay-us property
>> in your regulator node.
>
>True, this could also be handled via the regulator?s DTS properties, and
>some boards already do that. However, from my point of view, that?s not
>the right place for this particular delay.
>
>The SD specification distinguishes between two different delays
>(see Figure 6-5 ?Power-Up Diagram (Host)? in SD Spec 6.00, ?6.4.1):
>
>   1) "Power ramp up"
>   2) "Stable voltage delay"
>
>The first one (power ramp up) is regulator-specific and should indeed be
>covered by the regulator?s startup-delay-us property in the device tree.
>But this patch is about the second one - the "stable voltage delay".
>
>That delay is completely independent of any regulator/voltage-supply or
>board characteristics; it is a constant 1ms delay by the SD interface itself
>to ensure correct card initialization timing. 
>Decoupling it from the regulators would make board-code developers
>live easier, and can make U-Boot?s MMC initialization more robust across
>all boards.
>
>What do you think about that?

Sorry for late.
Thanks for explaining this, this is reasonable. I am thinking it might be better
if we add ios.post_power_delay_ms for your platform.

Regards
Peng

>
>Regards,
>Christoph
>
>> Thanks,
>> Peng.
>> 
>> > +     return ret;
>...

  reply	other threads:[~2025-11-18  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 14:59 [PATCH] mmc: Fix missing 1 ms delay after mmc power up Christoph Stoidner
2025-11-04  8:34 ` Peng Fan
2025-11-10 20:46   ` AW: " Christoph Stoidner
2025-11-18  4:56     ` Peng Fan [this message]
2025-11-28 12:38       ` Christoph Stoidner
2026-01-05  2:49         ` Peng Fan
     [not found] ` <a41edf4c-39f5-432e-8eeb-9426dba89a17@freeshell.de>
     [not found]   ` <DB9P195MB12122313AC9E54232C3B713D97CCA@DB9P195MB1212.EURP195.PROD.OUTLOOK.COM>
2025-11-12 20:25     ` E Shattow
2026-01-08 13:32 ` Peng Fan

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=aRv8gc0FNwulrsRm@nxa18884-linux \
    --to=peng.fan@oss.nxp.com \
    --cc=C.Stoidner@phytec.de \
    --cc=jh80.chung@samsung.com \
    --cc=peng.fan@nxp.com \
    --cc=u-boot@lists.denx.de \
    /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