1. 11 1月, 2010 2 次提交
  2. 09 12月, 2009 1 次提交
    • Z
      drm: disable all the possible outputs/crtcs before entering KMS mode · b16d9acb
      Zhao Yakui 提交于
      Sometimes we will use a crtc for integerated LVDS, which is different with
      that assigned by BIOS. If we want to get flicker-free transitions,
      then we could read out the current state for it and set our current state
      accordingly.
      
      But it is true that if we aren't reading current state out, we do need
      to turn everything off before modesetting.  Otherwise the clocks can get very
      angry and we get things worse than a flicker at boot.
      In fact we also do the similar thing in UMS mode. We will disable all the
      possible outputs/crtcs for the first modesetting.
      
      So we disable all the possible outputs/crtcs before entering the KMS mode.
      Before we configure connector/encoder/crtc, the function of
      drm_helper_disable_unused_function can disable all the possible outputs/crtcs.
      Signed-off-by: NZhao Yakui <yakui.zhao@intel.com>
      Reviewed-by: NEric Anholt <eric@anholt.net>
      Reviewed-by: NRafal Milecki <zajec5@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      b16d9acb
  3. 24 11月, 2009 1 次提交
  4. 10 11月, 2009 1 次提交
  5. 26 9月, 2009 1 次提交
  6. 25 9月, 2009 1 次提交
    • D
      drm/kms: start adding command line interface using fb. · d50ba256
      Dave Airlie 提交于
      [note this requires an fb patch posted to linux-fbdev-devel already]
      
      This uses the normal video= command line option to control the kms
      output setup at boot time. It is used to override the autodetection
      done by kms.
      
      video= normally takes a framebuffer as the first parameter, in kms
      it will take a connector name, DVI-I-1, or LVDS-1 etc. If no output
      connector is specified the mode string will apply to all connectors.
      
      The mode specification used will match down the probed modes, and if
      no mode is found it will add a CVT mode that matches.
      
      video=1024x768 - all connectors match a 1024x768 mode or add a CVT on
      video=VGA-1:1024x768, VGA-1 connector gets mode only.
      
      The same strings as used in current fb modedb.c are used, except I've
      added three more letters, e, D, d, e = enable, D = enable Digital,
      d = disable, which allow a connector to be forced into a certain state.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      d50ba256
  7. 18 9月, 2009 1 次提交
  8. 08 9月, 2009 1 次提交
  9. 07 9月, 2009 2 次提交
  10. 02 9月, 2009 3 次提交
  11. 31 8月, 2009 2 次提交
  12. 04 8月, 2009 2 次提交
  13. 11 7月, 2009 1 次提交
  14. 04 6月, 2009 1 次提交
    • K
      drm: Hook up DPMS property handling in drm_crtc.c. Add drm_helper_connector_dpms. · c9fb15f6
      Keith Packard 提交于
      Making the drm_crtc.c code recognize the DPMS property and invoke the
      connector->dpms function doesn't remove any capability from the driver while
      reducing code duplication.
      
      That just highlighted the problem with the existing DPMS functions which
      could turn off the connector, but failed to turn off any relevant crtcs. The
      new drm_helper_connector_dpms function manages all of that, using the
      drm_helper-specific crtc and encoder dpms functions, automatically computing
      the appropriate DPMS level for each object in the system.
      
      This fixes the current troubles in the i915 driver which left PLLs, pipes
      and planes running while in DPMS_OFF mode or even while they were unused.
      Signed-off-by: NKeith Packard <keithp@keithp.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      c9fb15f6
  15. 24 4月, 2009 1 次提交
  16. 03 4月, 2009 2 次提交
  17. 25 2月, 2009 1 次提交
  18. 20 2月, 2009 2 次提交
  19. 16 1月, 2009 2 次提交
    • J
      drm: handle depth & bpp changes correctly · 712531bf
      Jesse Barnes 提交于
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      712531bf
    • J
      drm: initial KMS config fixes · 40a518d9
      Jesse Barnes 提交于
      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: NJesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      40a518d9
  20. 29 12月, 2008 4 次提交