Skip to content

SOF driver fails on Dell Alienware 18 (Arrow Lake) - duplicate "Speaker Switch" control error with RT722/RT1320 SoundWire codecs #5639

Open

Description

@Botman-Mike

Environment:

System: Dell Alienware 18 Area-51 AA18250
CPU: Intel Arrow Lake-U
Audio Controller: Intel Corporation Device [8086:7f50] (rev 10)
Kernel: 6.14.0-1018-oem #18-Ubuntu SMP PREEMPT_DYNAMIC (Ubuntu 24.04)
SOF Firmware Version: 2.13.0.1
Topology File: intel/sof-ace-tplg/sof-arl-rt722-l0_rt1320-l2.tplg
Codec Detection: RT722-L0, RT1320-L2 (SoundWire)

Problem Description:
The SOF driver successfully loads firmware and detects SoundWire codecs but fails during ALSA card registration with error -EBUSY (error code -16) due to duplicate control "Speaker Switch".
Error Messages from dmesg:
sof-audio-pci-intel-mtl 0000:80:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
sof-audio-pci-intel-mtl 0000:80:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
sof-audio-pci-intel-mtl 0000:80:1f.3: use msi interrupt mode
sof-audio-pci-intel-mtl 0000:80:1f.3: hda codecs found, mask 4
sof-audio-pci-intel-mtl 0000:80:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
sof-audio-pci-intel-mtl 0000:80:1f.3: BT link detected in NHLT tables: 0x4
sof-audio-pci-intel-mtl 0000:80:1f.3: DMICs detected in NHLT tables: 0
sof-audio-pci-intel-mtl 0000:80:1f.3: Firmware paths/files for ipc type 1:
sof-audio-pci-intel-mtl 0000:80:1f.3: Firmware file: intel/sof-ipc4/arl-s/sof-arl-s.ri
sof-audio-pci-intel-mtl 0000:80:1f.3: Firmware lib path: intel/sof-ipc4-lib/arl-s
sof-audio-pci-intel-mtl 0000:80:1f.3: Topology file: intel/sof-ace-tplg/sof-arl-rt722-l0_rt1320-l2.tplg
sof-audio-pci-intel-mtl 0000:80:1f.3: Loaded firmware library: ADSPFW, version: 2.13.0.1
sof-audio-pci-intel-mtl 0000:80:1f.3: Booted firmware version: 2.13.0.1
sof-audio-pci-intel-mtl 0000:80:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
sof_sdw sof_sdw: ASoC: Parent card not yet available, widget card binding deferred
sof_sdw sof_sdw: control 2:0:0:Speaker Switch:0 is already present
sof_sdw sof_sdw: ASoC: Failed to add Speaker Switch: -16
sof_sdw sof_sdw: 0x1320 controls addition failed: -16
sof_sdw sof_sdw: error -EBUSY: snd_soc_register_card failed -16
sof_sdw sof_sdw: probe with driver sof_sdw failed with error -16
Expected Behavior:

SOF driver should successfully register the sound card
Laptop speakers and headphone jack should be functional
Internal microphones should be accessible

Current Workaround:
Using legacy HDA driver (options snd-intel-dspcfg dsp_driver=1) which provides HDMI audio only. No analog audio outputs (speakers/headphone jack) are available with this workaround.
Additional Information:

Audio hardware works correctly in Windows on the same system
HDMI audio works fine with legacy HDA driver in Linux
The error suggests the sof_sdw machine driver is attempting to register the "Speaker Switch" control twice, likely in the topology or machine driver configuration
This appears to be specific to the RT722+RT1320 SoundWire configuration on Arrow Lake platform

Attached Files:

alsa-info.txt (ALSA system information)
Full dmesg output available if needed

Impact:
This affects new Dell Alienware 18 laptops with Arrow Lake processors, making laptop speakers completely non-functional in Linux.

alsa-info.txt

Activity

  1. ranj063 commented on Jan 8, 2026

    @ranj063
    Collaborator

    @bardliao any ideas?

  2. bardliao commented on Jan 8, 2026

    @bardliao
    Collaborator

    @Botman-Mike Thanks for reporting this issue. The duplicated Speaker Switch is due to .widgets = generic_spk_widgets, is set in both rt722 and rt1320 codec info.
    https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/sdw_utils/soc_sdw_utils.c
    I will figure out a way to only register the first one.

  3. bardliao commented on Jan 9, 2026

    @bardliao
    Collaborator

    @Botman-Mike Can you try #5641?

  4. Botman-Mike commented on Jan 12, 2026

    @Botman-Mike
    Author
  5. bardliao commented on Jan 13, 2026

    @bardliao
    Collaborator

    @Botman-Mike No, it is not in a released kernel. You need to get the kernel source of your 6.14.0-1019-oem kernel and cherry pick the commits from #5641 and build the kernel.
    Or you could use the attached kernel.

    But I don't know the required config. It may or may not work on your laptop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions