Jaroslav Kysela

BTW: Another way may be to add a new start argument to snd_hdac_stream_timecounter_init and do just timestamp when this argument is false. This will catch all hda_controller code uses.

Resolved in https://github.com/tiwai/sound/commit/df5215618fbe425875336d3a2d31bd599ae8c401 .

Attach output from `alsa-info.sh --no-upload`. Also try to turn on (unmute) spdif or digital output in alsamixer or amixer.

Some hints: Look to https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/DEBUG.md For HDA driver - we have complete UCM config, but it's used only for new hardware (SOF/AMD) - https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/HDA/HDA.conf , https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/HDA/HiFi-analog.conf . So, to use...

> ALSA_CONFIG_UCM2 It should work. > named snd_hda_codec or snd_hda_codec_realtek or snd_hda_codec_hdmi I mean why was this snd dropped in the first place and stuff in conf.d starts with hda...

And... https://www.alsa-project.org/alsa-doc/alsa-lib/group__ucm__conf.html

Show `amixer -c 0 contents` for the mentioned headset (replace zero with the correct card number). It looks like a driver issue.

The dB values reported by device are totally bogus: ``` numid=4,iface=MIXER,name='PCM Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=128,step=0 : values=62,62 | dBminmax-min=-0.50dB,max=0.00dB ``` The correct values are like: ``` numid=6,iface=MIXER,name='Mic Capture Volume' ;...

I've tried to solve the zero HDMI device issue in https://github.com/perexg/alsa-ucm-conf/commit/0b550766cacbd0924671ccd74396709d84953aae . Could you give a test, please? It would be also nice to move the old configs to separate...

The update HDMI configuration file should work: https://github.com/perexg/alsa-ucm-conf/commit/b4e8a04694a2f8188fcc94f9615c05ba8fb38b50 > Regarding DMIC does it make sense to merge it with other card, when it is separate card and device? We expose...