From: Guennadi Liakhovetski <g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
To: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Shevchenko,
Andriy"
<andriy.shevchenko-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Phil Edworthy
<phil.edworthy-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [PATCH v4 2/2] dmaengine: add a driver for AMBA AXI NBPF DMAC IP cores
Date: Wed, 30 Jul 2014 23:23:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1407302319460.21427@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.1407281634150.32592-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
Hi Vinod,
On Mon, 28 Jul 2014, Guennadi Liakhovetski wrote:
> > Looking at the code again, I think we need to free irq (you can call
> > devm_free_irq()) and call syncronize_irq so that anything pending is
> > flushed. So if you can send follow up patch doing these in .remove, we can
> > merge these
>
> This is a nice offer, thanks! But to accept it I'd like to understand: why
> do you think we need that? In my previous email I presented to you a
> theoretical and improbable race situation, that I can foresee. You erased
> it in your reply, but it was dealing with the
> .device_free_chan_resources() method, so, your suspected race is a
> different one. Could you please explain to me, why do you think interrupts
> are possible during .release()? Aren't all channels guaranteed to have
> been freed by that time?
It would be great to get an explanation for your comment, please? How can
interrupts come after all channels have been freed? Or how can .release()
be called while some channels are still in use?
Thanks
Guennadi
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-30 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 10:48 [PATCH v4 1/2] dmaengine: add device tree binding documentation for the nbpfaxi driver Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407191239400.3062-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-07-19 10:48 ` [PATCH v4 2/2] dmaengine: add a driver for AMBA AXI NBPF DMAC IP cores Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407191243360.3062-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-07-25 14:16 ` Vinod Koul
[not found] ` <20140725141621.GT8181-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-25 15:00 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407251635070.13523-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-07-25 16:34 ` Vinod Koul
[not found] ` <20140725163417.GV8181-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-26 19:32 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407262105150.24257-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-07-28 14:25 ` Vinod Koul
[not found] ` <20140728142510.GF8181-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-28 14:42 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407281634150.32592-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-07-30 21:23 ` Guennadi Liakhovetski [this message]
2014-07-31 12:57 ` Vinod Koul
[not found] ` <20140731125704.GV8181-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-31 13:42 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1407311520290.24081-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-08-01 16:34 ` Vinod Koul
[not found] ` <20140801163456.GZ8181-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-08-01 21:04 ` Guennadi Liakhovetski
[not found] ` <alpine.DEB.2.00.1408012300270.4784-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2014-08-04 7:55 ` Vinod Koul
2014-08-04 8:08 ` [PATCH v4 1/2] dmaengine: add device tree binding documentation for the nbpfaxi driver 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=Pine.LNX.4.64.1407302319460.21427@axis700.grange \
--to=g.liakhovetski-mmb7mzphnfy@public.gmane.org \
--cc=andriy.shevchenko-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=phil.edworthy-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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