linux-toradex.git/drivers/dma/shdma.c, branch v3.4.2

dmaengine: add context parameter to prep_slave_sg and prep_dma_cyclic

2012-03-21T13:50:23+00:00

Add context parameter to device_prep_slave_sg() and device_prep_dma_cyclic()
interfaces to allow passing client/target specific information associated
with the data transfer.
Modify all affected DMA engine drivers.

Signed-off-by: Alexandre Bounine 
Acked-by: Linus Walleij 
Acked-by: Felipe Balbi 
Signed-off-by: Vinod Koul

dmaengine: ensure all DMA engine drivers initialize their cookies

2012-03-13T06:07:42+00:00

Ensure all DMA engine drivers initialize their cookies in the same way,
so that they all behave in a similar fashion.  This means their first
issued cookie will be 2 rather than 1, and will increment to INT_MAX
before returning 1 and starting over.

In connection with this, Dan Williams said:
> Russell King wrote:
> > Secondly, some DMA engine drivers initialize the dma_chan cookie to 0,
> > others to 1.  Is there a reason for this, or are these all buggy?
>
> I know that ioat and iop-adma expect 0 to mean "I have cleaned up this
> descriptor and it is idle", and would break if zero was an in-flight
> cookie value.  The reserved usage of zero is an driver internal
> concern, but I have no problem formalizing it as a reserved value.

Signed-off-by: Russell King 
Tested-by: Linus Walleij 
Reviewed-by: Linus Walleij 
Acked-by: Jassi Brar 
[imx-sdma.c & mxs-dma.c]
Tested-by: Shawn Guo 
Signed-off-by: Vinod Koul

dmaengine: consolidate tx_status functions

2012-03-13T06:07:14+00:00

Now that we have the completed cookie in the dma_chan structure, we
can consolidate the tx_status functions by providing a function to set
the txstate structure and returning the DMA status.  We also provide
a separate helper to set the residue for cookies which are still in
progress.

Signed-off-by: Russell King 
Tested-by: Linus Walleij 
Reviewed-by: Linus Walleij 
Acked-by: Jassi Brar 
[imx-sdma.c & mxs-dma.c]
Tested-by: Shawn Guo 
Signed-off-by: Vinod Koul

dmaengine: consolidate assignment of DMA cookies

2012-03-13T06:06:52+00:00

Everyone deals with assigning DMA cookies in the same way (it's part of
the API so they should be), so lets consolidate the common code into a
helper function to avoid this duplication.

Signed-off-by: Russell King 
Tested-by: Linus Walleij 
Reviewed-by: Linus Walleij 
Acked-by: Jassi Brar 
[imx-sdma.c & mxs-dma.c]
Tested-by: Shawn Guo 
Signed-off-by: Vinod Koul

dmaengine: add private header file

2012-03-13T06:06:44+00:00

Add a local private header file to contain definitions and declarations
which should only be used by DMA engine drivers.

We also fix linux/dmaengine.h to use LINUX_DMAENGINE_H to guard against
multiple inclusion.

Signed-off-by: Russell King 
Tested-by: Linus Walleij 
Reviewed-by: Linus Walleij 
Acked-by: Jassi Brar 
[imx-sdma.c & mxs-dma.c]
Tested-by: Shawn Guo 
Signed-off-by: Vinod Koul

dmaengine: move last completed cookie into generic dma_chan structure

2012-03-13T06:06:06+00:00

Every DMA engine implementation declares a last completed dma cookie
in their private dma channel structures.  This is pointless, and
forces driver specific code.  Move this out into the common dma_chan
structure.

Signed-off-by: Russell King 
Tested-by: Linus Walleij 
Reviewed-by: Linus Walleij 
Acked-by: Jassi Brar 
[imx-sdma.c & mxs-dma.c]
Tested-by: Shawn Guo 
Signed-off-by: Vinod Koul

dma: sh_dma: not all SH DMAC implementations support MEMCPY

2012-02-01T16:53:53+00:00

Add a flag to allow platforms to specify, whether a DMAC instance supports
the MEMCPY operation. To avoid regressions, preserve the current default.

Signed-off-by: Guennadi Liakhovetski 
Acked-by: Paul Mundt 
Signed-off-by: Vinod Koul

dma: shdma: fix runtime PM: clear channel buffers on reset

2012-01-06T06:10:11+00:00

On platforms, supporting power domains, if the domain, containing a DMAC
instance is powered down, the driver fails to resume correctly. On those
platforms DMAC channels have an additional CHCLR register for clearing
channel buffers. Using this register during runtime resume fixes the
problem.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Vinod Koul

dmaengine: move drivers to dma_transfer_direction

2011-10-27T15:23:43+00:00

fixup usage of dma direction by introducing dma_transfer_direction,
this patch moves dma/drivers/* to use new enum

Cc: Jassi Brar 
Cc: Russell King 
Cc: Viresh Kumar 
Cc: Linus Walleij 
Cc: Nicolas Ferre 
Cc: Mika Westerberg 
Cc: H Hartley Sweeten 
Cc: Li Yang 
Cc: Zhang Wei 
Cc: Sascha Hauer 
Cc: Guennadi Liakhovetski 
Cc: Shawn Guo 
Cc: Yong Wang 
Cc: Tomoya MORINAGA 
Cc: Boojin Kim 
Cc: Barry Song 
Acked-by: Mika Westerberg 
Acked-by: Linus Walleij 
Acked-by: Viresh Kumar 
Acked-by: Nicolas Ferre 
Signed-off-by: Vinod Koul

dma: shdma: transfer based runtime PM

2011-09-28T04:37:40+00:00

Currently the shdma dmaengine driver uses runtime PM to save power, when
no channel on the specific controller is requested by a user. This patch
switches the driver to count individual DMA transfers. That way the
controller can be powered down between transfers, even if some of its
channels are in use.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Vinod Koul