re: built in functions- set_pwm_duty query

[asmboy]

When trying to associate an action or variable with a given combination of pwm channel and my desired duty cycle - I seem to need to code it awkwardly owing to the different function names associated with the channel

I'm grateful for the clean solid pwm functions I'm using now
but does anybody know why the compiler could not
persuaded to accept input with a syntax of

set_pwm_duty( int channel number, unsigned long duty_cycle_var)

to pass 2 vars instead of one to a buncha different functions? ?

ditto the setup .h files

Is there a sys var or some way to resolve channel differences in a
simple default way?



Is it more than TTWIW?

If so - I am suitably abashed.

[Ttelmah]

You will just have to write a wrapper.
The reason', is size/speed.
The 'functions', are not really functions, but macros, which directly access the registers associated with a single PWM. The setup, just puts the values given, directly into the specified registers, and hence at runtime, are tiny. To make it support multiple channels, adds the test for 'which channel', and requires the 'function', to have code for all the channels present. Not 'huge', but a lot larger than the supplied macros. If you want the flexibility, then all you have to do, is provide this yourself. So something like: