dmaengine: mv_xor: remove support for dmacap,* DT properties
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Wed, 8 Jul 2015 14:28:16 +0000 (16:28 +0200)
committerVinod Koul <vinod.koul@intel.com>
Wed, 19 Aug 2015 17:01:53 +0000 (22:31 +0530)
commit6d8f7abd235c1a38629cdada49cc53992f4ad42e
tree68b85daa1cc0640517525c1922e84e3081e068a8
parent31495d60a06524f37a9ea66d7d62ce0418ef3506
dmaengine: mv_xor: remove support for dmacap,* DT properties

The only reason why we had dmacap,* properties is because back when
DMA_MEMSET was supported, only one out of the two channels per engine
could do a memset operation. But this is something that the driver
already knows anyway, and since then, the DMA_MEMSET support has been
removed.

The driver is already well aware of what each channel supports and the
one to one mapping between Linux specific implementation details (such
as dmacap,interrupt enabling DMA_INTERRUPT) and DT properties is a
good indication that these DT properties are wrong.

Therefore, this commit simply gets rid of these dmacap,* properties,
they are now ignored, and the driver is responsible for knowing the
capabilities of the hardware with regard to the dmaengine subsystem
expectations.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Documentation/devicetree/bindings/dma/mv-xor.txt
drivers/dma/mv_xor.c