04:33 <tokyovigilante> Just got line-out audio working too, good day!

09:19 <tokyovigilante> Have got the speaker working too, there's a speaker amp enable GPIO, and a headphone detect GPIO. There doesn't seem to be a mechanism in the driver to configure the headphone detection however, adding the speaker amp GPIO to the device tree enables the speaker, but audio is played out both the speaker and headphones in that case

09:21 <tokyovigilante> Seems that CLDO1 powers the amp, would it be a simple as tying the headphone detect GPIO to that amp (ie headphones in, amp power off?) Can you drive a regulator from more than one GPIO, or use one input GPIO to directly toggle another?

09:24 <tokyovigilante> Or do I need to think about ALSA UCM?

09:24 <sdfgsdfs> im not smart enough to actually answer your question, but shouldn't audio sink switching be left up to the operating system? idk how linux does it, but on freebsd that behavior is controlled by a sysctl hw.snd.default_auto

09:31 <tokyovigilante> My understanding on linux is that its the userspace portion of ALSA, based on the various inputs (routes, jacks etc) defined in the driver, but clearly my understanding is pretty limited :) Increasingly pipewire and the pipewire session manager (wireplumber) are taking into account things like bluetooth, VOIP/videoconferencing, silent mode etc, and all done in userspace