From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
tiwai@suse.de, Brent Lu <brent.lu@intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 2/4] ASoC: Intel: maxim-common: add max_98373_get_tx_mask function
Date: Mon, 24 Jun 2024 17:26:37 +0200 [thread overview]
Message-ID: <9394ab7c-d628-489b-9b88-66eb11fca0d7@linux.intel.com> (raw)
In-Reply-To: <f3b5caee-a27e-42f9-b541-4f6bf8e8d2f2@sirena.org.uk>
On 6/24/24 14:37, Mark Brown wrote:
> On Mon, Jun 24, 2024 at 02:11:17PM +0200, Pierre-Louis Bossart wrote:
>> From: Brent Lu <brent.lu@intel.com>
>>
>> Add a helper function max_98373_get_tx_mask() to get tx mask from
>> max98373 ACPI device properties at runtime.
>
> Similarly here.
I may have misunderstood Brent's patch but this isn't a fix really, more
a cleanup to use ACPI when possible, with a fallback to the existing
hard-coded setup if ACPI properties are not found.
I don't think it's a real 'fix' impacting users, in the linux-stable
sense, nor that this needs to be back-ported with case.
Brent, please chime in if I am mistaken?
next prev parent reply other threads:[~2024-06-24 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 12:11 [PATCH 0/4] ASoC: Intel: boards: updates for 6.11 - part2 Pierre-Louis Bossart
2024-06-24 12:11 ` [PATCH 1/4] ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP Pierre-Louis Bossart
2024-06-24 12:11 ` [PATCH 2/4] ASoC: Intel: maxim-common: add max_98373_get_tx_mask function Pierre-Louis Bossart
2024-06-24 12:37 ` Mark Brown
2024-06-24 15:26 ` Pierre-Louis Bossart [this message]
2024-06-24 15:35 ` Mark Brown
2024-06-24 12:11 ` [PATCH 3/4] ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C Pierre-Louis Bossart
2024-06-24 12:11 ` [PATCH 4/4] ASoC: Intel: sof_sdw: select PINCTRL_CS42L43 and SPI_CS42L43 Pierre-Louis Bossart
2024-06-25 14:54 ` [PATCH 0/4] ASoC: Intel: boards: updates for 6.11 - part2 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=9394ab7c-d628-489b-9b88-66eb11fca0d7@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=linux-sound@vger.kernel.org \
--cc=tiwai@suse.de \
--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