From: Benoit Cousson <bcousson@baylibre.com>
To: Vinod Koul <vinod.koul@intel.com>, broonie@kernel.org, lars@metafoo.de
Cc: misael.lopez@ti.com, lgirdwood@gmail.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH v4 6/8] ASoC: compress: Add support for DAI multicodec
Date: Thu, 03 Jul 2014 13:09:28 +0200 [thread overview]
Message-ID: <53B539E8.1000301@baylibre.com> (raw)
In-Reply-To: <20140703064147.GK2296@intel.com>
On 03/07/2014 08:41, Vinod Koul wrote:
> On Wed, Jul 02, 2014 at 02:53:50PM +0200, Benoit Cousson wrote:
>>>> @@ -622,23 +633,33 @@ int soc_new_compress(struct snd_soc_pcm_runtime *rtd, int num)
>>>> {
>>>> struct snd_soc_codec *codec = rtd->codec;
>>>> struct snd_soc_platform *platform = rtd->platform;
>>>> - struct snd_soc_dai *codec_dai = rtd->codec_dai;
>>>> struct snd_soc_dai *cpu_dai = rtd->cpu_dai;
>>>> struct snd_compr *compr;
>>>> struct snd_pcm *be_pcm;
>>>> char new_name[64];
>>>> - int ret = 0, direction = 0;
>>>> -
>>>> - /* check client and interface hw capabilities */
>>>> - snprintf(new_name, sizeof(new_name), "%s %s-%d",
>>>> - rtd->dai_link->stream_name, codec_dai->name, num);
>>>> -
>>>> - if (codec_dai->driver->playback.channels_min)
>>>> - direction = SND_COMPRESS_PLAYBACK;
>>>> - else if (codec_dai->driver->capture.channels_min)
>>>> - direction = SND_COMPRESS_CAPTURE;
>>>> - else
>>>> - return -EINVAL;
>>>> + int i, ret = 0, direction = -1;
>>>> +
>>>> + for (i = 0; i < rtd->num_codecs; i++) {
>>>> + struct snd_soc_dai *codec_dai = rtd->codec_dais[i];
>>>> + /* check client and interface hw capabilities */
>>>> + snprintf(new_name, sizeof(new_name), "%s %s-%d",
>>>> + rtd->dai_link->stream_name, codec_dai->name, num);
>>>> +
>>>> + if (direction < 0) {
>>>> + if (codec_dai->driver->playback.channels_min)
>>>> + direction = SND_COMPRESS_PLAYBACK;
>>>> + else if (codec_dai->driver->capture.channels_min)
>>>> + direction = SND_COMPRESS_CAPTURE;
>>> direction wont change with multiple codecs, so this loop makes no sense here.
>>> For simplcity perhaps we can use cpu_dai?
>>>> + else
>>>> + return -EINVAL;
>>>> + } else {
>>> when will this get executed? You have initialized direction to -1 and if case is
>>> always true. I think compiler will simply remove the below sinppet.
>>
>> direction is set to -1, then the first iteration will set it to the
>> direction of the first codec_dai. The other iteration are just
>> checking that there are all in the same direction and will fail
>> otherwise.
>>
>>>> + if ((codec_dai->driver->playback.channels_min &&
>>>> + direction != SND_COMPRESS_PLAYBACK) ||
>>>> + (codec_dai->driver->capture.channels_min &&
>>>> + direction != SND_COMPRESS_CAPTURE))
>>> and what exactly are we trying to check here?
>>
>> That every codec_dai are in the same direction.
>>
>> If you think this is pointless since every DAI are always in the
>> same direction, we can just remove it.
> I think that will simplify it. we certainly dont expect different direction,
> right?
Lars, Mark
Any thought on that? Does that sound reasonable to you to use only the
first codec_dai to figure out the direction?
Thanks,
Benoit
--
Benoît Cousson
BayLibre
Embedded Linux Technology Lab
www.baylibre.com
next prev parent reply other threads:[~2014-07-03 11:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 7:47 [PATCH v4 0/8] ASoC: core: Add support for DAI multicodec Benoit Cousson
2014-07-01 7:47 ` [PATCH v4 1/8] ASoC: core: Change soc_link_dai_widgets signature for multiple codecs Benoit Cousson
2014-07-01 17:17 ` Mark Brown
2014-07-04 16:13 ` Benoit Cousson
2014-07-04 16:51 ` Mark Brown
2014-07-01 7:47 ` [PATCH v4 2/8] ASoC: pcm: Refactor soc_pcm_apply_msb for multicodecs Benoit Cousson
2014-07-01 17:20 ` Mark Brown
2014-07-01 17:31 ` Benoit Cousson
2014-07-01 7:47 ` [PATCH v4 3/8] ASoC: core: Add initial support for DAI multicodec Benoit Cousson
2014-07-01 13:19 ` Lars-Peter Clausen
2014-07-01 17:27 ` Benoit Cousson
2014-07-01 7:47 ` [PATCH v4 4/8] ASoC: pcm: Add " Benoit Cousson
2014-07-01 13:32 ` Lars-Peter Clausen
2014-07-01 7:47 ` [PATCH v4 5/8] ASoC: dapm: " Benoit Cousson
2014-07-01 13:40 ` Lars-Peter Clausen
2014-07-01 7:47 ` [PATCH v4 6/8] ASoC: compress: " Benoit Cousson
2014-07-01 13:49 ` Lars-Peter Clausen
2014-07-01 16:25 ` Vinod Koul
2014-07-01 16:42 ` Lars-Peter Clausen
2014-07-01 16:45 ` Vinod Koul
2014-07-01 17:32 ` Benoit Cousson
2014-07-01 16:41 ` Vinod Koul
2014-07-01 17:41 ` Mark Brown
2014-07-03 6:39 ` Vinod Koul
2014-07-02 12:53 ` Benoit Cousson
2014-07-03 6:41 ` Vinod Koul
2014-07-03 11:09 ` Benoit Cousson [this message]
2014-07-03 11:16 ` Mark Brown
2014-07-03 11:20 ` Lars-Peter Clausen
2014-07-03 11:39 ` Benoit Cousson
2014-07-03 11:43 ` Lars-Peter Clausen
2014-07-03 11:46 ` Benoit Cousson
2014-07-03 12:06 ` Vinod Koul
2014-07-03 12:18 ` Mark Brown
2014-07-03 16:15 ` Vinod Koul
2014-07-03 18:23 ` Lars-Peter Clausen
2014-07-04 13:55 ` Benoit Cousson
2014-07-03 18:38 ` Mark Brown
2014-07-03 19:09 ` Pierre-Louis Bossart
2014-07-01 7:48 ` [PATCH v4 7/8] ASoC: pcm: Add soc_dai_hw_params helper Benoit Cousson
2014-07-01 13:43 ` Lars-Peter Clausen
2014-07-01 7:48 ` [PATCH v4 8/8] ASoC: core: Add a warning for link_dai_widget in the multicodec case Benoit Cousson
2014-07-01 13:41 ` 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=53B539E8.1000301@baylibre.com \
--to=bcousson@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=misael.lopez@ti.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).