Re: [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths

2013-12-03 Thread Lee Jones
On Mon, 02 Dec 2013, Lars-Peter Clausen wrote: > On 12/02/2013 07:00 PM, Lee Jones wrote: > > The Slave Config's addr_width attribute is populated by data_width of > > dma_cfg, which in turn is derived from dma_params' data_size attribute > > and that comes from the slot_width which is always 16 b

Re: [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths

2013-12-02 Thread Mark Brown
On Mon, Dec 02, 2013 at 06:00:20PM +, Lee Jones wrote: > The Slave Config's addr_width attribute is populated by data_width of > dma_cfg, which in turn is derived from dma_params' data_size attribute > and that comes from the slot_width which is always 16 bits (2 Bytes). > We're cutting out the

Re: [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths

2013-12-02 Thread Lars-Peter Clausen
On 12/02/2013 07:00 PM, Lee Jones wrote: > The Slave Config's addr_width attribute is populated by data_width of > dma_cfg, which in turn is derived from dma_params' data_size attribute > and that comes from the slot_width which is always 16 bits (2 Bytes). > We're cutting out the middle man here a

[PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths

2013-12-02 Thread Lee Jones
The Slave Config's addr_width attribute is populated by data_width of dma_cfg, which in turn is derived from dma_params' data_size attribute and that comes from the slot_width which is always 16 bits (2 Bytes). We're cutting out the middle man here and just setting the DMA Slave Config directly. C