Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>, Timur Tabi <timur@tabi.org>,
	Xiubo Li <Li.Xiubo@freescale.com>,
	Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH 2/4] ASoC: fsl: Update set_tdm_slot() semantics
Date: Tue, 13 Jan 2015 01:58:34 -0800	[thread overview]
Message-ID: <20150113095833.GA3189@Alpha> (raw)
In-Reply-To: <1421054841-19858-3-git-send-email-lars@metafoo.de>

On Mon, Jan 12, 2015 at 10:27:18AM +0100, Lars-Peter Clausen wrote:
> The fsl-ssi and imx-ssi drivers use inverted semantics for the tx_mask and
> rx_mask parameter of the set_tdm_slot() callback compared to rest of ASoC.
> This patch updates the driver's semantics to be consistent with the rest of
> ASoC, i.e. a set bit means a active slot and a cleared bit means a inactive
> slot.  This will allow us to use the set_tdm_slot() API in a more generic
> way.
> 
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> Changes since v1:
>  * Don't change the esai driver as it does not use the inverted semantics.
> ---
>  sound/soc/fsl/eukrea-tlv320.c | 2 +-
>  sound/soc/fsl/fsl_ssi.c       | 4 ++--
>  sound/soc/fsl/fsl_utils.c     | 6 +++---
>  sound/soc/fsl/imx-mc13783.c   | 2 +-
>  sound/soc/fsl/imx-ssi.c       | 4 ++--
>  sound/soc/fsl/wm1133-ev1.c    | 4 ++--
>  6 files changed, 11 insertions(+), 11 deletions(-)

> diff --git a/sound/soc/fsl/imx-mc13783.c b/sound/soc/fsl/imx-mc13783.c
> index 9589452..9e6493d 100644
> --- a/sound/soc/fsl/imx-mc13783.c
> +++ b/sound/soc/fsl/imx-mc13783.c
> @@ -45,7 +45,7 @@ static int imx_mc13783_hifi_hw_params(struct snd_pcm_substream *substream,
>  	if (ret)
>  		return ret;
>  
> -	ret = snd_soc_dai_set_tdm_slot(cpu_dai, 0x0, 0xfffffffc, 2, 16);
> +	ret = snd_soc_dai_set_tdm_slot(cpu_dai, 0x3, 0x3, 2, 16);

Hmm..I just notice the original configuration was 0x0 with 0xfffffffc.
It doesn't look making sense to me by using 0x0 here but not sure if
it was intentional.

However, I suppose it should be fine since the time slot number was 2.

Acked-by: Nicolin Chen <nicoleotsuka@gmail.com>

Thank you

  reply	other threads:[~2015-01-13  9:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12  9:27 [PATCH 0/4] ASoC: Make set_tdm_slot() semantics consistent Lars-Peter Clausen
2015-01-12  9:27 ` [PATCH 1/4] ASoC: mc13783: Update set_tdm_slot() semantics Lars-Peter Clausen
2015-01-12  9:27 ` [PATCH 2/4] ASoC: fsl: " Lars-Peter Clausen
2015-01-13  9:58   ` Nicolin Chen [this message]
2015-01-12  9:27 ` [PATCH 3/4] ASoC: fsl: Remove fsl_asoc_xlate_tdm_slot_mask() Lars-Peter Clausen
2015-01-12  9:27 ` [PATCH 4/4] ASoC: Update snd_soc_dai_set_tdm_slot() documentation Lars-Peter Clausen
2015-01-14 19:08 ` [PATCH 0/4] ASoC: Make set_tdm_slot() semantics consistent Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2015-01-10 10:52 Lars-Peter Clausen
2015-01-10 10:52 ` [PATCH 2/4] ASoC: fsl: Update set_tdm_slot() semantics Lars-Peter Clausen
2015-01-10 20:00   ` Nicolin Chen
2015-01-11 11:45     ` Lars-Peter Clausen

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=20150113095833.GA3189@Alpha \
    --to=nicoleotsuka@gmail.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=shawn.guo@linaro.org \
    --cc=timur@tabi.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