linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths
Date: Mon, 02 Dec 2013 19:34:29 +0100	[thread overview]
Message-ID: <529CD2B5.9060905@metafoo.de> (raw)
In-Reply-To: <1386007222-10081-1-git-send-email-lee.jones@linaro.org>

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 and just setting the DMA Slave
> Config directly.
> 
> Cc: alsa-devel at alsa-project.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>

Patch looks good. But as a follow up patch I think you can now switch to the
generic snd_dmaengine_pcm_prepare_slave_config.

> ---
>  sound/soc/ux500/ux500_pcm.c | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/sound/soc/ux500/ux500_pcm.c b/sound/soc/ux500/ux500_pcm.c
> index 6162f70..2f1bdb7 100644
> --- a/sound/soc/ux500/ux500_pcm.c
> +++ b/sound/soc/ux500/ux500_pcm.c
> @@ -104,26 +104,25 @@ static int ux500_pcm_prepare_slave_config(struct snd_pcm_substream *substream,
>  		struct dma_slave_config *slave_config)
>  {
>  	struct snd_soc_pcm_runtime *rtd = substream->private_data;
> -	struct ux500_msp_dma_params *dma_params;
> -	struct stedma40_chan_cfg *dma_cfg;
> +	struct snd_dmaengine_dai_dma_data *dma_params;
>  	int ret;
>  
>  	dma_params = snd_soc_dai_get_dma_data(rtd->cpu_dai, substream);
> -	dma_cfg = dma_params->dma_cfg;
>  
>  	ret = snd_hwparams_to_dma_slave_config(substream, params, slave_config);
>  	if (ret)
>  		return ret;
>  
>  	slave_config->dst_maxburst = 4;
> -	slave_config->dst_addr_width = dma_cfg->dst_info.data_width;
>  	slave_config->src_maxburst = 4;
> -	slave_config->src_addr_width = dma_cfg->src_info.data_width;
> +
> +	slave_config->src_addr_width = DMA_SLAVE_BUSWIDTH_2_BYTES;
> +	slave_config->dst_addr_width = DMA_SLAVE_BUSWIDTH_2_BYTES;
>  
>  	if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
> -		slave_config->dst_addr = dma_params->tx_rx_addr;
> +		slave_config->dst_addr = dma_params->addr;
>  	else
> -		slave_config->src_addr = dma_params->tx_rx_addr;
> +		slave_config->src_addr = dma_params->addr;
>  
>  	return 0;
>  }
> 

  parent reply	other threads:[~2013-12-02 18:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 18:00 [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths Lee Jones
2013-12-02 18:00 ` [PATCH 2/3] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-02 18:13   ` [alsa-devel] " Lars-Peter Clausen
2013-12-03  8:36     ` Lee Jones
2013-12-03  8:56       ` Lars-Peter Clausen
2013-12-03 10:03         ` Lee Jones
2013-12-02 18:00 ` [PATCH 3/3] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-12-02 18:10   ` [alsa-devel] " Lars-Peter Clausen
2013-12-03  8:40     ` Lee Jones
2013-12-03  8:57       ` Lars-Peter Clausen
2013-12-03  9:59         ` Lee Jones
2013-12-02 18:34 ` Lars-Peter Clausen [this message]
2013-12-03  8:31   ` [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths Lee Jones
2013-12-02 19:09 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=529CD2B5.9060905@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).