[PATCH] mmc: dwcmshc_bf3_hw_reset: Log eMMC reset calls

[PATCH] mmc: dwcmshc_bf3_hw_reset: Log eMMC reset calls

[Satyansh Shukla]

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@oracle.com>
---
 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));
 }
 
 static const struct sdhci_ops sdhci_dwcmshc_bf3_ops = {
-- 
2.31.1

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

[Satyansh Shukla]

This is my first upstream patch submission. Feedback on both the change(even though it is tiny) and submission process is appreciated.

Thanks.



________________________________________
From: Satyansh Shukla <satyansh.shukla@oracle.com>
Sent: Thursday, June 18, 2026 4:23 PM
To: Ulf Hansson <ulfh@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>; linux-mmc@vger.kernel.org <linux-mmc@vger.kernel.org>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
Subject: [External] : [PATCH] mmc: dwcmshc_bf3_hw_reset: Log eMMC reset calls
 
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@oracle.com>
---
 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));
 }
 
 static const struct sdhci_ops sdhci_dwcmshc_bf3_ops = {
--
2.31.1

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

[Adrian Hunter]

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@oracle.com>
> ---
>  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 = {

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

[Satyansh Shukla]

Log when the BlueField-3 eMMC hardware reset path is invoked.

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@oracle.com>
---
 drivers/mmc/host/sdhci-of-dwcmshc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/mmc/host/sdhci-of-dwcmshc.c b/drivers/mmc/host/sdhci-of-dwcmshc.c
index eef53455b8ee..a01668b66e7d 100644
--- a/drivers/mmc/host/sdhci-of-dwcmshc.c
+++ b/drivers/mmc/host/sdhci-of-dwcmshc.c
@@ -2013,6 +2013,7 @@ static void dwcmshc_bf3_hw_reset(struct sdhci_host *host)
 {
 	struct arm_smccc_res res = { 0 };
 
+	pr_debug("%s: resetting...\n", __func__);
 	arm_smccc_smc(BLUEFIELD_SMC_SET_EMMC_RST_N, 0, 0, 0, 0, 0, 0, 0, &res);
 
 	if (res.a0)
-- 
2.43.7