]> git.ipfire.org Git - thirdparty/u-boot.git/commit
Revert "mmc: mmc-uclass: Use max-frequency from device tree with default handling"
authorTanmay Kathpalia <tanmay.kathpalia@altera.com>
Thu, 8 Jan 2026 11:40:02 +0000 (03:40 -0800)
committerPeng Fan <peng.fan@nxp.com>
Thu, 8 Jan 2026 14:23:48 +0000 (22:23 +0800)
commitc4f5b1d4b037beeb538cf6dee0a16cd196539273
treef6c46cd59bc5fe905308301c4a1bef0f9e3156ff
parent3f208e1a99203c8ff257202a2e8447cc43a666c9
Revert "mmc: mmc-uclass: Use max-frequency from device tree with default handling"

This reverts commit aebb523a23818a8ee4199c9532b51e3d4020696f.

The change to use dev_read_u32_default() with a default value of 0
causes regression for host controller drivers that hardcode f_max
before calling mmc_of_parse().

When the "max-frequency" property is not specified in the device tree,
dev_read_u32_default() returns 0, which overwrites the previously
configured f_max value set by the driver. This effectively resets
the maximum frequency to 0, breaking MMC functionality for those
controllers.

Revert to the original dev_read_u32() behavior which only updates
cfg->f_max when the "max-frequency" property is explicitly present
in the device tree, preserving driver-configured values otherwise.

Signed-off-by: Tanmay Kathpalia <tanmay.kathpalia@altera.com>
Signed-off-by: Peng Fan <peng.fan@nxp.com>
drivers/mmc/mmc-uclass.c