00:35 <Dylanger> Anyone know where the channel definitions are for alsa?

00:35 <Dylanger> It seems to be tripping over how many channels there are `aplay: set_params:1358: Channels count non available`

00:36 <Dylanger> https://github.com/torvalds/linux/blob/5bfc75d92efd494db37f5c4c173d3639d4772966/sound/soc/codecs/max98357a.c#L120

00:36 <Dylanger> I think the definitions are here

00:39 <Dylanger> It's weird tho because it's working, like, it works, so it shouldn't be a driver/kernel/firmware thing

00:40 <broonie> Dylanger: It's going to be whatever the minimum common constraints are between the CPU and the CODEC, plus any additional restrictions from the DSP on a system like the QC SoCs.

00:41 <broonie> It can be that the system has restrictions that come from combinations of settings (eg, picking a sample rate might restrict some of the other settings).

00:43 <Dylanger> The cadmium ucm2 configs work on the Lazor (Trogdor variant), and they all share the same DSP etc

00:43 <broonie> Or that it's reporting the error on channels but actually just the whole config was rejected.

00:43 <Dylanger> Unless I need to specify a codec in the ucm2 config

00:43 <Dylanger> Lol alsa is just a joy 🙃

00:44 <broonie> You shouldn't need to say what the CODEC is (unless it's picking the wrong config I guess). You might need to set additional controls or some different controls if the board is wired up differently or has a different CODEC.

00:45 <Dylanger> Currently that's my ucm2 config

00:47 <Dylanger> Fair, `hw:sc7180rt5682max,1` should be the speaker, `plughw:sc7180rt5682max,1` works with aplay

00:47 <Dylanger> Setting `plughw:sc7180rt5682max,1` in the ucm doesn't work

04:05 <Dylanger> Right

04:05 <Dylanger> Pretty big hw param difference

04:30 <Dylanger> 🤯 you have a Duet 5 schematic?!

04:30 <Dylanger> I feel like this will end up being something silly/small

04:31 <Dylanger> Alsa has to be the most complicated Linux based thing

04:31 <Dylanger> Homestar yeah

04:31 <Dylanger> Is there a way to like, force-set hw params?

04:31 <Dylanger> I can't even find where these are defined

14:24 <broonie> Dylanger: The drivers are the place to force anything that's absolutely required.

14:26 <broonie> If you're having to explicitly set hw_params in userspace that's generally due to the driver telling the apps they can do things that they in fact can't do (main exception is if the app thinks it can use a shorter period than the system can really support).