> > Lionel, Michal, thoughts?
Compute UMD needs to know exact GTT total size.
== Series Details ==
Series: drm/i915/display: Fixed a screen flickering when turning on display
from off (rev5)
URL : https://patchwork.freedesktop.org/series/130780/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14442 -> Patchwork_130780v5
==
The original implementation was 47356eb67285 in Sep 17, 2001. The condition
can't be replicated for now.
The condition for invalid brightness level includes the minimum available
value. It does not make sense. I've added the new condition in rev #5. Please
consider if the condition is workable
From: Gareth Yu
Turn on the panel from zero brightness of the last state, the panel was
set a maximum PWM in the flow. Once the panel initialization is completed,
the backlight is restored to xero brightness. There is a flckering
generated. This flicker happens in "Screen dimming and power off" o
Switch to using drm_driver_legacy_fb_format() instead of
drm_mode_legacy_fb_format() to use the same logic as for the
DRM_IOCTL_MODE_ADDFB ioctl when selecting a framebuffer format.
Signed-off-by: Frej Drejhammar
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Thomas Zimmermann
Cc: David Airlie
C
Switch to using drm_driver_legacy_fb_format() instead of
drm_mode_legacy_fb_format() to use the same logic as for the
DRM_IOCTL_MODE_ADDFB ioctl when selecting a framebuffer format.
Signed-off-by: Frej Drejhammar
Cc: David Airlie
Cc: Daniel Vetter
Cc: intel-gfx@lists.freedesktop.org
Cc: intel..
When userland uses DRM_IOCTL_MODE_ADDFB to add a framebuffer, the DRM
subsystem tries to find a pixel format from the supplied depth and
bpp-values. It does this by calling drm_driver_legacy_fb_format().
Unfortunately drm_driver_legacy_fb_format() can return formats not
supported by the underlying
