diff options
| author | Chris Wilson | 2010-08-08 15:28:23 +0200 |
|---|---|---|
| committer | Eric Anholt | 2010-08-09 23:11:28 +0200 |
| commit | 8545423a912cf500009cbadfae57f706cf2b28e8 (patch) | |
| tree | a1b3adb16dbc824ef9b09f2ec2ec1198a4e11d51 /drivers/gpu/drm/i915/intel_display.c | |
| parent | drm/i915: Set up a render context on Ironlake (diff) | |
| download | kernel-qcow2-linux-8545423a912cf500009cbadfae57f706cf2b28e8.tar.gz kernel-qcow2-linux-8545423a912cf500009cbadfae57f706cf2b28e8.tar.xz kernel-qcow2-linux-8545423a912cf500009cbadfae57f706cf2b28e8.zip | |
drm/i915/sdvo: Only set is_lvds if we have a valid fixed mode.
If we have failed to ascertain the fixed mode for the LVDS panel, then
trust the pixel clock ranges reported for the connection when determing
valid modes. This makes intel_sdvo_mode_valid() consistent with
intel_lvds_mode_valid() which is also a no-op is there is no fixed mode
defined. (Since the mode is both validated by SDVO and LVDS, why are
checking against an LVDS fixed mode in SDVO...)
By only defining is_lvds to be true when we actually have an LVDS output
with a fixed mode, we avoid various potential NULL deferences where the
assumption is made that all LVDS outputs have a fixed mode.
References:
Bug 29449 - [Q35] failure to read EDID/vbios for LVDS, no mode => no output
https://bugs.freedesktop.org/show_bug.cgi?id=29449
The primary failure in this bug is not finding the EDID and determining
the correct fixed panel mode. However, this patch should fix the
secondary issue of not enabling any of the standard modes for the panel
either.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Eric Anholt <eric@anholt.net>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_display.c')
0 files changed, 0 insertions, 0 deletions