Péter Ujfalusi

@perexg , so in theory what we have currently should work and no need to look at UCM? On my system w/ IPC4: ``` numid=23,iface=PCM,name='ELD',device=3 ; type=BYTES,access=r--v----,values=44 : values=0x10,0x00,0x0a,0x00,0x6b,0x42,0x00,0x0f,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x10,0xac,0x93,0xd0,0x44,0x45,0x4c,0x4c,0x20,0x50,0x31,0x39,0x31,0x37,0x53,0x09,0x7f,0x07,0x0d,0x7f,0x07,0x15,0x7f,0x50,0x3d,0x7f,0xc0,0x00 numid=36,iface=PCM,name='Playback...

This is now IPC4 discussion. IPC3 is limited to stereo, that limit on IPC3 is unlikely to be rectified. The ELD/chmap information is identical regardless of the audio driver (HDA...

> IPC4 should behave like legacy HDA (reflect also the equipment capabilities). Yes, eventually. I have several failed attempt to do this. The BE is quite detached (where the ELD...

> > Pipewire does not use ELD info to probe channels supported by the connected equipment for UCM HDMI devices. > > Even if it did, what should it do...

@mirronake, the HDA legacy driver can be forced with `dsp_driver=1`, can you confirm that the issue can be reproduced with this stack?

Interesting: ``` Codec: Realtek ALC245 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0245 Subsystem Id: 0x103c8a29 ``` Looks similar mixup as #5370 , alsos with ALC245+CSC3551 ```...

@mirronake, can you upgrade to a newer kernel? 6.8 is really old, at minimum to 6.9 where https://github.com/thesofproject/linux/commit/33e5e648e6311135e4ada01bcfb6ff54be98926d ("ALSA: hda: cs35l41: Support additional HP Envy Models") https://github.com/thesofproject/linux/commit/aa8e3ef4fe5332c2ce33507e874b20d9c0077c21 ("ALSA: hda/realtek: Add...

@pankhurijain20, can you provide the output of `alsa-info.sh` as first step, then can you try to switch to the legacy HDA stack by adding `options snd_intel_dspcfg dsp_driver=1` to for example...

Can you test with `options snd_intel_dspcfg dsp_driver=1` if the speaker/headset is working or not to rule out SOF stack issue?

> Actually I dont have /etc/modprobe.d/force-legacy-hda.conf yes, you need to create it, then when tested the speaker/headset remove it.