linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] dma: Add Xilinx zynqmp dma engine driver support
Date: Sun, 23 Aug 2015 19:38:23 +0530	[thread overview]
Message-ID: <20150823140823.GA13546@localhost> (raw)
In-Reply-To: <CAGnW=BaU__+B2uAK=qpV3QP60SqSUxx-kgJVs0t42K0fqTxL0g@mail.gmail.com>

On Thu, Aug 20, 2015 at 12:01:27PM +0530, punnaiah choudary kalluri wrote:
> On Thu, Aug 20, 2015 at 11:43 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Thu, Aug 06, 2015 at 08:49:33AM +0530, Punnaiah Choudary Kalluri wrote:
> >
> >> +     list_for_each_entry_safe(desc, next, &chan->done_list, node) {
> >> +             dma_async_tx_callback callback;
> >> +             void *callback_param;
> >> +
> >> +             list_del(&desc->node);
> >> +
> >> +             callback = desc->async_tx.callback;
> >> +             callback_param = desc->async_tx.callback_param;
> >> +             if (callback) {
> >> +                     if (in_interrupt())
> >> +                             spin_unlock_bh(&chan->lock);
> >> +                     else
> >> +                             spin_unlock(&chan->lock);
> >
> > This looks bad!
> > Why would callback be called from different context. It should only be
> > invoked from your tasklet
> 
> During the terminate call, driver need to clean up the existing BDs so that time
> this function will be called from the thread or process context in
> addition to the
> tasklet context.
> 
> DO you have any suggestion here ?

Yes you need to terminate but you don't need to invoke user for terminate
flow. It is not expected.
Terminate flow expect youu to clean the channels

-- 
~Vinod

  reply	other threads:[~2015-08-23 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  3:19 [PATCH v4 1/2] Documentation: dt: Add Xilinx zynqmp dma device tree binding documentation Punnaiah Choudary Kalluri
2015-08-06  3:19 ` [PATCH v4 2/2] dma: Add Xilinx zynqmp dma engine driver support Punnaiah Choudary Kalluri
2015-08-20  6:13   ` Vinod Koul
2015-08-20  6:31     ` punnaiah choudary kalluri
2015-08-23 14:08       ` Vinod Koul [this message]
2015-08-23 14:54         ` punnaiah choudary kalluri
2015-08-20  5:52 ` [PATCH v4 1/2] Documentation: dt: Add Xilinx zynqmp dma device tree binding documentation Vinod Koul
2015-08-20  6:11   ` punnaiah choudary kalluri
2015-08-20  6:18     ` Vinod Koul
2015-08-20  6:20       ` Michal Simek
2015-08-21 16:42 ` Moritz Fischer
2015-08-22 10:47   ` punnaiah choudary kalluri
2015-08-24 13:47 ` Lars-Peter Clausen
2015-08-24 18:39   ` punnaiah choudary kalluri
2015-08-24 18:53 ` Rob Herring
2015-08-25  6:46   ` punnaiah choudary kalluri
2015-08-31  3:37     ` punnaiah choudary kalluri

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=20150823140823.GA13546@localhost \
    --to=vinod.koul@intel.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).