Re: [PATCH] mmc: dwcmshc_bf3_hw_reset: Log eMMC reset calls

From: Adrian Hunter

Date: Fri Jul 03 2026 - 09:58:17 EST


On 18/06/2026 13:53, Satyansh Shukla wrote:
> Log when the BlueField-3 eMMC hardware reset path is invoked and
> whether the RST_N SMC call succeeds.
>
> This makes it easier to diagnose cases where the controller recovery path
> depends on issuing an eMMC reset, and helps confirm that the reset sequence
> was attempted on affected systems.
>
> Signed-off-by: Satyansh Shukla <satyansh.shukla@xxxxxxxxxx>
> ---
> drivers/mmc/host/sdhci-of-dwcmshc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/mmc/host/sdhci-of-dwcmshc.c b/drivers/mmc/host/sdhci-of-dwcmshc.c
> index b9ecd91f44ad..8acd4652a12b 100644
> --- a/drivers/mmc/host/sdhci-of-dwcmshc.c
> +++ b/drivers/mmc/host/sdhci-of-dwcmshc.c
> @@ -2019,10 +2019,13 @@ static void dwcmshc_bf3_hw_reset(struct sdhci_host *host)
> {
> struct arm_smccc_res res = { 0 };
>
> + pr_info("%s: resetting...\n", __func__);
> arm_smccc_smc(BLUEFIELD_SMC_SET_EMMC_RST_N, 0, 0, 0, 0, 0, 0, 0, &res);
>
> if (res.a0)
> pr_err("%s: RST_N failed.\n", mmc_hostname(host->mmc));
> + else
> + pr_info("%s: RST_N succeeded.\n", mmc_hostname(host->mmc));

Diagnostic prints need to be pr_debug(). Also 1 print should be enough.

> }
>
> static const struct sdhci_ops sdhci_dwcmshc_bf3_ops = {