From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Shreyas NC <shreyas.nc@intel.com>
Cc: alsa-devel@alsa-project.org, ckeepax@opensource.cirrus.com,
patches.audio@intel.com, liam.r.girdwood@linux.intel.com,
Vinod Koul <vkoul@kernel.org>,
broonie@kernel.org
Subject: Re: [PATCH v6 1/3] ASoC: Add initial support for multiple CPU DAIs
Date: Fri, 22 Jun 2018 10:13:28 -0500 [thread overview]
Message-ID: <dffba216-f4ff-4ec6-24f0-f9c7bbdf4b68@linux.intel.com> (raw)
In-Reply-To: <20180622041437.GP3116@snc-desk>
>>> +static int snd_soc_init_single_cpu_dai(struct snd_soc_card *card,
>>> + struct snd_soc_dai_link *dai_link)
>>> +{
>>> + if (dai_link->cpu_name || dai_link->cpu_of_node ||
>>> + dai_link->cpu_dai_name) {
>>> + dai_link->num_cpu_dai = 1;
>>> + dai_link->cpu_dai = devm_kzalloc(card->dev,
>>> + sizeof(struct snd_soc_dai_link_component),
>>> + GFP_KERNEL);
>>> +
>>> + if (!dai_link->cpu_dai)
>>> + return -ENOMEM;
>>> +
>>> + dai_link->cpu_dai[0].name = dai_link->cpu_name;
>>> + dai_link->cpu_dai[0].of_node = dai_link->cpu_of_node;
>>> + dai_link->cpu_dai[0].dai_name = dai_link->cpu_dai_name;
>> Question: is cpu_dai[i].of_node defined for i>0 in the multi cpu_dai case?
>>
>
> Yes, it should be defined.
I have limited understanding of how cpu_of_node would be handled and if
there is any guidance for DT folks on how to deal with multiple cpu_dais.
>
>>> @@ -1644,7 +1751,7 @@ int snd_soc_runtime_set_dai_fmt(struct snd_soc_pcm_runtime *rtd,
>>> unsigned int dai_fmt)
>>> {
>>> struct snd_soc_dai **codec_dais = rtd->codec_dais;
>>> - struct snd_soc_dai *cpu_dai = rtd->cpu_dai;
>>> + struct snd_soc_dai **cpu_dais = rtd->cpu_dais;
>>> unsigned int i;
>>> int ret;
>>> @@ -1659,35 +1766,44 @@ int snd_soc_runtime_set_dai_fmt(struct snd_soc_pcm_runtime *rtd,
>>> }
>>> }
>>> - /* Flip the polarity for the "CPU" end of a CODEC<->CODEC link */
>> why was this comment removed?
>>
>
> Looks like I messed up resolving ocnflicts while rebase
>
>>> /* the component which has non_legacy_dai_naming is Codec */
>>> - if (cpu_dai->component->driver->non_legacy_dai_naming) {
>> Not sure if the code refactoring below makes sense in a codec-codec link,
>> you probably wouldn't have multiple cpu_dais then, would you?
>
> Yes, a valid point. You suggest to leave this piece of code as is ?
Not necessarily. I don't understand how the codec-codec and multi
cpu_dais intersect, all I am asking for is a check if this change is
needed or not.
>
>>> - unsigned int inv_dai_fmt;
>>> + for (i = 0; i < rtd->num_cpu_dai; i++) {
>>> + struct snd_soc_dai *cpu_dai = cpu_dais[i];
>>> + unsigned int inv_dai_fmt, temp_dai_fmt;
>>> - inv_dai_fmt = dai_fmt & ~SND_SOC_DAIFMT_MASTER_MASK;
>>> - switch (dai_fmt & SND_SOC_DAIFMT_MASTER_MASK) {
>>> - case SND_SOC_DAIFMT_CBM_CFM:
>>> - inv_dai_fmt |= SND_SOC_DAIFMT_CBS_CFS;
>>> - break;
>>> - case SND_SOC_DAIFMT_CBM_CFS:
>>> - inv_dai_fmt |= SND_SOC_DAIFMT_CBS_CFM;
>>> - break;
>>> - case SND_SOC_DAIFMT_CBS_CFM:
>>> - inv_dai_fmt |= SND_SOC_DAIFMT_CBM_CFS;
>>> - break;
>>> - case SND_SOC_DAIFMT_CBS_CFS:
>>> - inv_dai_fmt |= SND_SOC_DAIFMT_CBM_CFM;
>>> - break;
>>> - }
>>> + temp_dai_fmt = dai_fmt;
>>> + if (cpu_dai->component->driver->non_legacy_dai_naming) {
>>> - dai_fmt = inv_dai_fmt;
>>> - }
>>> + inv_dai_fmt = dai_fmt & ~SND_SOC_DAIFMT_MASTER_MASK;
>>> - ret = snd_soc_dai_set_fmt(cpu_dai, dai_fmt);
>>> - if (ret != 0 && ret != -ENOTSUPP) {
>>> - dev_warn(cpu_dai->dev,
>>> - "ASoC: Failed to set DAI format: %d\n", ret);
>>> - return ret;
>>> + switch (dai_fmt & SND_SOC_DAIFMT_MASTER_MASK) {
>>> + case SND_SOC_DAIFMT_CBM_CFM:
>>> + inv_dai_fmt |= SND_SOC_DAIFMT_CBS_CFS;
>>> + break;
>>> +
>>> + case SND_SOC_DAIFMT_CBM_CFS:
>>> + inv_dai_fmt |= SND_SOC_DAIFMT_CBS_CFM;
>>> + break;
>>> +
>>> + case SND_SOC_DAIFMT_CBS_CFM:
>>> + inv_dai_fmt |= SND_SOC_DAIFMT_CBM_CFS;
>>> + break;
>>> +
>>> + case SND_SOC_DAIFMT_CBS_CFS:
>>> + inv_dai_fmt |= SND_SOC_DAIFMT_CBM_CFM;
>>> + break;
>>> +
>>> + }
>>> +
>>> + temp_dai_fmt = inv_dai_fmt;
>>> + }
>>> +
>>> + ret = snd_soc_dai_set_fmt(cpu_dai, temp_dai_fmt);
>>> + if (ret != 0 && ret != -ENOTSUPP) {
>>> + dev_warn(cpu_dai->dev,
>>> + "ASoC: Failed to set DAI format: %d\n", ret);
>>> + return ret;
>>> + }
>>> }
>>>
>>
>
next prev parent reply other threads:[~2018-06-22 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 10:54 [PATCH v6 0/3] ASoC: Add Multi CPU DAI support Shreyas NC
2018-06-20 10:54 ` [PATCH v6 1/3] ASoC: Add initial support for multiple CPU DAIs Shreyas NC
2018-06-22 0:35 ` Pierre-Louis Bossart
2018-06-22 4:14 ` Shreyas NC
2018-06-22 15:13 ` Pierre-Louis Bossart [this message]
2018-06-25 4:50 ` Shreyas NC
2018-06-25 10:03 ` Charles Keepax
2018-06-20 10:54 ` [PATCH v6 2/3] ASoC: Add multiple CPU DAI support for PCM ops Shreyas NC
2018-06-22 2:43 ` Pierre-Louis Bossart
2018-06-22 5:04 ` Shreyas NC
2018-06-22 16:05 ` Pierre-Louis Bossart
2018-06-25 4:59 ` Shreyas NC
2018-06-20 10:54 ` [PATCH v6 3/3] ASoC: Add multiple CPU DAI support in DAPM Shreyas NC
2018-06-22 2:55 ` Pierre-Louis Bossart
2018-06-22 5:53 ` Shreyas NC
2018-06-22 16:18 ` Pierre-Louis Bossart
2018-06-26 10:35 ` Shreyas NC
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=dffba216-f4ff-4ec6-24f0-f9c7bbdf4b68@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=shreyas.nc@intel.com \
--cc=vkoul@kernel.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).