linux.git/include/sound/dmaengine_pcm.h, branch v3.13.3

ASoC: dmaengine: Support custom channel names

2013-10-24T08:52:14+00:00

Some devices have more than just simple TX and RX DMA channels, for example
modern Samsung I2S IPs support a secondary transmit DMA stream which is
mixed into the primary stream during playback. Allow such devices to
specify the names of the channels to be requested in their dma_data.

Signed-off-by: Mark Brown 
Acked-by: Lars-Peter Clausen

ASoC: dmaengine-pcm: Add support for querying DMA capabilities

2013-10-19T20:26:06+00:00

Currently each platform making use the the generic dmaengine PCM driver still
needs to provide a custom snd_pcm_hardware struct which specifies the
capabilities of the DMA controller, e.g. the maximum period size that can be
supported. This patch adds code which uses the newly introduced
dma_get_slave_caps() API to query this information from the dmaengine driver.
The new code path will only be taken if the 'pcm_hardware' field of the
snd_dmaengine_pcm_config struct is NULL.

The patch also introduces a new 'fifo_size' field to the
snd_dmaengine_dai_dma_data struct which is used to initialize the
snd_pcm_hardware 'fifo_size' field and needs to be set by the DAI driver.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Mark Brown

ASoC: generic-dmaengine-pcm: Add support for half-duplex

2013-04-22T10:27:04+00:00

Some platforms which are half-duplex share the same DMA channel between the
playback and capture stream. Add support for this to the generic dmaengine PCM
driver.

Signed-off-by: Lars-Peter Clausen 
Tested-by: Shawn Guo 
Signed-off-by: Mark Brown

ASoC: ux500: Use generic dmaengine PCM

2013-04-18T14:04:44+00:00

Use the generic dmaengine PCM driver instead of a custom implemention.  There is
a minor functional change, the ux500 PCM driver did not preallocate the audio
buffer, while the generic dmaengine PCM driver will do this.

Signed-off-by: Lars-Peter Clausen 
Acked-by: Lee Jones 
Signed-off-by: Mark Brown

ASoC: dmaengine-pcm: Add support for platforms which can't report residue

2013-04-17T13:25:56+00:00

Unfortunately there are still quite a few platforms with a dmaengine driver
which do not support reporting the number of bytes left to transfer. If we want
to support these platforms in the generic dmaengine PCM driver we have.

Signed-off-by: Lars-Peter Clausen 
Tested-by: Stephen Warren 
Tested-by: Shawn Guo 
Signed-off-by: Mark Brown

ASoC: dmaengine_pcm: Add support for compat platforms

2013-04-17T13:21:36+00:00

Add support for platforms which don't use devicetree yet or have to optionally
support a non-devicetree way to request the DMA channel. The patch adds the
compat_request_channel and compat_filter_fn callbacks to the
snd_dmaengine_pcm_config struct. If the compat_request_channel is implemented it
will be used to request the DMA channel. If not dma_request_channel with
compat_filter_fn as the filter function will be used to request the channel.

The patch also exports the snd_dmaengine_pcm_request_chan() function, since
compat platforms will want to use it to request their DMA channel.

Signed-off-by: Lars-Peter Clausen 
Tested-by: Stephen Warren 
Tested-by: Shawn Guo 
Signed-off-by: Mark Brown

ASoC: Add a generic dmaengine_pcm driver

2013-04-17T13:21:25+00:00

This patch adds a generic dmaengine PCM driver. It builds on top of the
dmaengine PCM library and adds the missing pieces like DMA channel management,
buffer management and channel configuration. It will be able to replace the
majority of the existing platform specific dmaengine based PCM drivers.
Devicetree is used to map the DMA channels to the PCM device.

Signed-off-by: Lars-Peter Clausen 
Tested-by: Stephen Warren 
Tested-by: Shawn Guo 
Signed-off-by: Mark Brown

ASoC: dmaengine-pcm: Make requesting the DMA channel at PCM open optional

2013-04-17T13:17:54+00:00

Refactor the dmaengine PCM library to allow the DMA channel to be requested
before opening a PCM substream. snd_dmaengine_pcm_open() now expects a DMA
channel instead of a filter function and filter parameter as its parameters.
snd_dmaengine_pcm_close() is updated to not release the DMA channel. This allows
a dmaengine based PCM driver to request its channels before the substream is
opened.

The patch also introduces two new functions, snd_dmaengine_pcm_open_request_chan()
and snd_dmaengine_pcm_close_release_chan(), which have the same signature and
behaviour of the old snd_dmaengine_pcm_{open,close}() and internally use the new
variants of these functions. All users of snd_dmaengine_pcm_{open,close}() are
updated to use snd_dmaengine_pcm_open_request_chan() and
snd_dmaengine_pcm_close_release_chan().

Signed-off-by: Lars-Peter Clausen 
Tested-by: Stephen Warren 
Tested-by: Shawn Guo 
Signed-off-by: Mark Brown

ASoC: dmaengine-pcm: Add a common DAI DMA data struct

2013-04-03T17:12:33+00:00

This patch adds a common DMA data struct which can be used by DAI drivers to
communicate their DMA configuration requirements to the DMA pcm driver.  Having
a common data structure for this allows us to implement common functions on top
of them, which can be used by multiple platforms.

This patch also introduces a new function to initialize certain fields of a
dma_slave_config struct from the common DAI DMA data struct.

Signed-off-by: Lars-Peter Clausen 
Reviewed-by: Stephen Warren 
Tested-by: Stephen Warren 
Signed-off-by: Mark Brown

ASoC: dmaengine-pcm: Remove snd_dmaengine_pcm_{set,get}_data

2013-03-26T14:18:01+00:00

These functions were initially added to be able to support some oddball dma
drivers, but all users have been updated to deal with the situation without the
help of snd_dmaengine_pcm_{set,get}_data, so these two functions can be removed.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Mark Brown