From: Adrian Hunter <adrian.hunter@intel.com>
To: "Benoît Thébaudeau" <benoit@wsystem.com>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
joancarles <joancarles@fqingenieria.es>,
"Eric Bénard" <eric@eukrea.com>,
"Wolfram Sang" <wsa@the-dreams.de>
Subject: Re: [PATCH 4/4] mmc: sdhci-esdhc-imx: Remove the ENGcm07207 workaround
Date: Mon, 29 May 2017 11:07:18 +0300 [thread overview]
Message-ID: <b5c8c521-c2a7-89bf-8c36-519558079464@intel.com> (raw)
In-Reply-To: <1493805925-3644-4-git-send-email-benoit@wsystem.com>
On 03/05/17 13:05, Benoît Thébaudeau wrote:
> The SDHCI_QUIRK_NO_MULTIBLOCK quirk was used as a workaround for the
> ENGcm07207 erratum. However, it caused excruciatingly slow SD transfers
> (300 kB/s on average), and this erratum actually does not imply that
> multiple-block transfers are not supported, so this was overkill.
>
> The suggested workaround for this erratum is to set SYSCTL.RSTA, but the
> simple DAT line software reset (which resets the DMA circuit among
> others) triggered by sdhci_finish_data() in case of errors seems to be
> sufficient. Indeed, generating errors in a controlled manner on i.MX25
> using the FEVT register right in the middle of read data transfers
> without this quirk shows that nothing is written to the buffer by the
> eSDHC past CMD12, and no extra Auto CMD12 is sent with AC12EN set, so
> the data transfers on AHB are properly aborted. For write data
> transfers, neither extra data nor extra Auto CMD12 is sent, as expected.
> Moreover, after intensive stress tests on i.MX25, removing
> SDHCI_QUIRK_NO_MULTIBLOCK seems to be safe.
>
> Signed-off-by: Benoît Thébaudeau <benoit@wsystem.com>
Aside from one comment below...
I would expect to see Acks from other sdhci-esdhc-imx users. Nevertheless,
for sdhci:
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> drivers/mmc/host/sdhci-esdhc-imx.c | 16 +++-------------
> 1 file changed, 3 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c b/drivers/mmc/host/sdhci-esdhc-imx.c
> index fa60d13..868a51f 100644
> --- a/drivers/mmc/host/sdhci-esdhc-imx.c
> +++ b/drivers/mmc/host/sdhci-esdhc-imx.c
> @@ -115,11 +115,6 @@
> */
> #define ESDHC_FLAG_MULTIBLK_NO_INT BIT(1)
> /*
> - * The flag enables the workaround for ESDHC errata ENGcm07207 which
> - * affects i.MX25 and i.MX35.
> - */
> -#define ESDHC_FLAG_ENGCM07207 BIT(2)
> -/*
> * The flag tells that the ESDHC controller is an USDHC block that is
> * integrated on the i.MX6 series.
> */
> @@ -149,11 +144,11 @@ struct esdhc_soc_data {
> };
>
> static struct esdhc_soc_data esdhc_imx25_data = {
> - .flags = ESDHC_FLAG_ENGCM07207,
> + .flags = ESDHC_FLAG_ERR004536,
> };
>
> static struct esdhc_soc_data esdhc_imx35_data = {
> - .flags = ESDHC_FLAG_ENGCM07207,
> + .flags = ESDHC_FLAG_ERR004536,
> };
>
> static struct esdhc_soc_data esdhc_imx51_data = {
> @@ -286,7 +281,7 @@ static u32 esdhc_readl_le(struct sdhci_host *host, int reg)
> * ADMA2 capability of esdhc, but this bit is messed up on
> * some SOCs (e.g. on MX25, MX35 this bit is set, but they
> * don't actually support ADMA2). So set the BROKEN_ADMA
> - * uirk on MX25/35 platforms.
> + * quirk on MX25/35 platforms.
Please do spelling fixes as a separate patch. Note there are several
spelling errors in comments in drivers/mmc/host/sdhci-esdhc-imx.c so you
could easily do a few of them to make a separate patch more worthwhile.
> */
>
> if (val & SDHCI_CAN_DO_ADMA1) {
> @@ -1278,11 +1273,6 @@ static int sdhci_esdhc_imx_probe(struct platform_device *pdev)
> if (IS_ERR(imx_data->pins_default))
> dev_warn(mmc_dev(host->mmc), "could not get default state\n");
>
> - if (imx_data->socdata->flags & ESDHC_FLAG_ENGCM07207)
> - /* Fix errata ENGcm07207 present on i.MX25 and i.MX35 */
> - host->quirks |= SDHCI_QUIRK_NO_MULTIBLOCK
> - | SDHCI_QUIRK_BROKEN_ADMA;
> -
> if (esdhc_is_usdhc(imx_data)) {
> host->quirks2 |= SDHCI_QUIRK2_PRESET_VALUE_BROKEN;
> host->mmc->caps |= MMC_CAP_1_8V_DDR;
>
next prev parent reply other threads:[~2017-05-29 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:05 [PATCH 1/4] mmc: sdhci-esdhc: Add SDHCI_QUIRK_32BIT_DMA_ADDR Benoît Thébaudeau
2017-05-03 10:05 ` [PATCH 2/4] mmc: sdhci-esdhc-imx: Fix DAT line software reset Benoît Thébaudeau
2017-05-29 8:02 ` Adrian Hunter
2017-05-29 11:13 ` Fabio Estevam
2017-05-03 10:05 ` [PATCH 3/4] mmc: sdhci-esdhc-imx: Allow all supported prescaler values Benoît Thébaudeau
2017-05-29 8:03 ` Adrian Hunter
2017-05-29 11:14 ` Fabio Estevam
2017-05-03 10:05 ` [PATCH 4/4] mmc: sdhci-esdhc-imx: Remove the ENGcm07207 workaround Benoît Thébaudeau
2017-05-29 8:07 ` Adrian Hunter [this message]
2017-05-29 14:42 ` Ulf Hansson
2017-05-29 16:39 ` Benoît Thébaudeau
2017-05-29 11:14 ` Fabio Estevam
2017-05-04 8:47 ` [PATCH 1/4] mmc: sdhci-esdhc: Add SDHCI_QUIRK_32BIT_DMA_ADDR Arnd Bergmann
2017-05-04 9:00 ` Benoît Thébaudeau
2017-05-04 9:37 ` Arnd Bergmann
2017-05-29 8:02 ` Adrian Hunter
2017-05-29 11:12 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5c8c521-c2a7-89bf-8c36-519558079464@intel.com \
--to=adrian.hunter@intel.com \
--cc=benoit@wsystem.com \
--cc=eric@eukrea.com \
--cc=fabio.estevam@nxp.com \
--cc=joancarles@fqingenieria.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®