On Mon, May 13, 2013 at 10:20:36AM -0600, Stephen Warren wrote: > On 05/11/2013 10:30 AM, Dmitry Osipenko wrote: > > Lock scenario: Channel 1 was allocated and prepared as slave_sg, used and freed. > > Now preparation of cyclic dma on channel 1 will fail with err "DMA configuration > > conflict" because tdc->isr_handler still setted to handle_once_dma_done. > > > > This happens because tegra_dma_abort_all() won't be called on channel freeing > > if pending list is empty and channel not busy. We need to clear isr_handler > > on channel freeing to avoid locking. > ... > > Reposting with dma maintainers cc'd as suggested by Stephen. > > Added Stephen's ack. Applied, both thanks > > Just for reference (not need to repost again): You'd usually send the > messages *to* the DMA maintainers since they will be taking the patches > through their tree, and then Ccing anyone else. get_maintainer.pl is your friend for this -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
