From: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, yusuke.goda.sx@renesas.com,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Paul Mundt <lethal@linux-sh.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
koba@kmckk.co.jp
Subject: Re: [PATCH] mmc: sh-mmcif: properly handle MMC_WRITE_MULTIPLE_BLOCK completion IRQ
Date: Wed, 19 Sep 2012 02:50:17 +0000 [thread overview]
Message-ID: <505932E9.8050202@kmckk.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.64.1209190105080.31203@axis700.grange>
(2012/09/19 8:10), Guennadi Liakhovetski wrote:
> Upon completion of a MMC_WRITE_MULTIPLE_BLOCK command MMCIF issues an IRQ
> with the DTRANE bit set and often with one or several of CMD12 bits set.
> If those interrupts are not acknowledged, an additional interrupt can be
> produced and will be delivered later, possibly, when the transaction has
> already been completed. To prevent this from happening, CMD12 completion
> interrupt sources have to be cleared too upon reception of an DTRANE IRQ.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
>
> Tested on kzm9g and mackerel. Kobayashi-san, this fixes spurious
> interrupts, that you are observing.
I verified on kzm9g.
This works with
[PATCH] mmc: sh-mmcif: avoid Oops on spurious interrupts
Tested-by: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
>
> drivers/mmc/host/sh_mmcif.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
> index 82bf921..387bf63 100644
> --- a/drivers/mmc/host/sh_mmcif.c
> +++ b/drivers/mmc/host/sh_mmcif.c
> @@ -1213,7 +1213,9 @@ static irqreturn_t sh_mmcif_intr(int irq, void *dev_id)
> sh_mmcif_writel(host->addr, MMCIF_CE_INT, ~INT_BUFRE);
> sh_mmcif_bitclr(host, MMCIF_CE_INT_MASK, MASK_MBUFRE);
> } else if (state & INT_DTRANE) {
> - sh_mmcif_writel(host->addr, MMCIF_CE_INT, ~INT_DTRANE);
> + sh_mmcif_writel(host->addr, MMCIF_CE_INT,
> + ~(INT_CMD12DRE | INT_CMD12RBE |
> + INT_CMD12CRE | INT_DTRANE));
> sh_mmcif_bitclr(host, MMCIF_CE_INT_MASK, MASK_MDTRANE);
> } else if (state & INT_CMD12RBE) {
> sh_mmcif_writel(host->addr, MMCIF_CE_INT,
>
next prev parent reply other threads:[~2012-09-19 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:10 [PATCH] mmc: sh-mmcif: properly handle MMC_WRITE_MULTIPLE_BLOCK completion IRQ Guennadi Liakhovetski
2012-09-19 2:50 ` Tetsuyuki Kobayashi [this message]
2012-09-19 6:25 ` Chris Ball
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=505932E9.8050202@kmckk.co.jp \
--to=koba@kmckk.co.jp \
--cc=g.liakhovetski@gmx.de \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yusuke.goda.sx@renesas.com \
/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