On 01/27/2017 03:56 PM, Peter Ujfalusi wrote: >> That extra blank/unblank cycle seems a bit user unfriendly? > > most likely this will help: > > diff --git a/drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c b/drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c > index 5ab39e0060f2..d5a21a96ea82 100644 > --- a/drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c > +++ b/drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c > @@ -839,7 +839,7 @@ static int acx565akm_probe(struct spi_device *spi) > bldev->props.max_brightness = max_brightness; > bldev->props.brightness = brightness; > > - acx565akm_bl_update_status(bldev); > + backlight_update_status(bldev); No, it will not. At the end they are going to do the same thing. what does /sys/class/backlight/acx565akm/bl_power and brightness shows right after the modprobes? - Péter -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
