I 'm now confused about why these parameters were designed and how can we implement them.
In my understanding, the actual controller output the predefined behavior in the form of control groups like main and aux. Then the PWM driver take over the responsibility to receive these abstract control signals which is under its power and send them to mixers to get what they finally should output per channel.
Thus, what mixers have done made all of the channels fall back to a flat level, without any abstract meanings from actual controller. They should be defined as pure CH0~CHx, but not Main0~8 or something like AUX0~8. Because this is done by mixer. PWM drivers only want to know the correct frequency and the range of pulse width.
BTW, I haven’ t found a driver in tree have full compatibility to these params.
This question exists for a long time but seems not very critical. But this new issue put forward the PWM related definitions again. I think It is not a defect of a single driver but, a big architecture problem. Because I really can not come up with a solution to produce such a driver with full params implemented. Any suggestions?