From: timur@freescale.com (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry checking for each DAIs separately
Date: Thu, 1 Sep 2011 15:35:35 -0500 [thread overview]
Message-ID: <4E5FEC97.6080608@freescale.com> (raw)
In-Reply-To: <4E5FDDCB.9060709@metafoo.de>
Lars-Peter Clausen wrote:
> Try to add a small delay between the two commands. e.g. 'aplay -r 8000 ... &
> sleep 1; arecrod -r 16000 ...'. And of course the DAIs need to be configured to
> be asynchronous, otherwise you'll of course catch the error in the fsl_ssi driver.
Ok, I'm an idiot. I just noticed that I don't support different sample rates
for playback and capture in my driver, because the CS4270 doesn't support it.
The P1022DS uses the WM8776, which does support it, but I never updated the driver.
Another oddity is that I have this code:
/* Are the RX and the TX clocks locked? */
if (of_find_property(np, "fsl,ssi-asynchronous", NULL))
ssi_private->asynchronous = 1;
else
ssi_private->cpu_dai_drv.symmetric_rates = 1;
and later I do this:
if (!ssi_private->asynchronous) {
snd_pcm_hw_constraint_minmax(substream->runtime,
SNDRV_PCM_HW_PARAM_SAMPLE_BITS,
first_runtime->sample_bits,
first_runtime->sample_bits);
So it looks like I'm confusing sample rate locking with sample size locking. Ugh.
Anyway, I'm not in any position at the moment to verify this patch. I need to
get my driver working with asynchronous sample rates first.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-09-01 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 9:15 [RFC v2 PATCH 1/1] ASoC: soc-core: symmetry checking for each DAIs separately Dong Aisheng
2011-08-29 20:34 ` [alsa-devel] " Tabi Timur-B04825
2011-08-30 2:54 ` Dong Aisheng-B29396
2011-08-31 10:52 ` Liam Girdwood
2011-08-31 11:55 ` Tabi Timur-B04825
2011-08-31 12:17 ` Lars-Peter Clausen
2011-09-01 18:58 ` Timur Tabi
2011-09-01 19:32 ` Lars-Peter Clausen
2011-09-01 20:35 ` Timur Tabi [this message]
2011-09-16 3:02 ` Dong Aisheng
2011-09-02 14:44 ` Wolfram Sang
2011-09-21 14:59 ` 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=4E5FEC97.6080608@freescale.com \
--to=timur@freescale.com \
--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).