From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Ajye Huang <ajye_huang@compal.corp-partner.google.com>
Cc: Libin Yang <libin.yang@intel.com>,
"balamurugan . c" <balamurugan.c@intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Muralidhar Reddy <muralidhar.reddy@intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Akihiko Odaki <akihiko.odaki@gmail.com>,
ye xingchen <ye.xingchen@zte.com.cn>,
David Lin <CTLIN0@nuvoton.com>,
alsa-devel@alsa-project.org,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Brent Lu <brent.lu@intel.com>, Yong Zhi <yong.zhi@intel.com>
Subject: Re: [PATCH v2] ASoC: Intel: sof_nau8825: add variant with nau8318 amplifier.
Date: Fri, 16 Dec 2022 11:36:56 -0600 [thread overview]
Message-ID: <9aa4bffd-bc7e-0e40-3063-5ce80b5fbe9a@linux.intel.com> (raw)
In-Reply-To: <CALprXBYy9_ax8-xfh0paB59Pn=TB7yVLwtY8vnT_-y5vWd867w@mail.gmail.com>
On 12/16/22 10:55, Ajye Huang wrote:
> Hi Pierre
>
> On Sat, Dec 17, 2022 at 12:03 AM Pierre-Louis Bossart
> <pierre-louis.bossart@linux.intel.com> wrote:
>
>> 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?
>
> Really , it has two speakers. The nau8318 is an auto mode Amplifier
> chip, similar to the max98360a amp chip.
> EX: Sof_maxim_common.c (sound\soc\intel\boards):
> static struct snd_soc_dai_link_component max_98360a_components[] = {
> {
> .name = MAX_98360A_DEV0_NAME,
> .dai_name = MAX_98357A_CODEC_DAI,
> }
> };
> It is not an i2c interface, from the nau8318 data sheet, there are
> five pins used mainly. one for enable, others for I2S.
> EN-- enable pin
> FSR-- Frame Sync, Right
> FSL-- Frame Sync, Left
> BCLK-- bit clock
> DACIN-- Input i2s data
>
> The FSR and FSL pins are for Left and Right channels used.
> thanks
Ok, thanks for the explanations.
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2022-12-16 17:37 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
2022-12-16 16:55 ` Ajye Huang
2022-12-16 17:36 ` Pierre-Louis Bossart [this message]
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=9aa4bffd-bc7e-0e40-3063-5ce80b5fbe9a@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=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®