1. 21 May, 2013 4 commits
    • Paulo Zanoni's avatar
      drm/i915: remove intel_update_linetime_watermarks · 1011d8c4
      Paulo Zanoni authored
      The spec says the linetime watermarks must be programmed before
      enabling any display low power watermarks, but we're currently
      updating the linetime watermarks after we call intel_update_watermarks
      (and only at crtc_mode_set, not at crtc_{enable,disable}). So IMHO the
      best way guarantee the linetime watermarks will be updated before the
      low power watermarks is inside the update_wm function, because it's
      the function that enables low power watermarks. And since Haswell is
      the only platform that has linetime watermarks, let's completely kill
      the "intel_update_linetime_watermarks" abstraction and just use the
      intel_update_watermarks abstraction by creating haswell_update_wm.
      
      For now haswell_update_wm is still calling sandybridge_update_wm, but
      in the future I plan to implement a function specific to Haswell.
      
      v2: - Rename patch
          - Disable LP watermarks before changing linetime WMs (Chris)
          - Add a comment explaining that this is just temporary code.
      Signed-off-by: default avatarPaulo Zanoni <paulo.r.zanoni@intel.com>
      Reviewed-by: default avatarVille Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      1011d8c4
    • Paulo Zanoni's avatar
      drm/i915: ILK, SNB and IVB don't have linetime watermarks · 5a41254e
      Paulo Zanoni authored
      So don't call intel_update_linetime_watermarks from
      ironlake_crtc_mode_set. Only Haswell has these watermarks.
      Signed-off-by: default avatarPaulo Zanoni <paulo.r.zanoni@intel.com>
      Reviewed-by: default avatarVille Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      5a41254e
    • Jesse Barnes's avatar
      drm/i915: add encoder get_config function v5 · 045ac3b5
      Jesse Barnes authored
      We can use this for fetching encoder specific pipe_config state, like
      mode flags, adjusted clock, etc.
      
      Just used for mode flags atm, so we can check the pipe config state at
      mode set time.
      
      v2: get_config when checking hw state too
      v3: fix DVO and LVDS mode flags (Ville)
          get SDVO DTD for flag fetch (Ville)
      v4: use input timings (Ville)
          correct command used (Ville)
          remove gen4 check (Ville)
      v5: get DDI flag config too
      Signed-off-by: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
      Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> (v4)
      Tested-by: Paulo Zanoni <przanoni@gmail.com> (the new hsw ddi stuff)
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      045ac3b5
    • Daniel Vetter's avatar
      Merge tag 'v3.10-rc2' into drm-intel-next-queued · e1b73cba
      Daniel Vetter authored
      Backmerge Linux 3.10-rc2 since the various (rather trivial) conflicts
      grew a bit out of hand. intel_dp.c has the only real functional
      conflict since the logic changed while dev_priv->edp.bpp was moved
      around.
      
      Also squash in a whitespace fixup from Ben Widawsky for
      i915_gem_gtt.c, git seems to do something pretty strange in there
      (which I don't fully understand tbh).
      
      Conflicts:
      	drivers/gpu/drm/i915/i915_reg.h
      	drivers/gpu/drm/i915/intel_dp.c
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      e1b73cba
  2. 20 May, 2013 11 commits
  3. 19 May, 2013 3 commits
  4. 18 May, 2013 22 commits