Re: [PATCH] dmaengine: tegra: add slave capabilities reporting

2015-01-13 Thread Vinod Koul
On Tue, Jan 06, 2015 at 06:44:56AM +, Paul Walmsley wrote: > > After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add > a warning for drivers not using the generic slave caps retrieval"), > the Tegra APB DMA driver causes this warning during boot: > > WARNING: CPU: 0 PID: 1 at

Re: [PATCH] dmaengine: tegra: add slave capabilities reporting

2015-01-08 Thread Maxime Ripard
On Tue, Jan 06, 2015 at 06:44:56AM +, Paul Walmsley wrote: > > After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add > a warning for drivers not using the generic slave caps retrieval"), > the Tegra APB DMA driver causes this warning during boot: > > WARNING: CPU: 0 PID: 1 at

Re: [PATCH] dmaengine: tegra: add slave capabilities reporting

2015-01-06 Thread Thierry Reding
On Tue, Jan 06, 2015 at 06:44:56AM +, Paul Walmsley wrote: > > After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add > a warning for drivers not using the generic slave caps retrieval"), > the Tegra APB DMA driver causes this warning during boot: > > WARNING: CPU: 0 PID: 1 at

[PATCH] dmaengine: tegra: add slave capabilities reporting

2015-01-05 Thread Paul Walmsley
After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add a warning for drivers not using the generic slave caps retrieval"), the Tegra APB DMA driver causes this warning during boot: WARNING: CPU: 0 PID: 1 at drivers/dma/dmaengine.c:830 dma_async_device_register+0x294/0x538() this