Skip to contentSkip to conversation

ASoC: SOF: Intel: hda: Do not probe Soundwire in nocodec mode

PATCH In review Peter Ujfalusi 2 participants 2 messages Jun 19, 2025 – Jun 20, 2025

Subsystems (3)
lore
Share & tools
lore

Peter Ujfalusi

author maintainer
#0 lore raw

PATCH 1/1 ASoC: SOF: Intel: hda: Do not probe Soundwire in nocodec mode

Soundwire is not needed for nocodec mode, skip probing it.

---
 sound/soc/sof/intel/hda.c | 5 +++++
 1 file changed, 5 insertions(+)
sound/soc/sof/intel/hda.c +5 -0
index bdfe388da198..5347c433ac8e 100644
@@ -629,6 +629,11 @@ static int hda_init_caps(struct snd_sof_dev *sdev)
 	if (!(interface_mask & BIT(SOF_DAI_INTEL_ALH)))
 		goto skip_soundwire;
 
+	/* Skip SoundWire in nocodec mode */
+	if (IS_ENABLED(CONFIG_SND_SOC_SOF_NOCODEC_DEBUG_SUPPORT) &&
+	    sof_debug_check_flag(SOF_DBG_FORCE_NOCODEC))
+		goto skip_soundwire;
+
 	/* scan SoundWire capabilities exposed by DSDT */
 	ret = hda_sdw_acpi_scan(sdev);
 	if (ret < 0) {
Signature · 1 line
2.49.0
maintainer
#1 lore raw
Quoted 3 lines · Peter Ujfalusi

Soundwire is not needed for nocodec mode, skip probing it.

Applied to

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

Thanks!

[1/1] ASoC: SOF: Intel: hda: Do not probe Soundwire in nocodec mode

      commit: ce4b269c26ac3216da44ef7699ee61791e6fcbc7

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