Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jassi Brar <jassi.brar@samsung.com>
Cc: sbkim73@samsung.com, kgene.kim@samsung.com,
	alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: WM8580: Debug BCLK and sample size
Date: Tue, 07 Dec 2010 12:48:32 +0000	[thread overview]
Message-ID: <1291726112.3275.23.camel@odin> (raw)
In-Reply-To: <1291717387-11961-1-git-send-email-jassi.brar@samsung.com>

On Tue, 2010-12-07 at 19:23 +0900, Jassi Brar wrote:
> In case of SNDRV_PCM_FORMAT_S32_LE, we need to set WM8580_AIF_LENGTH_32,
> rather than WM8580_AIF_LENGTH_24.
> Also, the BCLK has to be 64fs, for sample size of 20, 24 and 32 bits.
> 
> Signed-off-by: Jassi Brar <jassi.brar@samsung.com>
> ---
>  sound/soc/codecs/wm8580.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/sound/soc/codecs/wm8580.c b/sound/soc/codecs/wm8580.c
> index cb7765f..45efc94 100644
> --- a/sound/soc/codecs/wm8580.c
> +++ b/sound/soc/codecs/wm8580.c
> @@ -491,16 +491,16 @@ static int wm8580_paif_hw_params(struct snd_pcm_substream *substream,
>  		paifa |= 0x8;
>  		break;
>  	case SNDRV_PCM_FORMAT_S20_3LE:
> -		paifa |= 0x10;
> +		paifa |= 0x0;

Any reason why we are OR ing paifa with 0 ?

>  		paifb |= WM8580_AIF_LENGTH_20;
>  		break;
>  	case SNDRV_PCM_FORMAT_S24_LE:
> -		paifa |= 0x10;
> +		paifa |= 0x0;
>  		paifb |= WM8580_AIF_LENGTH_24;
>  		break;
>  	case SNDRV_PCM_FORMAT_S32_LE:
> -		paifa |= 0x10;
> -		paifb |= WM8580_AIF_LENGTH_24;
> +		paifa |= 0x0;
> +		paifb |= WM8580_AIF_LENGTH_32;
>  		break;
>  	default:
>  		return -EINVAL;

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-12-07 12:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 10:23 [PATCH] ASoC: WM8580: Debug BCLK and sample size Jassi Brar
2010-12-07 12:48 ` Liam Girdwood [this message]
2010-12-07 13:41   ` Jassi Brar
2010-12-08  7:50 ` [PATCHv2] " Jassi Brar
2010-12-08  8:06   ` 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=1291726112.3275.23.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jassi.brar@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=sbkim73@samsung.com \
    /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