linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: rcar-dmac: Wait for IRQs completion when freeing channel
Date: Thu, 08 Oct 2015 14:22:01 +0000	[thread overview]
Message-ID: <2421567.ZFdiTCl9SH@avalon> (raw)
In-Reply-To: <1442233573-26684-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Vinod,

On Monday 05 October 2015 15:11:55 Vinod Koul wrote:
> On Tue, Sep 15, 2015 at 12:11:33AM +0000, Kuninori Morimoto wrote:
> > Hi Laurent
> > 
> > > When freeing channel resources we need to ensure that no IRQ will occur
> > > for the given channel. In order to do so the driver stops the hardware,
> > > but an IRQ handler could still be running, especially given that the
> > > channel IRQ is threaded. Fix it by waiting for pending IRQs completion
> > > with synchronize_irq()
> > > 
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> > > ---
> > > 
> > >  drivers/dma/sh/rcar-dmac.c | 37 +++++++++++++++++++------------------
> > >  1 file changed, 19 insertions(+), 18 deletions(-)
> > > 
> > > Hi Morimoto-san,
> > > 
> > > This patch is compile-tested only. Would you be able to check if it
> > > fixes the issue you've reported with SDHI and rcar-dmac ?
> > 
> > Thanks. I will ask to BSP team
> 
> Patch looks okay, but if we get this confirmation it would be great.

I've just received a report that the patch has been successfully tested to get 
rid of the oops, but it introduced another issue in that synchronize_irq() 
gets called from non-sleeptable context through terminate_all(). 

The DMA engine API states that

   * device_terminate_all
     - Aborts all the pending and ongoing transfers on the channel
     - This command should operate synchronously on the channel,
       terminating right away all the channels

I wonder how to interpret "synchronously" here, should terminate_all() wait 
for termination to be complete ? In that case it wouldn't be valid to call it 
from non-sleepable context.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2015-10-08 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 12:26 [PATCH] dmaengine: rcar-dmac: Wait for IRQs completion when freeing channel Laurent Pinchart
2015-09-15  0:11 ` Kuninori Morimoto
2015-10-05 14:11 ` Vinod Koul
2015-10-08 14:22 ` Laurent Pinchart [this message]
2015-10-08 14:51 ` Lars-Peter Clausen
2015-10-14 10:47 ` Vinod Koul
2015-10-14 11:02 ` Lars-Peter Clausen
2015-10-15  3:52 ` Vinod Koul
2015-10-15  7:35 ` Lars-Peter Clausen
2015-10-15 17:04 ` Laurent Pinchart
2015-10-15 17:09 ` Laurent Pinchart
2015-10-15 17:15 ` Lars-Peter Clausen
2015-10-16 13:47 ` Lars-Peter Clausen

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=2421567.ZFdiTCl9SH@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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).