diff options
| author | Peter Ujfalusi <peter.ujfalusi@ti.com> | 2012-09-14 15:05:52 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2012-09-22 11:12:59 -0400 |
| commit | 03945e99a8ac4f596dad9a679816e5b4bb77e5d2 (patch) | |
| tree | 51f73408c4f3eefdfd6be05f776ee497beda92da /COPYING | |
| parent | 061fb36db7c0187aa90b95f1ba56f6192f42b984 (diff) | |
| download | talos-op-linux-03945e99a8ac4f596dad9a679816e5b4bb77e5d2.tar.gz talos-op-linux-03945e99a8ac4f596dad9a679816e5b4bb77e5d2.zip | |
ASoC: omap-pcm: Prepare to configure the DMA data_type based on stream properties
Based on the format of the stream the omap-pcm can decide alone what data
type should be used with by the sDMA.
Keep the possibility for OMAP dai drivers to tell omap-pcm if they want to
use different data type. This is needed for the omap-hdmi for example which
needs 32bit data type even if the stream format is S16_LE.
The check if (dma_data->data_type) is safe at the moment since omap-pcm
does not support 8bit samples (OMAP_DMA_DATA_TYPE_S8 == 0x00).
The next step is to redefine the meaning of dma_data->data_type to unblock
this limitation.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Tested-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions
