From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: linux-sound@vger.kernel.org, vkoul@kernel.org,
broonie@kernel.org, tiwai@suse.de
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
bard.liao@intel.com
Subject: [PATCH 0/3] ASoC/soundwire: remove ghost peripherals from the mach table
Date: Tue, 15 Sep 2026 21:13:24 +0800 [thread overview]
Message-ID: <20260915131327.1783551-1-yung-chuan.liao@linux.intel.com> (raw)
ACPI may report a ghost SoundWire peripheral. It will cause unexpected
error like duplicated links, codec driver can't probe, etc. This series
check the presence of SoundWire peripherals and skip the non-existing
peripherals.
Though it is a SoundWire feature, but the change is mainly in the ASoC.
Can we go through the ASoC tree?
Bard Liao (3):
soundwire: allow drivers to check whether the peripheral is present
soundwire: change sdw_show_ping_status type to int
ASoC: SOF: Intel: wait and verifies the presence of SoundWire
peripherals
drivers/soundwire/bus.c | 23 +++++++++++++----
include/linux/soundwire/sdw.h | 7 +++++-
sound/soc/sof/intel/hda.c | 47 +++++++++++++++++++++++++++++++++--
3 files changed, 69 insertions(+), 8 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-15 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 13:13 Bard Liao [this message]
2026-09-15 13:13 ` [PATCH 1/3] soundwire: allow drivers to check whether the peripheral is present Bard Liao
2026-09-15 17:32 ` Cezary Rojewski
2026-09-15 18:31 ` Pierre-Louis Bossart
2026-09-16 2:50 ` Liao, Bard
2026-09-15 13:13 ` [PATCH 2/3] soundwire: change sdw_show_ping_status type to int Bard Liao
2026-09-15 13:13 ` [PATCH 3/3] ASoC: SOF: Intel: wait and verifies the presence of SoundWire peripherals Bard Liao
2026-09-15 19:08 ` [PATCH 0/3] ASoC/soundwire: remove ghost peripherals from the mach table Pierre-Louis Bossart
2026-09-16 4:08 ` Liao, Bard
2026-10-07 2:25 ` Liao, Bard
2026-10-07 16:37 ` Pierre-Louis Bossart
2026-10-08 3:14 ` Liao, Bard
2026-10-08 17:09 ` Pierre-Louis Bossart
2026-10-12 14:46 ` Liao, Bard
2026-10-18 8:25 ` Pierre-Louis Bossart
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=20260915131327.1783551-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.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@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
/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®