From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>,
broonie@kernel.org, vkoul@kernel.org
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
peter.ujfalusi@linux.intel.com, oder_chiou@realtek.com,
jack.yu@realtek.com, shumingf@realtek.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 3/3] soundwire: dmi-quirks: Disable ghost Realtek devices
Date: Wed, 20 May 2026 19:16:55 +0200 [thread overview]
Message-ID: <be5dd478-d520-4e7e-a0e2-946b128ec4f2@linux.dev> (raw)
In-Reply-To: <20260520163631.3300102-4-ckeepax@opensource.cirrus.com>
On 5/20/26 18:36, Charles Keepax wrote:
> Many systems ship with a Realtek audio codec in the ACPI that doesn't
> physically exist in the system. This confuses the newer function
> topology system that creates the soundcard, as it builds the card based
> on the ACPI information.
>
> Whilst we are working with the laptop vendors to try and stop this
> happening there are quite a few systems where this has shipped. Add a
> quirk to disable this "ghost" device.
>
> Currently this patch should cover:
> - Asus UX5406AA
> - Lenovo Yoga Pro 9i (83SF)
> - Lenovo Yoga Slim 7 Ultra (83QK)
if this broken ACPI stuff works for Windows then it'll be an uphill battle...
Could we filter instead those 'ghost' devices if they fail to appear in the new ACPI table that describes all the endpoints and card topology?
next prev parent reply other threads:[~2026-05-20 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:36 [PATCH 0/3] Update some topology matching for newer laptops Charles Keepax
2026-05-20 16:36 ` [PATCH 1/3] ASoC: soc-acpi-intel-ptl-match: Make Chrome matches conditional Charles Keepax
2026-05-20 16:36 ` [PATCH 2/3] ASoC: Intel: soc-acpi-intel-ptl-match: Remove unnecessary cs42l43 match Charles Keepax
2026-05-20 16:36 ` [PATCH 3/3] soundwire: dmi-quirks: Disable ghost Realtek devices Charles Keepax
2026-05-20 17:16 ` Pierre-Louis Bossart [this message]
2026-05-21 1:09 ` Liao, Bard
2026-05-21 8:17 ` Charles Keepax
2026-05-21 13:36 ` Pierre-Louis Bossart
2026-05-21 18:18 ` (subset) [PATCH 0/3] Update some topology matching for newer laptops 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=be5dd478-d520-4e7e-a0e2-946b128ec4f2@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=shumingf@realtek.com \
--cc=vkoul@kernel.org \
--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