From: Brent Lu <brent.lu@intel.com>
To: alsa-devel@alsa-project.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.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>, Brent Lu <brent.lu@intel.com>,
linux-kernel@vger.kernel.org,
Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
Yong Zhi <yong.zhi@intel.com>,
Terry Cheong <htcheong@chromium.org>,
Uday M Bhat <uday.m.bhat@intel.com>,
Mac Chiang <mac.chiang@intel.com>,
"Dharageswari . R" <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: [PATCH v2 0/2] Intel: sof_rt5682: remove quirk flag
Date: Wed, 26 Jul 2023 22:08:46 +0800 [thread overview]
Message-ID: <20230726140848.2267568-1-brent.lu@intel.com> (raw)
We add a helper function to detect amplifier number according to device instance
in ACPI table so the SOF_MAX98390_TWEETER_SPEAKER_PRESENT flag and a dmi quirk
for 4-amplifier configuration could be safely removed.
Also refactor the max_98390_hw_params() function to use an array to handle the
TDM parameter.
Amplifier number detection and TDM parameter are tested on two Chromebooks. One
with 2 MAX98390 and one with 4 MAX98390 amplifier.
V2 Changes:
- fix some typos in cover letter
- use for_each_acpi_dev_match() macro to simplify the codec
- use 'unsign int' for codec number variable
Brent Lu (2):
ASoC: Intel: maxim-common: get codec number from ACPI
ASoC: Intel: sof_rt5682: remove SOF_MAX98390_TWEETER_SPEAKER_PRESENT
flag
sound/soc/intel/boards/sof_maxim_common.c | 171 +++++++++++++---------
sound/soc/intel/boards/sof_maxim_common.h | 21 ++-
sound/soc/intel/boards/sof_rt5682.c | 37 +----
3 files changed, 112 insertions(+), 117 deletions(-)
--
2.34.1
next reply other threads:[~2023-07-26 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:08 Brent Lu [this message]
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
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=20230726140848.2267568-1-brent.lu@intel.com \
--to=brent.lu@intel.com \
--cc=ajye_huang@compal.corp-partner.google.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.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=pierre-louis.bossart@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®