mmc: mmci: stm32: fix max busy timeout calculation

The way that the timeout is currently calculated could lead to a u64 timeout value. this value is then cast in a u32 register that leads to mmc erase failed issue with some SD cards. Change-Id: Ibe2682ba42e878c30b61471672800f5fc04ce87c Signed-off-by: Christophe Kerello <[email protected]> Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/linux-stm32/+/311057 Tested-by: Eric FOURMONT <[email protected]> Reviewed-by: Eric FOURMONT <[email protected]> Domain-Review: Eric FOURMONT <[email protected]>
STMicroelectronics · Jun 16, 2023 · d33b43a · d33b43a
1 parent e689673
commit d33b43a
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c
@@ -1746,7 +1746,8 @@ static void mmci_set_max_busy_timeout(struct mmc_host *mmc)
 		return;
 
 	if (host->variant->busy_timeout && mmc->actual_clock)
-		max_busy_timeout = ~0UL / (mmc->actual_clock / MSEC_PER_SEC);
+		max_busy_timeout = U32_MAX / DIV_ROUND_UP(mmc->actual_clock,
+							  MSEC_PER_SEC);
 
 	mmc->max_busy_timeout = max_busy_timeout;
 }