[PATCH 3/5] mms: sdhci-esdhc-imx: Fix SDHCI_RESET_ALL for CQHCI

Bough Chen haibo.chen at nxp.com
Tue Oct 18 00:22:04 PDT 2022


> -----Original Message-----
> From: Brian Norris <briannorris at chromium.org>
> Sent: 2022年10月18日 11:57
> To: Ulf Hansson <ulf.hansson at linaro.org>
> Cc: Shawn Lin <shawn.lin at rock-chips.com>; Adrian Hunter
> <adrian.hunter at intel.com>; Shawn Guo <shawnguo at kernel.org>; Fabio
> Estevam <festevam at gmail.com>; Faiz Abbas <faiz_abbas at ti.com>;
> dl-linux-imx <linux-imx at nxp.com>; Bough Chen <haibo.chen at nxp.com>; Al
> Cooper <alcooperx at gmail.com>; linux-mmc at vger.kernel.org; Pengutronix
> Kernel Team <kernel at pengutronix.de>; linux-kernel at vger.kernel.org; Florian
> Fainelli <f.fainelli at gmail.com>; Sascha Hauer <s.hauer at pengutronix.de>;
> Thierry Reding <thierry.reding at gmail.com>; Michal Simek
> <michal.simek at xilinx.com>; Jonathan Hunter <jonathanh at nvidia.com>;
> Sowjanya Komatineni <skomatineni at nvidia.com>;
> linux-arm-kernel at lists.infradead.org; Broadcom internal kernel review list
> <bcm-kernel-feedback-list at broadcom.com>; Brian Norris
> <briannorris at chromium.org>
> Subject: [PATCH 3/5] mms: sdhci-esdhc-imx: Fix SDHCI_RESET_ALL for CQHCI
> 
>  [[ NOTE: this is completely untested by the author, but included solely
>     because, as noted in commit df57d73276b8 ("mmc: sdhci-pci: Fix
>     SDHCI_RESET_ALL for CQHCI for Intel GLK-based controllers"), "other
>     drivers using CQHCI might benefit from a similar change, if they
>     also have CQHCI reset by SDHCI_RESET_ALL." We've now seen the same
>     bug on at least MSM, Arasan, and Intel hardware. ]]
> 
> SDHCI_RESET_ALL resets will reset the hardware CQE state, but we aren't
> tracking that properly in software. When out of sync, we may trigger various
> timeouts.
> 
> It's not typical to perform resets while CQE is enabled, but this may occur in
> some suspend or error recovery scenarios.
> 
> Fixes: bb6e358169bf ("mmc: sdhci-esdhc-imx: add CMDQ support")
> Signed-off-by: Brian Norris <briannorris at chromium.org>
> ---
> 
>  drivers/mmc/host/sdhci-esdhc-imx.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
> b/drivers/mmc/host/sdhci-esdhc-imx.c
> index 55981b0f0b10..222c83929e20 100644
> --- a/drivers/mmc/host/sdhci-esdhc-imx.c
> +++ b/drivers/mmc/host/sdhci-esdhc-imx.c
> @@ -1288,6 +1288,13 @@ static void esdhc_set_uhs_signaling(struct
> sdhci_host *host, unsigned timing)
> 
>  static void esdhc_reset(struct sdhci_host *host, u8 mask)  {
> +	struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host);
> +	struct pltfm_imx_data *imx_data = sdhci_pltfm_priv(pltfm_host);
> +
> +	if ((host->mmc->caps2 & MMC_CAP2_CQE) && (mask & SDHCI_RESET_ALL)
> &&
> +	    imx_data->socdata->flags & ESDHC_FLAG_CQHCI)

I think we can remove the condition " imx_data->socdata->flags & ESDHC_FLAG_CQHCI" here.
According to code logic, host->mmc->caps2 & MMC_CAP2_CQE means it already contain imx_data->socdata->flags & ESDHC_FLAG_CQHCI

Best Regards
Haibo Chen


> +		cqhci_deactivate(host->mmc);
> +
>  	sdhci_reset(host, mask);
> 
>  	sdhci_writel(host, host->ier, SDHCI_INT_ENABLE);
> --
> 2.38.0.413.g74048e4d9e-goog



More information about the linux-arm-kernel mailing list