From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: at_hdmac: remove clear-on-read in atc_dostart()
Date: Fri, 20 Apr 2012 09:40:49 +0200 [thread overview]
Message-ID: <4F911301.9090303@atmel.com> (raw)
In-Reply-To: <1334580390-16303-1-git-send-email-nicolas.ferre@atmel.com>
On 04/16/2012 02:46 PM, Nicolas Ferre :
> This loop on EBCISR register was designed to clear IRQ sources before enabling
> a DMA channel. This register is clear-on-read so a race condition can appear if
> another channel is already active and has just finished its transfer.
> Removing this read on EBCISR is fixing the issue as there is no case where an IRQ
> could be pending: we already make sure that this register is drained at probe()
> time and during resume.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> Cc: stable <stable@vger.kernel.org>
Vinod,
Could you please take this patch as a fix for 3.4-rc?
Thanks, best regards,
> ---
> drivers/dma/at_hdmac.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c
> index 7aa58d2..445fdf8 100644
> --- a/drivers/dma/at_hdmac.c
> +++ b/drivers/dma/at_hdmac.c
> @@ -221,10 +221,6 @@ static void atc_dostart(struct at_dma_chan *atchan, struct at_desc *first)
>
> vdbg_dump_regs(atchan);
>
> - /* clear any pending interrupt */
> - while (dma_readl(atdma, EBCISR))
> - cpu_relax();
> -
> channel_writel(atchan, SADDR, 0);
> channel_writel(atchan, DADDR, 0);
> channel_writel(atchan, CTRLA, 0);
--
Nicolas Ferre
next prev parent reply other threads:[~2012-04-20 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 12:46 [PATCH] dmaengine: at_hdmac: remove clear-on-read in atc_dostart() Nicolas Ferre
2012-04-20 7:40 ` Nicolas Ferre [this message]
2012-04-20 10:15 ` Vinod Koul
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=4F911301.9090303@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).