diff options
author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2023-01-20 15:00:17 +0300 |
---|---|---|
committer | Lee Jones <lee@kernel.org> | 2023-02-22 13:55:28 +0300 |
commit | 00e7e698bff1dfdb74da6aff1d80508cdbde25f9 (patch) | |
tree | 59f3fa5dd32f97130591fd1a5858f936e9968205 /tools/perf/scripts/python/stackcollapse.py | |
parent | 744fc2dada5073b8d9822c8c838c8141037ec651 (diff) | |
download | linux-00e7e698bff1dfdb74da6aff1d80508cdbde25f9.tar.xz |
backlight: pwm_bl: Configure pwm only once per backlight toggle
When the function pwm_backlight_update_status() was called with
brightness > 0, pwm_get_state() was called twice (once directly and once
in compute_duty_cycle). Also pwm_apply_state() was called twice (once in
pwm_backlight_power_on() and once directly).
Optimize this to do both calls only once.
Note that with this affects the order of regulator and PWM setup. It's
not expected to have a relevant effect on hardware. The rationale for
this is that the regulator (and the GPIO) are reasonable to switch in
pwm_backlight_power_on()/pwm_backlight_power_off() but the PWM has
nothing to do with power. (The post_pwm_on_delay and pwm_off_delay are
still there though.)
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
Signed-off-by: Lee Jones <lee@kernel.org>
Link: https://lore.kernel.org/r/20230120120018.161103-2-u.kleine-koenig@pengutronix.de
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions