public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Martin Fuzzey <mfuzzey@parkeon.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-esdhc-imx: Fix SDIO interrupts
Date: Sun, 26 May 2013 13:12:29 -0400	[thread overview]
Message-ID: <877gilsm0y.fsf@octavius.laptop.org> (raw)
In-Reply-To: <20130415150835.7614.98080.stgit@localhost> (Martin Fuzzey's message of "Mon, 15 Apr 2013 17:08:35 +0200")

Hi Martin,

On Mon, Apr 15 2013, Martin Fuzzey wrote:
> Currently SDIO interrupts do not work on i.MX53 and maybe others.
>
> This was observed with a Marvell 8787 based SDIO wifi adapter
> using the mwifiex driver and firmware from the Marvell git
> repository.
> The symptom was a timeout after firmware download.
>
> Observing the SDIO_DAT1 line showed that an interrupt was requested
> (level 0) but no interrupt was generated in software, the line
> stayed low until a timeout ocurred and the card was reset.
>
> There is a Freescale errata
> 	ENGcm11186 "eSDHC misses SDIO interrupt when CINT is disabled"
>
> The workaround suggested by this errata is already implemented and
> involves clearing and then setting the D3CD bit in the host control
> register [see esdhc_writel_le()]
>
> However, when esdhc_writeb_le() is later used to write to
> SDHCI_HOST_CONTROL it always resets the D3CD bit.
>
> To fix this simply add the D3CD bit to the set of bits
> not modified by esdhc_writeb_le().
>
> Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>
> ---
>  drivers/mmc/host/sdhci-esdhc-imx.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c b/drivers/mmc/host/sdhci-esdhc-imx.c
> index 78ac002..3c4c63d 100644
> --- a/drivers/mmc/host/sdhci-esdhc-imx.c
> +++ b/drivers/mmc/host/sdhci-esdhc-imx.c
> @@ -324,8 +324,10 @@ static void esdhc_writeb_le(struct sdhci_host *host, u8 val, int reg)
>  		/*
>  		 * Do not touch buswidth bits here. This is done in
>  		 * esdhc_pltfm_bus_width.
> +		 * Do not touch the D3CD bit either which is used for the
> +		 * SDIO interrupt errata workaround.
>  		 */
> -		mask = 0xffff & ~ESDHC_CTRL_BUSWIDTH_MASK;
> +		mask = 0xffff & ~(ESDHC_CTRL_BUSWIDTH_MASK | ESDHC_CTRL_D3CD);
>  
>  		esdhc_clrset_le(host, mask, new_val, reg);
>  		return;

I didn't see any review comments from other -imx developers -- I've
applied this to mmc-next now, hopefully someone will yell if there's
any reason not to.

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2013-05-26 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 15:08 [PATCH] mmc: sdhci-esdhc-imx: Fix SDIO interrupts Martin Fuzzey
2013-05-26 17:12 ` Chris Ball [this message]

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=877gilsm0y.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mfuzzey@parkeon.com \
    --cc=s.hauer@pengutronix.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