29 Jul, 2016
1 commit
-
Pull dmaengine updates from Vinod Koul:
"This time we have bit of largish changes: two new drivers, bunch of
updates and cleanups to existing set. Nothing super exciting though.New drivers:
- Xilinx zynqmp dma engine driver
- Marvell xor2 driverUpdates:
- dmatest sg support
- updates and enhancements to Xilinx drivers, adding of cyclic mode
- clock handling fixes across drivers
- removal of OOM messages on kzalloc across subsystem
- interleaved transfers support in omap driver
- runtime pm support in qcom bam dma
- tasklet kill freeup across drivers
- irq cleanup on remove across drivers"* tag 'dmaengine-4.8-rc1' of git://git.infradead.org/users/vkoul/slave-dma: (94 commits)
dmaengine: k3dma: add missing clk_disable_unprepare() on error in k3_dma_probe()
dmaengine: zynqmp_dma: add missing MODULE_LICENSE
dmaengine: qcom_hidma: use for_each_matching_node() macro
dmaengine: zynqmp_dma: Fix static checker warning
dmaengine: omap-dma: Support for interleaved transfer
dmaengine: ioat: statify symbol
dmaengine: pxa_dma: implement device_synchronize
dmaengine: imx-sdma: remove assignment never used
dmaengine: imx-sdma: remove dummy assignment
dmaengine: cppi: remove unused and bogus check
dmaengine: qcom_hidma_lli: kill the tasklets upon exit
dmaengine: pxa_dma: remove owner assignment
dmaengine: fsl_raid: remove owner assignment
dmaengine: coh901318: remove owner assignment
dmaengine: qcom_hidma: kill the tasklets upon exit
dmaengine: txx9dmac: explicitly freeup irq
dmaengine: sirf-dma: kill the tasklets upon exit
dmaengine: s3c24xx: kill the tasklets upon exit
dmaengine: s3c24xx: explicitly freeup irq
dmaengine: pl330: explicitly freeup irq
...
28 Jul, 2016
1 commit
24 Jul, 2016
5 commits
-
Add the missing clk_disable_unprepare() before return
from k3_dma_probe() in the error handling case.Signed-off-by: Wei Yongjun
Signed-off-by: Vinod Koul -
We get a warning about the missing MODULE_LICENSE tag for this newly
added driver module:WARNING: modpost: missing MODULE_LICENSE() in drivers/dma/xilinx/zynqmp_dma.o
see include/linux/module.h for more informationThis adds a "GPL" license, matching the "version 2 or later" information in
the comment at the start of the file.Signed-off-by: Arnd Bergmann
Acked-by: Kedareswara rao Appana
Signed-off-by: Vinod Koul -
Use for_each_matching_node() macro instead of open coding it.
Signed-off-by: Wei Yongjun
Acked-by: Sinan Kaya
Signed-off-by: Vinod Koul -
This patch fixes the below static checker warning
drivers/dma/xilinx/zynqmp_dma.c:973 zynqmp_dma_chan_probe()
warn: was && intended here instead of ||?Reported-by: Dan Carpenter
Signed-off-by: Kedareswara rao Appana
Signed-off-by: Vinod Koul -
Initial support for interleaved transfer with sDMA.
The implementation only supports DMA_MEM_TO_MEM and frame_size must be 1.
sDMA needs to be configured for double indexing when ICG is needed.Signed-off-by: Peter Ujfalusi
Signed-off-by: Vinod Koul
23 Jul, 2016
14 commits
-
Sparse warns:
drivers/dma/ioat/init.c:1215:6: warning: symbol 'ioat_resume' was not declared. Should it be static?Signed-off-by: Vinod Koul
Acked-by: Dave Jiang -
Implement the function which wait until a dma channel is stopped to have
a synchronization point.This also protects the pxad_remove() from races, such as spurious
interrupts while removing the driver, because :
- as long as there is one dma channel requested, ie. dma_chan_get() but
no dma_chan_put(), the try_module_get() of dma_chan_get() prevents
the remove() routine from running
- when the last channel is released, ie. the last dma_chan_put() is
called, if there is a running DMA, pxad_synchronize() is called
- pxad_synchronize() waits for the channel to stop, which in turn
ensures on pxa architecture that the interrupt cannot be fired anymoreReported-by: Vinod Koul
Signed-off-by: Robert Jarzmik
Signed-off-by: Vinod Koul -
David reported:
[drivers/dma/imx-sdma.c:769]: (style) Variable 'emi_2_emi' is assigned a value that is never usedSince emi_2_emi is never used afterwards, remove thsi as well
Reported-by: David Binderman
Cc: Sascha Hauer
Cc: Fabio Estevam
Signed-off-by: Vinod Koul -
David reported:
drivers/dma/imx-sdma.c:1003]: (style) Same expression on both sides of '|='ORing with itself yields same result, So remove this
Reported-by: David Binderman
Cc: Sascha Hauer
Cc: Fabio Estevam
Signed-off-by: Vinod Koul -
In cppi41_dma_prep_slave_sg() variable num is initialized to zero, but never
updated and a BUG_ON is checked for it being greater than zero which will be
always false.Remove the bogus check and this variable
Reported-by: David Binderman
Signed-off-by: Vinod Koul -
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Cc: Sinan Kaya -
debugfs file operations owner is set by core, so remove
Signed-off-by: Vinod Koul
Acked-by: Robert Jarzmik -
platform driver operations owner is set by core, so remove
Signed-off-by: Vinod Koul
Cc: Xuelin Shi -
debugfs file operations owner is set by core, so remove
Signed-off-by: Vinod Koul
Cc: Linus Walleij -
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Acked-by: Sinan Kaya -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
-
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Cc: Barry Song -
drivers should ensure that tasklets are killed, so that they can't be
executed after driver remove is executed, so ensure they are killed.This driver used vchan tasklets, so those need to be killed.
Signed-off-by: Vinod Koul
Reviewed-by: Krzysztof Kozlowski -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Reviewed-by: Krzysztof Kozlowski
16 Jul, 2016
19 commits
-
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Cc: Jassi Brar
Cc: Linus Walleij -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Acked-by: Peter Ujfalusi -
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Cc: Mario Six -
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Cc: Guennadi Liakhovetski -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Cc: Guennadi Liakhovetski -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Cc: Jonas Jensen -
Sparse complains:
drivers/dma/mmp_tdma.c:407:22: warning: symbol 'mmp_tdma_alloc_descriptor' was not declared. Should it be static?
drivers/dma/mmp_tdma.c:595:17: warning: symbol 'mmp_tdma_xlate' was not declared. Should it be static?Signed-off-by: Vinod Koul
Cc: Qiao Zhou -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Acked-by: Zhangfei Gao -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Acked-by: Zhangfei Gao -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Cc: Sascha Hauer
Cc: Fabio Estevam -
imxdma_probe function starting brace is wrongly indented, so fix that
Signed-off-by: Vinod Koul
Cc: Sascha Hauer
Cc: Linus Walleij -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
-
drivers should ensure that tasklets are killed, so that they can't be
executed after driver remove is executed, so ensure they are killed.This driver used vchan tasklets, so those need to be killed.
Signed-off-by: Vinod Koul
Cc: Jingchang Lu
Cc: Peter Griffin -
drivers should ensure that tasklets are killed, so that they can't be
executed after driver remove is executed, so ensure they are killed.This driver used vchan tasklets, so those need to be killed.
Signed-off-by: Vinod Koul
Acked-by: Lars-Peter Clausen -
size_t should be printed with %zu, not %lu as driver did, so fix these
warning by doing this changedrivers/dma/fsl_raid.c: In function 'fsl_re_prep_dma_genq':
drivers/dma/fsl_raid.c:341:4: warning: format '%lu' expects argument of type
'long unsigned int', but argument 3 has type 'size_t' [-Wformat=]
len, FSL_RE_MAX_DATA_LEN);
^
drivers/dma/fsl_raid.c: In function 'fsl_re_prep_dma_pq':
drivers/dma/fsl_raid.c:428:4: warning: format '%lu' expects argument of type
'long unsigned int', but argument 3 has type 'size_t' [-Wformat=]
len, FSL_RE_MAX_DATA_LEN);
^
drivers/dma/fsl_raid.c: In function 'fsl_re_prep_dma_memcpy':
drivers/dma/fsl_raid.c:549:4: warning: format '%lu' expects argument of type
'long unsigned int', but argument 3 has type 'size_t' [-Wformat=]
len, FSL_RE_MAX_DATA_LEN);
^Signed-off-by: Vinod Koul
-
drivers should ensure that tasklets are killed, so that they can't be
run after driver remove is executedSigned-off-by: Vinod Koul
Cc: Xuelin Shi -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Cc: Jingchang Lu
Cc: Peter Griffin -
drivers should ensure that tasklets are killed, so that they can't be
executed after driver remove is executed, so ensure they are killed.This driver used vchan tasklets, so those need to be killed.
Signed-off-by: Vinod Koul
Acked-by: Peter Ujfalusi -
dmaengine device should explicitly call devm_free_irq() when using
devm_request_irq().The irq is still ON when devices remove is executed and irq should be
quiesced before remove is completed.Signed-off-by: Vinod Koul
Acked-by: Peter Ujfalusi