diff options
| author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2018-10-08 16:46:40 +0300 |
|---|---|---|
| committer | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2018-10-09 16:32:55 +0300 |
| commit | 19dfe5726bab6d2ef337b3051d5a96868a875ac4 (patch) | |
| tree | d3a3d799d33bc494cf5bd1ec3b88696861c56ead /tools/perf/scripts/python | |
| parent | 71ffd49cc9b9da5d9e97b5153ee1fe33dfd61a43 (diff) | |
| download | kernel-19dfe5726bab6d2ef337b3051d5a96868a875ac4.tar.gz | |
drm/i915: Do intel_panel_destroy_backlight() later
Currently we destroy the backlight during connector unregistration.
That means the final modeset performed by drm_atomic_helper_shutdown()
will leave the backlight on. We don't want that so let's just move
intel_panel_destroy_backlight() into intel_panel_fini() which gets
called during connector destuction.
We still unregister the user visible backlight device during connector
unregistration.
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20181008134641.24868-1-ville.syrjala@linux.intel.com
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106386
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions