u-boot.git/drivers/mmc, branch v2025.10

mmc: rockchip_sdhci: Do not test unsigned for being less than 0

2025-08-30T15:33:32Z

In rockchip_sdhci_execute_tuning the variable tuning_loop_counter is tested for being less than 0. Ensure that it is a signed type by declaring it as s8 instead of char. This issue was found by Smatch. Signed-off-by: Andrew Goodbody Reviewed-by: Peng Fan Reviewed-by: Kever Yang

Merge tag 'u-boot-stm32-20250825' of https://source.denx.de/u-boot/custodians/u-boot-stm

2025-08-26T14:33:10Z

CI: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/27466 - Enable OF_UPSTREAM_BUILD_VENDOR for stm32mp25_defconfig - Fix to avoid inifite loop in stm32_sdmmc2 driver - Populate oobavail field of nand_ecclayout in stm32_fmc2_nand driver

mmc: stm32_sdmmc2: avoid infinite while loop

2025-08-25T14:47:39Z

Avoid unlimited while loop by adding a timeout. The timeout is calculated based on a minimal throughput of 256 KB/s. The timeout is set at least to 2 seconds. Signed-off-by: Christophe Kerello Reviewed-by: Patrice Chotard

mmc: gen_atmel_mci: NULL check variable before use

2025-08-13T09:59:36Z

In mci_send_cmd the pointer 'data' is optional so guard its use with a NULL check to prevent any attempt to dereference it when not provided. This issue was found by Smatch. Signed-off-by: Andrew Goodbody Reviewed-by: Peng Fan

mmc: gen_atmel_mci: Remove duplicate checks

2025-08-13T09:59:36Z

Remove duplicate checks on status from mci_data_read and mci_data_write which are guaranteed to be true as exiting the above do..while loop above requires that to be so. This issue was found by Smatch. Signed-off-by: Andrew Goodbody Reviewed-by: Peng Fan

sunxi: mmc: add support for Allwinner A523 MMC mod clock

2025-07-27T21:57:35Z

The Allwinner A523 SoC has a slightly changed mod clock, where the P factor, formerly a shift value, is now a second divider value. Also the input clock is not PLL_PERIPH0 (600MHz) anymore, but PLL_PERIPH0_400M (for MMC0/1), so adjust the input rate calculation accordingly. MMC2 has a different set of parents, so the input clock is 800 MHz there. Adjust for all of this. Signed-off-by: Andre Przywara

Fix emmc error state after mmc write timeout

2025-07-24T04:43:31Z

This is a fix for the sporadic mmc write failure: mmc write failed 0 blocks written: ERROR After this happens the emmc will remain in an error state where subsequent read/writes fail with a timeout. The mmc driver sends CMD25 - WRITE_MULTIPLE_BLOCK which can sporadically timeout. When this happens, the mmc driver aborts the transfer and returns the above error messages. But the emmc still remains in data transfer mode, since the timeout was decided by uboot, not by the emmc. Fix this by sending the STOP_TRANSMISSION command (CMD12) and waiting for the emmc to be in ready state again (CMD13). Transferring data blocks after a CMD25 can take anywhere between 5 and +15s on Samsung EMMCs and the current timeout is not enough. Increase the timeout by 2x to accommodate the long transfer times observed. Signed-off-by: Iulian Banaga Acked-by: Jimmy Durand Wesolowski Reviewed-by: Peng Fan Signed-off-by: Peng Fan

mmc: exynos_dw_mmc: add exynos5420 compatibles

2025-07-24T04:35:38Z

The exynos5420 DTSes in linux kernel uses the compatibles samsung,exynos5420-dw-mshc{,-smu} instead of just samsung,exynos-dwmmc. Match the additional compatibles in the driver to make it possible to use it with DTSes from Linux kernel. Signed-off-by: Jaehoon Chung [ grimler: rebase after clksel reg abstraction and re-write commit message ] Signed-off-by: Henrik Grimler Reviewed-by: Sam Protsenko Reviewed-by: Anand Moon Signed-off-by: Peng Fan

mmc: s5p_sdhci: add samsung,exynos4210-sdhci compatible

2025-07-24T04:35:35Z

the Exynos4210 devices in u-boot uses samsung,exynos4412-sdhci as sdhci compatible in their DTSes, while the upstream DTSes uses samsung,exynos4210-sdhci. Add samsung,exynos4210-sdhci compatible string for s5p_sdhci driver as well so that it can be used with upstream DTSes. Signed-off-by: Henrik Grimler Reviewed-by: Anand Moon Reviewed-by: Sam Protsenko Signed-off-by: Peng Fan

mmc: s5p_sdhci: remove duplicated card detect code

2025-07-24T04:35:34Z

The common sdhci infrastructure is already parsing the cd-gpios property, since commit 451931ea7002 ("mmc: sdhci: Read cd-gpio from devicetree"). The s5p code is therefore duplicated, and also broken since it assumes that the GPIO value is inverted, while the sdhci code correctly follows the ACTIVE_LOW/ACTIVE_HIGH flag specified in the device tree. This fix was originally authored by Simon Shields: https://github.com/fourkbomb/u-boot/commit/2eac9dea7903 The change has been tested on exynos4210-i9100, a device similar to exynos4210-trats. Signed-off-by: Henrik Grimler Reviewed-by: Anand Moon Reviewed-by: Sam Protsenko Signed-off-by: Peng Fan