From: sashiko-bot@kernel.org
To: "Judith Mendez" <jm@ti.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH] mmc: dts: am654: Add 650ms power off delay for proper MMC power cycle
Date: Tue, 08 Sep 2026 17:15:13 +0000 [thread overview]
Message-ID: <20260908171513.E35991F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908170635.238775-1-jm@ti.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `power-off-delay-us` property is added directly to the MMC host controller node, where it is completely ignored, rendering the boot failure fix entirely ineffective.
--
commit 02105a5fc6c6d24da9df99e671b001a1f3cd6d1c
Author: Judith Mendez <jm@ti.com>
mmc: dts: am654: Add 650ms power off delay for proper MMC power cycle
This commit attempts to fix a boot failure caused by incomplete VDD
discharge during MMC power cycles. It adds a power-off-delay-us property
to the sdhci1 node to provide time for the RC circuit to discharge.
> diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> --- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> @@ -460,6 +460,7 @@ &sdhci0 {
> &sdhci1 {
> status = "okay";
> vmmc-supply = <&vdd_mmc1_sd>;
> + power-off-delay-us = <650000>;
[Severity: Medium]
Will this property actually be parsed by the MMC core here?
When placed directly in the MMC host controller node, the power-off-delay-us
property is completely ignored. It is only parsed when placed inside an
mmc-pwrseq-simple node, rendering this proposed fix ineffective.
Furthermore, even if it were parsed via a pwrseq node, the
mmc_pwrseq_power_off() delay executes before the VDD regulator is disabled by
mmc_set_ios(). This means the delay would occur while VDD is still actively
driven, failing to provide the required time for the RC circuit to discharge.
Should this instead be implemented by adding an off-on-delay-us property
directly to the vdd_mmc1_sd regulator node?
> pinctrl-names = "default";
> pinctrl-0 = <&main_mmc1_pins_default>;
> ti,driver-strength-ohm = <50>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260908170635.238775-1-jm@ti.com?part=1
next prev parent reply other threads:[~2026-09-08 17:15 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 [this message]
2026-09-08 17:16 ` Nishanth Menon
2026-09-08 17:29 ` Judith Mendez
2026-09-08 17:49 ` Nishanth Menon
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=20260908171513.E35991F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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