From: Takashi Iwai <tiwai@suse.de>
To: "Vladimir A. Barinov" <vbarinov@ru.mvista.com>
Cc: liam.girdwood@wolfsonmicro.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC TLV320AIC3X codec driver
Date: Wed, 14 Nov 2007 10:24:29 +0100 [thread overview]
Message-ID: <s5h6405facy.wl%tiwai@suse.de> (raw)
In-Reply-To: <473AF25F.5060305@ru.mvista.com>
At Wed, 14 Nov 2007 16:04:31 +0300,
Vladimir A. Barinov wrote:
>
> >> +/*
> >> + * All input lines are connected when !0xf and disconnected with 0xf bit field,
> >>
> >
> > Please keep the line within 80 chars. Try to run checkpatch.pl in
> > linuxkernel/scripts for checking such minor coding-style issues.
> >
> But this line is less then 80 chars :)
Ah, ok, maybe my editor window was too narrow. Please disregard it.
> >> +#define AIC3X_RATES SNDRV_PCM_RATE_8000_96000
> >> +#define AIC3X_FORMATS (SNDRV_PCM_FMTBIT_S16_LE | SNDRV_PCM_FMTBIT_S20_3LE | \
> >> + SNDRV_PCM_FMTBIT_S24_LE | SNDRV_PCM_FMTBIT_S32_LE)
> >>
> >
> > Are you sure that it's FMTBIT_S24_LE? It's not packed in 3 bytes but
> > uses lower 3 bytes of 4 bytes frame.
> >
> >
> Aic3x supports 16/20/24/32 bits data word length and in accordance with
> aic33 documentation the
> number of clocks per half-frame for each channel are equal to exact
> number of bits of the word.
> Unfortunately, now I have no h/w to test 24bits mode.
Then it sounds like the correct data format is FMTBIT_S24_3LE instead
of FMTBIT_S24_LE. The former is 3-byte format while the latter is
4-byte. Please check again.
thanks,
Takashi
next prev parent reply other threads:[~2007-11-14 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 19:41 [PATCH] ASoC TLV320AIC3X codec driver Vladimir Barinov
[not found] ` <s5hhcjpfecc.wl%tiwai@suse.de>
2007-11-14 13:04 ` Vladimir A. Barinov
2007-11-14 9:24 ` Takashi Iwai [this message]
2007-11-14 14:22 ` Vladimir A. Barinov
2007-11-14 14:53 ` [PATCH] ASoC TLV320AIC3X codec driver (take#2) Vladimir Barinov
2007-11-14 13:21 ` Takashi Iwai
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=s5h6405facy.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=vbarinov@ru.mvista.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