09:36 <jbrunet> chewitt: If the goal is route FRDDR_A to TDMOUT_A then HDMI_TX, of course

09:36 <jbrunet> Have a look at the documentation (EE_AUDIO_FRDDR_A_CTRL_0), the output numbers are the same in the control and the datasheet

09:37 <jbrunet> same applies to the other controls. When in doubt have a look the register doc pointed by the kcontrol

19:03 <khilman> jbrunet: dumb Q Re: audio routing. Can routing be fully described in DT for most boards (for a specific, static set of routes)? Or is there always a need to run some mixer commands to setup routing?

19:05 <jbrunet> DT describe *fully* the wiring and bus format. Mixer sets how things flows through those wires

19:06 <jbrunet> and yes, there is always the need for some mixer. The SoC reset state does not provide any valid, even by luck

19:06 <jbrunet> any valid route

19:07 <jbrunet> the driver expose the HW caps, how it should be used it up to the user

19:08 <jbrunet> alsalib provides tools save and restore these settings easily

19:20 <khilman> TBH, I've always been rather confused by this (just like la-s and chewitt). I think we're missing some basic examples. Any chance you could add a section to linux-meson.com with a static-route mixer example for a couple popular community boards that work with the upstream DTs?

19:20 <khilman> The aslamixer options are not noob friendly either, so a bit of human-readable description of those (with links to the datasheet where appropiate) could go a long way for helping people set this up for new boards.