summaryrefslogtreecommitdiffstats
path: root/lib/hweight.c
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2018-04-24 16:02:50 +0300
committerSean Paul <seanpaul@chromium.org>2018-04-25 15:03:13 -0400
commit1f6b8eef11c3d097bc8a6b2bbb868eb47ec6f7d8 (patch)
tree733fe38821e2be7a500a37560987e8c2a29f812c /lib/hweight.c
parentd02d270014f70dcab0117776b81a37b6fca745ae (diff)
downloadlinux-stable-1f6b8eef11c3d097bc8a6b2bbb868eb47ec6f7d8.tar.gz
linux-stable-1f6b8eef11c3d097bc8a6b2bbb868eb47ec6f7d8.tar.bz2
linux-stable-1f6b8eef11c3d097bc8a6b2bbb868eb47ec6f7d8.zip
drm/edid: Reset more of the display info
We're currently failing to reset everything in display_info.hdmi which will potentially cause us to use stale information when swapping monitors. Eg. if the user replaces a HDMI 2.0 monitor with a HDMI 1.x monitor we will continue to think that the monitor supports scrambling. That will lead to a black screen since the HDMI 1.x monitor won't understand the scrambled signal. Fix the problem by clearing display_info.hdmi fully. And while at eliminate some duplicated code by calling drm_reset_display_info() in drm_add_display_info(). Cc: stable@vger.kernel.org Cc: Antony Chen <antonychen@qnap.com> Cc: Shashank Sharma <shashank.sharma@intel.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105655 Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180424130250.7028-1-ville.syrjala@linux.intel.com Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Tested-by: Antony Chen <antonychen@qnap.com> Signed-off-by: Sean Paul <seanpaul@chromium.org>
Diffstat (limited to 'lib/hweight.c')
0 files changed, 0 insertions, 0 deletions