From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Lu, Brent" <brent.lu@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "Rojewski, Cezary" <cezary.rojewski@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
"Zhi, Yong" <yong.zhi@intel.com>,
Terry Cheong <htcheong@chromium.org>,
"Bhat, Uday M" <uday.m.bhat@intel.com>,
"Chiang, Mac" <mac.chiang@intel.com>,
"R, Dharageswari" <dharageswari.r@intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
ye xingchen <ye.xingchen@zte.com.cn>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2 1/2] ASoC: Intel: maxim-common: get codec number from ACPI
Date: Wed, 26 Jul 2023 10:52:53 +0200 [thread overview]
Message-ID: <9e8892cd-4c31-61a2-94e0-379e576cb7d6@linux.intel.com> (raw)
In-Reply-To: <CY5PR11MB625741E8CCBA25EAA82739579700A@CY5PR11MB6257.namprd11.prod.outlook.com>
On 7/26/23 10:33 AM, Lu, Brent wrote:
>
>>> const struct snd_soc_dapm_route max_98373_dapm_routes[] = { @@
>>> -168,17 +181,6 @@ static struct snd_soc_codec_conf max_98390_codec_conf[]
>> = {
>>> .dlc = COMP_CODEC_CONF(MAX_98390_DEV1_NAME),
>>> .name_prefix = "Left",
>>> },
>>> -};
>>> -
>>> -static struct snd_soc_codec_conf max_98390_4spk_codec_conf[] = {
>>> - {
>>> - .dlc = COMP_CODEC_CONF(MAX_98390_DEV0_NAME),
>>> - .name_prefix = "Right",
>>> - },
>>> - {
>>> - .dlc = COMP_CODEC_CONF(MAX_98390_DEV1_NAME),
>>> - .name_prefix = "Left",
>>> - },
>>
>> if you remove the codec conf, doesn't this impact the Kcontrols names?
>> Does this break existing UCM files?
>>
>> It's rather hard to review with just the diff.
>>
>
> I just merge two arrays, max_98373_dapm_routes and max_98390_4spk_codec_conf,
> since the first two entries are the same.
Routes and codec conf are different things, not following how you can
merge them?
Wondering if you are referring to a different array, i.e.
static struct snd_soc_codec_conf max_98390_codec_conf[]
static struct snd_soc_codec_conf max_98390_4spk_codec_conf[]
>
> Later in max_98390_set_codec_conf() function we will set the num_configs with
> number of amplifiers.
>
> void max_98390_set_codec_conf(struct snd_soc_card *card)
> {
> unsigned int num_codecs = get_num_codecs(MAX_98390_ACPI_HID);
>
> card->codec_conf = max_98390_codec_conf;
>
> switch (num_codecs) {
> case 2:
> case 4:
> card->num_configs = num_codecs;
>
> Regards,
> Brent
>
next prev parent reply other threads:[~2023-07-26 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:08 [PATCH v2 0/2] Intel: sof_rt5682: remove quirk flag Brent Lu
2023-07-26 14:08 ` [PATCH v2 1/2] ASoC: Intel: maxim-common: get codec number from ACPI Brent Lu
2023-07-26 8:15 ` Pierre-Louis Bossart
2023-07-26 8:33 ` Lu, Brent
2023-07-26 8:52 ` Pierre-Louis Bossart [this message]
2023-07-26 9:03 ` Lu, Brent
2023-07-26 16:27 ` Andy Shevchenko
2023-07-27 3:18 ` Lu, Brent
2023-07-26 14:08 ` [PATCH v2 2/2] ASoC: Intel: sof_rt5682: remove SOF_MAX98390_TWEETER_SPEAKER_PRESENT flag Brent Lu
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=9e8892cd-4c31-61a2-94e0-379e576cb7d6@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brent.lu@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=dharageswari.r@intel.com \
--cc=htcheong@chromium.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mac.chiang@intel.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=uday.m.bhat@intel.com \
--cc=ye.xingchen@zte.com.cn \
--cc=yong.zhi@intel.com \
--cc=yung-chuan.liao@linux.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
all inboxes | Powered by JetHome®