Now function topologies are being used more routinely we are hitting a
couple of issues on some new laptops. Firstly, several laptops ship with
devices in the ACPI which don't physically exist in the laptop, this
confuses the function topology code as it tries to add those into the
card. Add some quirks to ignore these. Secondly, remove some unnecessary
matches and quirk the ones that remain so they only match the laptops
that require them.

Thanks,
Charles

Charles Keepax (3):
  ASoC: soc-acpi-intel-ptl-match: Make Chrome matches conditional
  ASoC: Intel: soc-acpi-intel-ptl-match: Remove unnecessary cs42l43
    match
  soundwire: dmi-quirks: Disable ghost Realtek devices

 drivers/soundwire/dmi-quirks.c                |  35 ++++++
 .../intel/common/soc-acpi-intel-ptl-match.c   | 119 +-----------------
 .../intel/common/soc-acpi-intel-sdca-quirks.c |  16 +++
 .../intel/common/soc-acpi-intel-sdca-quirks.h |   1 +
 4 files changed, 53 insertions(+), 118 deletions(-)

-- 
2.47.3

On Wed, 20 May 2026 17:36:28 +0100, Charles Keepax wrote:
> Update some topology matching for newer laptops
> 
> Now function topologies are being used more routinely we are hitting a
> couple of issues on some new laptops. Firstly, several laptops ship with
> devices in the ACPI which don't physically exist in the laptop, this
> confuses the function topology code as it tries to add those into the
> card. Add some quirks to ignore these. Secondly, remove some unnecessary
> matches and quirk the ones that remain so they only match the laptops
> that require them.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: soc-acpi-intel-ptl-match: Make Chrome matches conditional
      https://git.kernel.org/broonie/sound/c/e0fb794d67f8
[2/3] ASoC: Intel: soc-acpi-intel-ptl-match: Remove unnecessary cs42l43 match
      https://git.kernel.org/broonie/sound/c/45cf24da0a10

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