From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Sean Hong <sean.hong@quanta.corp-partner.google.com>,
perex@perex.cz, tiwai@suse.com
Cc: cezary.rojewski@intel.com, kai.vehmanen@linux.intel.com,
peter.ujfalusi@linux.intel.com,
ranjani.sridharan@linux.intel.com, linux-kernel@vger.kernel.org,
liam.r.girdwood@linux.intel.com, broonie@kernel.org,
alsa-devel@alsa-project.org, yung-chuan.liao@linux.intel.com,
brent.lu@intel.com, yong.zhi@intel.com
Subject: Re: [PATCH] ASoC: Intel: sof_rt5682: Add support for jsl_rt5682_rt1019
Date: Fri, 12 Aug 2022 14:41:09 +0200 [thread overview]
Message-ID: <4fe4853d-a446-1f72-2f32-f63eb6733adc@linux.intel.com> (raw)
In-Reply-To: <20220812114804.550809-1-sean.hong@quanta.corp-partner.google.com>
> static const struct snd_soc_acpi_codecs mx98360a_spk = {
> .num_codecs = 1,
> .codecs = {"MX98360A"}
> @@ -78,6 +83,14 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_jsl_machines[] = {
> .quirk_data = &mx98360a_spk,
> .sof_tplg_filename = "sof-jsl-rt5682-mx98360a.tplg",
> },
> + {
> + .comp_ids = &rt5682_rt5682s_hp,
> + .drv_name = "jsl_rt5682_rt1019",
> + .sof_fw_filename = "sof-jsl.ri",
> + .machine_quirk = snd_soc_acpi_codec_list,
> + .quirk_data = &rt1019p_spk,
> + .sof_tplg_filename = "sof-jsl-rt5682-rt1015.tplg",
this patch adds support for the rt1019, the line above looks like a
copy-paste mistake.
We shouldn't use the same topology files for different platforms, it's
not good maintenance-wise and since we store default values for some
controls it's really not a good idea.
Please use a unique string such as sof-jsl-rt5682-rt1019.tplg, thanks.
> + },
> {
> .id = "10134242",
> .drv_name = "jsl_cs4242_mx98360a",
WARNING: multiple messages have this Message-ID (diff)
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Sean Hong <sean.hong@quanta.corp-partner.google.com>,
perex@perex.cz, tiwai@suse.com
Cc: cezary.rojewski@intel.com, liam.r.girdwood@linux.intel.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
broonie@kernel.org, brent.lu@intel.com, yong.zhi@intel.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: sof_rt5682: Add support for jsl_rt5682_rt1019
Date: Fri, 12 Aug 2022 14:41:09 +0200 [thread overview]
Message-ID: <4fe4853d-a446-1f72-2f32-f63eb6733adc@linux.intel.com> (raw)
In-Reply-To: <20220812114804.550809-1-sean.hong@quanta.corp-partner.google.com>
> static const struct snd_soc_acpi_codecs mx98360a_spk = {
> .num_codecs = 1,
> .codecs = {"MX98360A"}
> @@ -78,6 +83,14 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_jsl_machines[] = {
> .quirk_data = &mx98360a_spk,
> .sof_tplg_filename = "sof-jsl-rt5682-mx98360a.tplg",
> },
> + {
> + .comp_ids = &rt5682_rt5682s_hp,
> + .drv_name = "jsl_rt5682_rt1019",
> + .sof_fw_filename = "sof-jsl.ri",
> + .machine_quirk = snd_soc_acpi_codec_list,
> + .quirk_data = &rt1019p_spk,
> + .sof_tplg_filename = "sof-jsl-rt5682-rt1015.tplg",
this patch adds support for the rt1019, the line above looks like a
copy-paste mistake.
We shouldn't use the same topology files for different platforms, it's
not good maintenance-wise and since we store default values for some
controls it's really not a good idea.
Please use a unique string such as sof-jsl-rt5682-rt1019.tplg, thanks.
> + },
> {
> .id = "10134242",
> .drv_name = "jsl_cs4242_mx98360a",
next prev parent reply other threads:[~2022-08-12 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 11:48 [PATCH] ASoC: Intel: sof_rt5682: Add support for jsl_rt5682_rt1019 Sean Hong
2022-08-12 11:48 ` Sean Hong
2022-08-12 12:41 ` Pierre-Louis Bossart [this message]
2022-08-12 12:41 ` Pierre-Louis Bossart
2022-08-12 19:09 ` kernel test robot
2022-08-12 19:09 ` kernel test robot
2022-08-15 2:14 ` Lu, Brent
2022-08-15 2:14 ` Lu, Brent
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 6:04 Sean Hong
2022-08-16 6:04 ` Sean Hong
2022-08-16 7:11 ` Lu, Brent
2022-08-16 7:11 ` Lu, Brent
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=4fe4853d-a446-1f72-2f32-f63eb6733adc@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--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=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sean.hong@quanta.corp-partner.google.com \
--cc=tiwai@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.