From: sashiko-bot@kernel.org
To: "Tanmay Kathpalia" <tanmay.kathpalia@altera.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/8] arm64: dts: agilex5: add SD/eMMC host controller
Date: Thu, 20 Aug 2026 19:11:19 +0000 [thread overview]
Message-ID: <20260820191119.BD6B11F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260820185721.22823-3-tanmay.kathpalia@altera.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Warm reboot failure due to UHS-I (SDR104) enabled with a fixed, always-on VMMC regulator.
--
--- Patch [2]: [PATCH v5 2/8] arm64: dts: agilex5: add SD/eMMC host controller ---
commit e282634760a9fadb886896083cbc7186c285bb38
Author: Tanmay Kathpalia <tanmay.kathpalia@altera.com>
arm64: dts: agilex5: add SD/eMMC host controller
This commit adds the SD/eMMC host controller node to the Agilex5 HPS
device tree. It configures the controller for SD card operation on the
SOCDK OOBE board, utilizing a fixed 3.3V supply and a switchable I/O
voltage regulator to support UHS-I SDR104 signaling.
> diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
> index 57d3c5807c65c..93222b199038d 100644
> --- a/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
> +++ b/arch/arm64/boot/dts/intel/socfpga_agilex5_socdk.dts
[ ... ]
> + vmmc_reg: regulator-fixed-3p3v {
> + compatible = "regulator-fixed";
> + regulator-always-on;
> + regulator-max-microvolt = <3300000>;
> + regulator-min-microvolt = <3300000>;
> + regulator-name = "vcc-sd";
> + };
> };
>
> -&gpio0 {
> +&emmc {
> + bus-width = <4>;
> + cap-sd-highspeed;
> + disable-wp;
> + max-frequency = <200000000>;
> + no-mmc;
> + sd-uhs-sdr104;
[Severity: High]
Will this combination of a fixed, always-on VMMC regulator and UHS-I SDR104
enabled cause warm reboot failures?
If the kernel negotiates UHS-I, it switches the SD card's signaling voltage
to 1.8V. During a warm reboot, the kernel shuts down the SD controller,
but because vmmc_reg is marked regulator-always-on, physical power to the
SD card is never cut.
When the CPU resets, the BootROM or SPL will attempt to boot from the SD
card using the default 3.3V signaling. Since the SD card never lost power,
it is still expecting 1.8V signaling, which typically causes the boot
process to hang.
Since SD cards lack a dedicated hardware reset pin, would it be better to
remove the sd-uhs-* properties unless the host can physically toggle the
VMMC power?
> + vmmc-supply = <&vmmc_reg>;
> + vqmmc-supply = <&vqmmc_io_reg>;
> +
> status = "okay";
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260820185721.22823-1-tanmay.kathpalia@altera.com?part=2
next prev parent reply other threads:[~2026-08-20 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:57 [PATCH v5 0/8] mmc: sdhci-cadence: add SD6HC support and Agilex5 enablement Tanmay Kathpalia
2026-08-20 18:57 ` [PATCH v5 1/8] dt-bindings: mmc: add Cadence SD6HC binding Tanmay Kathpalia
2026-08-20 18:57 ` [PATCH v5 2/8] arm64: dts: agilex5: add SD/eMMC host controller Tanmay Kathpalia
2026-08-20 19:11 ` sashiko-bot [this message]
2026-08-20 18:57 ` [PATCH v5 3/8] dt-bindings: arm: altera: add Agilex5 SOCDK eMMC board variant Tanmay Kathpalia
2026-08-20 18:57 ` [PATCH v5 4/8] arm64: dts: agilex5: add SOCDK eMMC daughter board Tanmay Kathpalia
2026-08-20 18:57 ` [PATCH v5 5/8] mmc: sdhci-cadence: rename SD4HC symbols for SD6HC groundwork Tanmay Kathpalia
2026-08-20 19:06 ` sashiko-bot
2026-08-20 18:57 ` [PATCH v5 6/8] mmc: sdhci-cadence: refactor driver structure for V6 controller support Tanmay Kathpalia
2026-08-20 18:57 ` [PATCH v5 7/8] mmc: sdhci-cadence: add Cadence SD6HC support Tanmay Kathpalia
2026-08-20 19:14 ` sashiko-bot
2026-08-20 18:57 ` [PATCH v5 8/8] mmc: sdhci-cadence: add Altera Agilex5 " Tanmay Kathpalia
2026-08-20 19:16 ` sashiko-bot
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=20260820191119.BD6B11F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tanmay.kathpalia@altera.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