diff options
author | Jesse Barnes <jbarnes@virtuousgeek.org> | 2009-01-12 12:05:32 -0800 |
---|---|---|
committer | Dave Airlie <airlied@linux.ie> | 2009-01-16 18:40:54 +1000 |
commit | 40a518d9f1fd8ed1061b8b4e2ce8a44794f4eb03 (patch) | |
tree | c085ac55dadbd78024b06a052f73e097777858b5 /arch | |
parent | 3a03ac1a0223f779a3de313523408ddb099e5679 (diff) |
drm: initial KMS config fixes
When mode setting is first initialized, the driver will call into
drm_helper_initial_config() to set up an initial output and framebuffer
configuration. This routine is responsible for probing the available
connectors, encoders, and crtcs, looking for modes and putting together
something reasonable (where reasonable is defined as "allows kernel
messages to be visible on as many displays as possible").
However, the code was a bit too aggressive in setting default modes when
none were found on a given connector. Even if some connectors had modes,
any connectors found lacking modes would have the default 800x600 mode added
to their mode list, which in some cases could cause problems later down the
line. In my case, the LVDS was perfectly available, but the initial config
code added 800x600 modes to both of the detected but unavailable HDMI
connectors (which are on my non-existent docking station). This ended up
preventing later code from setting a mode on my LVDS, which is bad.
This patch fixes that behavior by making the initial config code walk
through the connectors first, counting the available modes, before it decides
to add any default modes to a possibly connected output. It also fixes the
logic in drm_target_preferred() that was causing zeroed out modes to be set
as the preferred mode for a given connector, even if no modes were available.
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@linux.ie>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions