From: Sataporn Saijai <excursively@gmail.com>
To: "Liao, Bard" <bard.liao@intel.com>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ujfalusi, Peter" <peter.ujfalusi@intel.com>
Subject: Re: [PATCH] ASoC: Intel: soc-acpi-intel-ptl-match: add rt721_l3_rt1320_l3
Date: Mon, 17 Aug 2026 16:00:34 +0700 [thread overview]
Message-ID: <CAHgGaxy-GQJLiXtO2LZkMzVi9ehemyMTj8JbajeokzdRsNTNbQ@mail.gmail.com> (raw)
In-Reply-To: <SJ2PR11MB8424EA2C7382EBE3D914FA05FFA72@SJ2PR11MB8424.namprd11.prod.outlook.com>
On Mon, Aug 17, 2026 at 11:42 AM Liao, Bard <bard.liao@intel.com> wrote:
> Can you add the SKU to drivers/soundwire/dmi-quirks.c?
> Like 4dab2b904414 ("soundwire: dmi-quirks: Disable ghost Realtek devices ")
Done. ghost_realtek already has the exact address, so only the DMI match
for 83QM was needed. Tested - the RT722 no longer appears under
/sys/bus/soundwire/devices/. Will send as patch 1/2 in v2.
> Can you check if c8f3c9fa75ff ("ASoC: soc-acpi / SOF: Add best_effort
> flag to get_function_tplg_files op ") is in your kernel?
> In theory, it will skip the BT link and will load other function
> topologies.
It is in my tree (7.2.0-rc7), but best_effort is only ever set from the
topology name:
topology.c: bool no_fallback = strstr(file, "dummy");
With a real sof_tplg_filename it is false, so sof_sdw_get_tplg_files()
returns 0 at SSP2-BT instead of skipping it, and the card fails to probe.
The comment above that line describes 'dummy' as meaning no monolithic
fallback exists, which is the case here - so I think it is the intended
mechanism, though this would be the first machine entry to use it. Happy
to do it differently if you prefer.
Thanks,
Sataporn
next prev parent reply other threads:[~2026-08-17 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 18:27 Sataporn
2026-08-17 4:42 ` Liao, Bard
2026-08-17 9:00 ` Sataporn Saijai [this message]
2026-08-17 15:56 ` Mark Brown
2026-08-18 3:53 ` Sataporn Saijai
2026-08-18 15:01 ` Mark Brown
2026-08-18 18:24 ` Sataporn Saijai
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=CAHgGaxy-GQJLiXtO2LZkMzVi9ehemyMTj8JbajeokzdRsNTNbQ@mail.gmail.com \
--to=excursively@gmail.com \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@intel.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--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®