From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2] ASoC: Handle multiple codecs with split playback / capture
Date: Thu, 20 Aug 2015 10:10:06 -0700 [thread overview]
Message-ID: <20150820171006.GD12027@sirena.org.uk> (raw)
In-Reply-To: <55D5F611.9090205@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]
On Thu, Aug 20, 2015 at 10:45:21AM -0500, Pierre-Louis Bossart wrote:
> On 8/19/15 10:32 AM, Ricard Wanderlof wrote:
> >+ /*
> >+ * Skip CODECs which don't support the current stream type.
> >+ * Otherwise, since the rate, channel, and format values will
> >+ * zero in that case, we would have no usable settings left,
> >+ * causing the resulting setup to fail.
> >+ * At least one CODEC should match, otherwise we should have
> >+ * bailed out on a higher level, since there would be no
> >+ * CODEC to support the transfer direction in that case.
> >+ */
> >+ if (!snd_soc_dai_stream_valid(rtd->codec_dais[i],
> >+ substream->stream))
> Maybe I misunderstood but shouldn't there be some sort of verification that
> the codecs can use the same number of slots between playback and capture if
> they share the same LRCLK/FS? e.g. it's not uncommon to have 4 mic capture
> and 2 ch playback. If the capture and playback is handled by different chips
> you'd still need to maintain some level of consistency.
Yes, this was my point about it being hard to work out what's going on
with regard to things being shared.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-08-20 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 15:32 [PATCH v2] ASoC: Handle multiple codecs with split playback / capture Ricard Wanderlof
2015-08-20 15:45 ` Pierre-Louis Bossart
2015-08-20 17:10 ` Mark Brown [this message]
2015-08-21 7:11 ` Ricard Wanderlof
[not found] ` <55D72E1B.2040109@linux.intel.com>
2015-08-21 14:05 ` Ricard Wanderlof
2015-09-03 15:05 ` Ricard Wanderlof
2015-09-03 15:18 ` Mark Brown
2015-09-03 15:59 ` Ricard Wanderlof
2015-09-03 16:24 ` Mark Brown
2015-09-20 0:13 ` Applied "ASoC: Handle multiple codecs with split playback / capture" to the asoc tree 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=20150820171006.GD12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ricard.wanderlof@axis.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