mbox series

[0/2] ASoC: Intel: don't check number of sdw links when set dmic_fixup

Message ID 20250225093716.67240-1-yung-chuan.liao@linux.intel.com (mailing list archive)
Headers show
Series ASoC: Intel: don't check number of sdw links when set dmic_fixup | expand

Message

Bard Liao Feb. 25, 2025, 9:37 a.m. UTC
Currently, we assume that the PCH DMIC pins are pin-muxed with SoundWire
links. However, we do see a HW design that use PCH DMIC along with 3
SoundWire links. Remove the check and add warning to let users know that
SoundWire MIC and PCH DMIC are both present and they could overwrite it
with kernel params.

Bard Liao (2):
  ASoC: SOF: Intel: don't check number of sdw links when set dmic_fixup
  ASoC: Intel: sof_sdw: warn both sdw and pch dmic are used

 sound/soc/intel/boards/sof_sdw.c |  7 +++++++
 sound/soc/sof/intel/hda.c        | 18 ++----------------
 2 files changed, 9 insertions(+), 16 deletions(-)

Comments

Mark Brown Feb. 25, 2025, 7:32 p.m. UTC | #1
On Tue, 25 Feb 2025 17:37:14 +0800, Bard Liao wrote:
> Currently, we assume that the PCH DMIC pins are pin-muxed with SoundWire
> links. However, we do see a HW design that use PCH DMIC along with 3
> SoundWire links. Remove the check and add warning to let users know that
> SoundWire MIC and PCH DMIC are both present and they could overwrite it
> with kernel params.
> 
> Bard Liao (2):
>   ASoC: SOF: Intel: don't check number of sdw links when set dmic_fixup
>   ASoC: Intel: sof_sdw: warn both sdw and pch dmic are used
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: SOF: Intel: don't check number of sdw links when set dmic_fixup
      commit: 56a677293509b2a0d39ac8d02b583c1ab1fe4d94
[2/2] ASoC: Intel: sof_sdw: warn both sdw and pch dmic are used
      commit: 4bcef04ca67fa8c46591a211885bb9c37f25dbbd

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark