From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Akihiko Odaki <akihiko.odaki@gmail.com>,
Yong Zhi <yong.zhi@intel.com>,
ye xingchen <ye.xingchen@zte.com.cn>,
Muralidhar Reddy <muralidhar.reddy@intel.com>,
"balamurugan . c" <balamurugan.c@intel.com>,
Libin Yang <libin.yang@intel.com>,
Jaroslav Kysela <perex@perex.cz>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
David Lin <CTLIN0@nuvoton.com>, Brent Lu <brent.lu@intel.com>,
Takashi Iwai <tiwai@suse.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ASoC: Intel: sof_nau8825: add variant with nau8318 amplifier.
Date: Fri, 16 Dec 2022 10:03:03 -0600 [thread overview]
Message-ID: <b0612bbd-2eba-36cf-9c29-7542cf32adfd@linux.intel.com> (raw)
In-Reply-To: <20221216154938.9426-1-ajye_huang@compal.corp-partner.google.com>
On 12/16/22 09:49, Ajye Huang wrote:
> This patch adds the driver data for two nau8318 speaker amplifiers on
> SSP1 and nau8825 on SSP0 for ADL platform.
So here you are making reference to two amplifiers...
> +static struct snd_soc_dai_link_component nau8318_components[] = {
> + {
> + .name = "NVTN2012:00",
> + .dai_name = "nau8315-hifi",
> + }
> +};
but here there's only one? I was expecting something like what we've
used for Maxim amplifiers with a codec configuration and dailink
components that list the two amplifiers.
static struct snd_soc_codec_conf max_98373_codec_conf[] = {
{
.dlc = COMP_CODEC_CONF(MAX_98373_DEV0_NAME),
.name_prefix = "Right",
},
{
.dlc = COMP_CODEC_CONF(MAX_98373_DEV1_NAME),
.name_prefix = "Left",
},
};
struct snd_soc_dai_link_component max_98373_components[] = {
{ /* For Right */
.name = MAX_98373_DEV0_NAME,
.dai_name = MAX_98373_CODEC_DAI,
},
{ /* For Left */
.name = MAX_98373_DEV1_NAME,
.dai_name = MAX_98373_CODEC_DAI,
},
};
Or is this a commit message problem and there's really only one amplifier?
> +
> static struct snd_soc_dai_link_component dummy_component[] = {
> {
> .name = "snd-soc-dummy",
> @@ -486,6 +494,11 @@ static struct snd_soc_dai_link *sof_card_dai_links_create(struct device *dev,
> max_98360a_dai_link(&links[id]);
> } else if (sof_nau8825_quirk & SOF_RT1015P_SPEAKER_AMP_PRESENT) {
> sof_rt1015p_dai_link(&links[id]);
> + } else if (sof_nau8825_quirk &
> + SOF_NAU8318_SPEAKER_AMP_PRESENT) {
> + links[id].codecs = nau8318_components;
> + links[id].num_codecs = ARRAY_SIZE(nau8318_components);
> + links[id].init = speaker_codec_init;
The rest looks fine, I only have this one/two amplifier question.
next prev parent reply other threads:[~2022-12-16 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 15:49 Ajye Huang
2022-12-16 15:57 ` Ajye Huang
2022-12-16 16:05 ` Pierre-Louis Bossart
2022-12-16 16:57 ` Ajye Huang
2022-12-16 16:03 ` Pierre-Louis Bossart [this message]
2022-12-16 16:55 ` Ajye Huang
2022-12-16 17:36 ` Pierre-Louis Bossart
2022-12-20 14:06 ` Ajye Huang
2022-12-21 23:30 ` Ajye Huang
2022-12-22 0:27 ` Pierre-Louis Bossart
2022-12-22 2:38 ` Ajye Huang
2022-12-26 23:33 ` 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=b0612bbd-2eba-36cf-9c29-7542cf32adfd@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=CTLIN0@nuvoton.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=akihiko.odaki@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=balamurugan.c@intel.com \
--cc=brent.lu@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=libin.yang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhar.reddy@intel.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.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®