Files
kernel/include/linux
Uwe Kleine-König 71523d1812 pwm: Ensure pwm_apply_state() doesn't modify the state argument
It is surprising for a PWM consumer when the variable holding the
requested state is modified by pwm_apply_state(). Consider for example a
driver doing:

        #define PERIOD 5000000
        #define DUTY_LITTLE 10
        ...
        struct pwm_state state = {
                .period = PERIOD,
                .duty_cycle = DUTY_LITTLE,
                .polarity = PWM_POLARITY_NORMAL,
                .enabled = true,
        };

        pwm_apply_state(mypwm, &state);
        ...
        state.duty_cycle = PERIOD / 2;
        pwm_apply_state(mypwm, &state);

For sure the second call to pwm_apply_state() should still have
state.period = PERIOD and not something the hardware driver chose for a
reason that doesn't necessarily apply to the second call.

So declare the state argument as a pointer to a const type and adapt all
drivers' .apply callbacks.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
2019-09-21 03:25:10 +02:00
..
2019-07-10 09:00:57 -06:00
2019-07-01 08:18:54 -06:00
2019-07-10 09:00:57 -06:00
2019-07-10 09:00:57 -06:00
2019-07-18 09:49:30 +02:00
2019-07-05 21:34:50 +02:00
2019-06-26 13:19:46 -07:00
2019-07-05 15:19:10 -07:00
2019-07-08 19:25:19 -07:00
2019-07-09 14:15:37 -07:00
2019-07-16 19:23:25 -07:00
2019-07-09 14:32:14 -06:00
2019-07-08 10:51:25 +02:00
2019-07-12 11:05:43 -07:00
2019-06-27 21:22:15 +08:00
2019-07-07 11:50:03 +02:00
2019-07-10 09:00:57 -06:00