From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] DMA: sun6i: Add driver for the Allwinner A31 DMA controller
Date: Wed, 21 May 2014 16:32:32 +0530 [thread overview]
Message-ID: <20140521110232.GP21128@intel.com> (raw)
In-Reply-To: <20140521085829.GP27329@lukather>
On Wed, May 21, 2014 at 10:58:29AM +0200, Maxime Ripard wrote:
> On Wed, May 21, 2014 at 11:01:05AM +0530, Vinod Koul wrote:
> > On Tue, May 13, 2014 at 03:42:58PM +0200, Maxime Ripard wrote:
> > > Hi Vinod,
> > >
> > > On Wed, Apr 30, 2014 at 12:34:08PM +0530, Vinod Koul wrote:
> > > > > +
> > > > > +static int sun6i_dma_terminate_all(struct sun6i_vchan *vchan)
> > > > > +{
> > > > > + struct sun6i_dma_dev *sdev = to_sun6i_dma_dev(vchan->vc.chan.device);
> > > > > + struct sun6i_pchan *pchan = vchan->phy;
> > > > > + unsigned long flags;
> > > > > + LIST_HEAD(head);
> > > > > +
> > > > > + spin_lock(&sdev->lock);
> > > > > + list_del_init(&vchan->node);
> > > > > + spin_unlock(&sdev->lock);
> > > > > +
> > > > > + spin_lock_irqsave(&vchan->vc.lock, flags);
> > > > > +
> > > > > + vchan_get_all_descriptors(&vchan->vc, &head);
> > > > > +
> > > > > + if (pchan) {
> > > > > + writel(DMA_CHAN_ENABLE_STOP, pchan->base + DMA_CHAN_ENABLE);
> > > > > + writel(DMA_CHAN_PAUSE_RESUME, pchan->base + DMA_CHAN_PAUSE);
> > > > > +
> > > > > + vchan->phy = NULL;
> > > > > + pchan->vchan = NULL;
> > > > > + pchan->desc = NULL;
> > > > > + pchan->done = NULL;
> > > > > + }
> > > > > +
> > > > > + spin_unlock_irqrestore(&vchan->vc.lock, flags);
> > > > > +
> > > > > + vchan_dma_desc_free_list(&vchan->vc, &head);
> > > >
> > > > shouldn't you kill the tasklet as well here?
> > >
> > > Just to be clear, which tasklet? vchan's or the driver's?
> > You need to take care of both. But I suspect if we ensure irq is not triggered
> > and any pending ones are completed you can simply kill both of the tasklets
> > happily. See the fixes merged in dmaengine last cycle (hint: patchlog shows what
> > we need to do)
>
> I still don't get why I should kill the driver tasklet in terminate_all.
>
> The tasklet is common to all the channels, if you kill it, you'll
> prevent it from scheduling while other channels might have had a need
> for it to actually run.
I think I was under the impression that your tasklet is per channel, If that is
not the case it makes no sense then for this case
>
> About the commits themselves, I guess you talk about 9068b032 and
> ccc7aad0. Both these commits only fix the remove path, not the
> terminate_all one, and both these drivers are not doing anything
> related to the tasklet in terminate_all.
Yup as you would have noticed these were not per channel as well
>
> > Btw just noticed, you *should* use dmaengine: as the subsytem name on the patch
> > series...
>
> Ok, I will.
Thanks
--
~Vinod
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/3beb68fa/attachment.sig>
next prev parent reply other threads:[~2014-05-21 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:22 [PATCH v7] Add support for the Allwinner A31 DMA Controller Maxime Ripard
2014-04-24 14:22 ` [PATCH v7] DMA: sun6i: Add driver for the Allwinner A31 DMA controller Maxime Ripard
2014-04-30 7:04 ` Vinod Koul
2014-04-30 21:53 ` Maxime Ripard
2014-05-02 16:34 ` Vinod Koul
2014-05-08 3:19 ` Maxime Ripard
2014-05-21 5:29 ` Vinod Koul
2014-05-13 13:42 ` Maxime Ripard
2014-05-21 5:31 ` Vinod Koul
2014-05-21 8:58 ` Maxime Ripard
2014-05-21 11:02 ` Vinod Koul [this message]
2014-05-20 12:40 ` [linux-sunxi] " Emilio López
2014-05-20 12:52 ` Shevchenko, Andriy
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=20140521110232.GP21128@intel.com \
--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).