Re: [PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers
On Thu, Feb 27, 2014 at 10:44:39AM +0530, George Cherian wrote: > Warinings are seen after ISOCH transfers, during channel tear down. > This is mainly beacause we handle ISOCH differently as compared to > other transfers. > > Patch 1: make sure we do channel tear down only if channel is busy. >If not the tear down will never succeed. > > Patch 2: ISOCH completions are done differently, so this might lead to > reprogram of dma channel on which already a teardown is done. Applied, Thanks -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers
On Thu, Feb 27, 2014 at 10:44:39AM +0530, George Cherian wrote: Warinings are seen after ISOCH transfers, during channel tear down. This is mainly beacause we handle ISOCH differently as compared to other transfers. Patch 1: make sure we do channel tear down only if channel is busy. If not the tear down will never succeed. Patch 2: ISOCH completions are done differently, so this might lead to reprogram of dma channel on which already a teardown is done. Applied, Thanks -- ~Vinod -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers
Warinings are seen after ISOCH transfers, during channel tear down. This is mainly beacause we handle ISOCH differently as compared to other transfers. Patch 1: make sure we do channel tear down only if channel is busy. If not the tear down will never succeed. Patch 2: ISOCH completions are done differently, so this might lead to reprogram of dma channel on which already a teardown is done. George Cherian (2): dma: cppi41: start tear down only if channel is busy usb: musb: musb_cppi41: Dont reprogram DMA if tear down is initiated drivers/dma/cppi41.c | 7 +-- drivers/usb/musb/musb_cppi41.c | 3 ++- 2 files changed, 7 insertions(+), 3 deletions(-) -- 1.8.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/2] Fix CPPI Warnings during tear down after ISOCH transfers
Warinings are seen after ISOCH transfers, during channel tear down. This is mainly beacause we handle ISOCH differently as compared to other transfers. Patch 1: make sure we do channel tear down only if channel is busy. If not the tear down will never succeed. Patch 2: ISOCH completions are done differently, so this might lead to reprogram of dma channel on which already a teardown is done. George Cherian (2): dma: cppi41: start tear down only if channel is busy usb: musb: musb_cppi41: Dont reprogram DMA if tear down is initiated drivers/dma/cppi41.c | 7 +-- drivers/usb/musb/musb_cppi41.c | 3 ++- 2 files changed, 7 insertions(+), 3 deletions(-) -- 1.8.1 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
