Re: dma_request_slave_channel_reason vs dma_release_channel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/02/2014 06:12 PM, Lars-Peter Clausen wrote:
On 11/26/2014 09:26 PM, Julian Scheel wrote:
This allows two conclusion:
(a) dma_request_slave_channel and dma_request_slave_channel_reason shall
increase the privatecnt just like __dma_request_channel does.
(b) dma_release_channel must not be used for channels which have not been
acquired via __dma_request_channel.

dma_get_any_slave_channel() should behave the same as
__dma_request_channel() in this regard. Best is to probably factor it
out into a helper function dma_get_private_chan() or similar that can be
used by both of the functions.

Thank you for clarification. Patch will follow.
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux PCI]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux