kernel/linux.git/drivers/pwm, branch v5.15.7

pwm: mtk-disp: Implement atomic API .get_state()

2021-09-02T20:27:46+00:00

Switch the driver to support the .get_state() method. Signed-off-by: Jitao Shi [thierry.reding@gmail.com: add missing linux/bitfield.h include] Signed-off-by: Thierry Reding

pwm: mtk-disp: Fix overflow in period and duty calculation

2021-09-02T20:27:44+00:00

Current calculation for period and high_width may have 64-bit overflow. state->period and rate are u64. rate * state->period will overflow. clk_div = div_u64(rate * state->period, NSEC_PER_SEC) period = div64_u64(rate * state->period, div); high_width = div64_u64(rate * state->duty_cycle, div); This patch is to resolve it by using mul_u64_u64_div_u64(). Signed-off-by: Jitao Shi Signed-off-by: Thierry Reding

pwm: mtk-disp: Implement atomic API .apply()

2021-09-02T20:27:40+00:00

Switch the driver to support the .apply() method. Signed-off-by: Jitao Shi Signed-off-by: Thierry Reding

pwm: mtk-disp: Adjust the clocks to avoid them mismatch

2021-09-02T20:03:43+00:00

The clks "main" and "mm" are prepared in .probe() (and unprepared in .remove()). This results in the clocks being on during suspend which results in unnecessarily increased power consumption. Remove the clock operations from .probe() and .remove(). Add the clk_prepare_enable() in .enable() and the clk_disable_unprepare() in .disable(). Signed-off-by: Jitao Shi [thierry.reding@gmail.com: squashed in fixup patch] Signed-off-by: Thierry Reding

pwm: Make pwmchip_remove() return void

2021-09-02T19:38:56+00:00

Since some time pwmchip_remove() always returns 0 so the return value isn't usefull. Now that all callers are converted to ignore its value the function can be changed to return void. Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding

pwm: sun4i: Don't check the return code of pwmchip_remove()

2021-09-02T19:38:55+00:00

pwmchip_remove() returns always 0. Don't use the value to make it possible to eventually change the function to return void. Also the driver core ignores the return value of sun4i_pwm_remove() and considers the device removed anyhow. So returning early results in a resource leak. Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding

pwm: sifive: Don't check the return code of pwmchip_remove()

2021-09-02T19:38:55+00:00

pwmchip_remove() returns always 0. Don't use the value to make it possible to eventually change the function to return void. Also the driver core ignores the return value of pwm_sifive_remove(). Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding

pwm: samsung: Don't check the return code of pwmchip_remove()

2021-09-02T19:38:54+00:00

pwmchip_remove() returns always 0. Don't use the value to make it possible to eventually change the function to return void. Also the driver core ignores the return value of pwm_samsung_remove() and considers the device removed anyhow. So returning early results in a resource leak. Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding

pwm: renesas-tpu: Don't check the return code of pwmchip_remove()

2021-09-02T19:38:54+00:00

pwmchip_remove() returns always 0. Don't use the value to make it possible to eventually change the function to return void. Also the driver core ignores the return value of tpu_remove(). Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding

pwm: rcar: Don't check the return code of pwmchip_remove()

2021-09-02T19:38:53+00:00

pwmchip_remove() returns always 0. Don't use the value to make it possible to eventually change the function to return void. Also the driver core ignores the return value of rcar_pwm_remove(). Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding