linux-kernel - Re: [PATCH] arm64: dts: imx8mp-var-som: Fix LDO5 shutdown causing SD card timeout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174610123214.1957273.17506465011735193373.robh@kernel.org>
Date: Thu, 01 May 2025 07:08:18 -0500
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Himanshu Bhavani <himanshu.bhavani@...iconsignals.io>
Cc: imx@...ts.linux.dev, Sascha Hauer <s.hauer@...gutronix.de>, 
 krzk+dt@...nel.org, devicetree@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, tarang.raval@...iconsignals.io, 
 linux-kernel@...r.kernel.org, 
 Pengutronix Kernel Team <kernel@...gutronix.de>, 
 Shawn Guo <shawnguo@...nel.org>, Fabio Estevam <festevam@...il.com>, 
 Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH] arm64: dts: imx8mp-var-som: Fix LDO5 shutdown causing
 SD card timeout


On Thu, 01 May 2025 11:16:03 +0530, Himanshu Bhavani wrote:
> Fix SD card timeout issue caused by LDO5 regulator getting disabled
> after boot.
> 
> The kernel log shows LDO5 being disabled, which leads to a timeout
> on USDHC2:
> [   33.760561] LDO5: disabling
> [   81.119861] mmc1: Timeout waiting for hardware interrupt.
> 
> To prevent this, set regulator-boot-on and regulator-always-on for
> LDO5. Also add the vqmmc regulator to properly support 1.8V/3.3V
> signaling for USDHC2 using a GPIO-controlled regulator.
> 
> Fixes: 6c2a1f4f71258 ("arm64: dts: imx8mp-var-som-symphony: Add Variscite Symphony board and VAR-SOM-MX8MP SoM")
> Signed-off-by: Himanshu Bhavani <himanshu.bhavani@...iconsignals.io>
> ---
> 
> kernel hangs during boot with the following logs:
> 
> [   33.760561] LDO5: disabling
> [   81.119861] mmc1: Timeout waiting for hardware interrupt.
> [   81.119872] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
> [   81.119876] mmc1: sdhci: Sys addr:  0x00000010 | Version:  0x00000002
> [   81.119882] mmc1: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000010
> [   81.119886] mmc1: sdhci: Argument:  0x00844358 | Trn mode: 0x0000002b
> [   81.119891] mmc1: sdhci: Present:   0x01f88009 | Host ctl: 0x00000012
> [   81.119896] mmc1: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
> [   81.119900] mmc1: sdhci: Wake-up:   0x00000008 | Clock:    0x0000003f
> [   81.119904] mmc1: sdhci: Timeout:   0x0000008f | Int stat: 0x00000000
> [   81.119908] mmc1: sdhci: Int enab:  0x117f100b | Sig enab: 0x117f100b
> [   81.119912] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000502
> [   81.119917] mmc1: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000b407
> [   81.119921] mmc1: sdhci: Cmd:       0x0000193a | Max curr: 0x00ffffff
> [   81.119925] mmc1: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0x0076b27f
> [   81.119929] mmc1: sdhci: Resp[2]:   0x325b5900 | Resp[3]:  0x00000900
> [   81.119933] mmc1: sdhci: Host ctl2: 0x00000008
> [   81.119937] mmc1: sdhci: ADMA Err:  0x00000003 | ADMA Ptr: 0x4003f204
> [   81.119941] mmc1: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP =========
> [   81.119944] mmc1: sdhci-esdhc-imx: cmd debug status:  0x21b0
> [   81.119949] mmc1: sdhci-esdhc-imx: data debug status:  0x2200
> [   81.119954] mmc1: sdhci-esdhc-imx: trans debug status:  0x2300
> [   81.119959] mmc1: sdhci-esdhc-imx: dma debug status:  0x2400
> [   81.119964] mmc1: sdhci-esdhc-imx: adma debug status:  0x2594
> [   81.119970] mmc1: sdhci-esdhc-imx: fifo debug status:  0x2608
> [   81.119976] mmc1: sdhci-esdhc-imx: async fifo debug status:  0x2798
> [   81.119981] mmc1: sdhci: ===========================================
> 
> ---
>  arch/arm64/boot/dts/freescale/imx8mp-var-som.dtsi | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/next-20250501 (exact match)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/freescale/' for 20250501054604.23368-1-himanshu.bhavani@...iconsignals.io:

arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dtb: regulator-usdhc2-vqmmc (regulator-gpio): 'gpios' is a required property
	from schema $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dtb: regulator-usdhc2-vqmmc (regulator-gpio): Unevaluated properties are not allowed ('gpio' was unexpected)
	from schema $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#