diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2016-08-19 15:25:41 +0200 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2016-08-26 16:58:37 +0200 |
| commit | 421c98d7d2ebf929debf907e75ec04419cf07dbe (patch) | |
| tree | 066fff4164e808f9f502aaed7b7793eef541b753 /arch/microblaze/include/asm | |
| parent | 8d463c5a32f7d404ee1a0cd68d4746e2ebab9e22 (diff) | |
sunxi: display: Use PWM to drive backlight where applicable
When the backlight's pwm input is connected to a pwm output of the SoC,
actually use pwm to drive the backlight.
The mean reason for doing this is to fix the backlight turning off
for aprox. 1 second while the kernel is booting. This is caused by
the kernel actually using pwm to drive the backlight, so that it
can dim the backlight. First the pwm driver loads and switches the
pinmux for the pin driving the backlight's pwm input to the pwm
controller. Then about 1s later the actual backlight driver loads
and tells the pwm driver to actually update the pwm settings, which
have a power-on-reset value of "off".
An additional advantage is that this allows us to initatiate the
backlight at 80%, which is the kernel default, avoiding a brightness
change while the kernel loads.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'arch/microblaze/include/asm')
0 files changed, 0 insertions, 0 deletions