04:09 <bamse> konradybcio: do you have working ipa on Sagami?

06:21 <konradybcio> With this commit yes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=27df68d579c67ef6c39a5047559b6a7c08c96219 bamse

09:05 <srinik> calebccff: those messages are saying that SLIM_RX2/3 channels are already associated with a dai and you can not assign them to a different dai. This was bug in previous code now we do a check before assigning a channel to a dai

09:28 <srinik> steev:I can say for sure that ucm2 did not pick up the correct configs as we can see "QUAT_MI2S_RX Audio Mixer MultiMedia1 numid 319 1".

09:29 <srinik> steev: i have pushed a update to link in this patch https://git.linaro.org/people/srinivas.kandagatla/alsa-ucm-conf.git/commit/?h=v1.2.5/c630&id=680e3ecc8ab6cb3402edba3998220e8bd7e67134 can you give it a try

16:11 <steev> srinik: that does help... let me get to a boot where i don't blue screen to actually test

16:12 <steev> i still blame pipewire

16:18 <steev> srinik: still does 3 audible pops at the start, however the startup sound *does* play, however it only plays out of the left speaker

16:19 <srinik> steev: with volume control you should be able to adjust volume for both speakers

16:21 <steev> i have right set to 90%, left to 50%,

16:22 <steev> and no audio when i run canberra-gtk-play -i desktop-login

16:22 <steev> well, some popping

16:23 <srinik> steev:I need to debug the popping issue, I know its due to discharge of COMP soundwire port

16:23 <steev> at least we are on the right track now :D

16:24 <srinik> steev: you should also notice that headset volume control is bit loud so never try it with 100% set

16:25 <steev> oh that is good to know

16:26 <srinik> steev: now we can play different streams in both speakers and headset

16:35 <steev> oh that's cool, i don't actually have a headset to plug in, at least, that i can easily find

17:23 <steev> srinik: coming back from suspend, https://paste.debian.net/1220084 i get a lot of dai_prepare failed

17:24 <srinik> steev: how can I reproduce this issue?

17:26 <steev> good question, all i did was let gnome suspend because of > 5 minutes of idle, and then unsuspended, so i guess, assuming your system is set up to suspend on lid close, just close it, wait about 10 seconds and then wake it up by opening it back up? it might be the comp thing you mentioned because it was popping a lot, and eventually stopped

17:28 <srinik> steev:okay.. I can try "systemctl suspend" or try it with /sys/power/state.. From the logs it suggests that the mixers are not setup in resume path

17:28 <steev> si

17:29 <steev> i use systemctl suspend with sway but i was in gnome at the time because my sway setup is back to basics and i don't have it set up to suspend

17:32 <srinik> steev: I also see CMD 10bcd timeout which might be the 10 sec wait that you described. this is ASM_STREAM_CMD_CLOSE command to dsp. I will debug bit more on this on monday and get back to you if I find any thing interesting

17:32 <steev> no rush, the audio mostly works, and i'm okay with that :D

17:32 <steev> can play youtube videos in chromium as well

17:35 <steev> thank you so much for the work you've done so far, i really do appreciate it

17:36 <srinik> steev: thanks for testing..

17:37 <steev> the c630 is my daily driver :)

17:59 <steev> srinik: please don't judge me too harshly for this.... but, i've found a video on youtube that causes issues... https://youtu.be/WMweEpGlu_U

18:01 <steev> other issue i found... pavucontrol launching to change volume while video is playing (.e.g the video above) seems to kill audio - nothing in dmesg, it just ends up popping a bit

18:05 <steev> https://bpa.st/P5BA is what firefox shows on the console, not sure if that means anything

18:06 <steev> interestingly enough, attempting to launch pavucontrol after that seems to claim it can't connect to pulse, but pipewire-pulse is definitely running