1. 16 12月, 2015 1 次提交
  2. 10 12月, 2015 1 次提交
  3. 09 12月, 2015 1 次提交
  4. 08 12月, 2015 2 次提交
  5. 03 12月, 2015 1 次提交
    • P
      drm/i915: introduce is_active/activate/deactivate to the FBC terminology · 0e631adc
      Paulo Zanoni 提交于
      The long term goal is to have enable/disable as the higher level
      functions and activate/deactivate as the lower level functions, just
      like we do for PSR and for the CRTC. This way, we'll run enable and
      disable once per modeset, while update, activate and deactivate will
      be run many times. With this, we can move the checks and code that
      need to run only once per modeset to enable(), making the code simpler
      and possibly a little faster.
      
      This patch is just the first step on the conversion: it starts by
      converting the current low level functions from enable/disable to
      activate/deactivate. This patch by itself has no benefits other than
      making review and rebase easier. Please see the next patches for more
      details on the conversion.
      
      v2:
        - Rebase.
        - Improve commit message (Chris).
      v3: Rebase after changing the patch order.
      Reviewed-by: NChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: NPaulo Zanoni <paulo.r.zanoni@intel.com>
      Link: http://patchwork.freedesktop.org/patch/msgid/
      0e631adc
  6. 02 12月, 2015 1 次提交
  7. 18 11月, 2015 2 次提交
  8. 17 11月, 2015 1 次提交
    • K
      drm/i915/skl: Correct other-pipe watermark update condition check (v2) · e6d90023
      Kumar, Mahesh 提交于
      If ddb allocation for planes in current CRTC is changed, that doesn't
      lead to ddb allocation change for other CRTCs, because our DDB allocation
      is not dynamic according to plane parameters, ddb is allocated according
      to number of CRTC enabled, & divided equally among CTRC's.
      
      In current condition check during Watermark calculation, if number of
      plane/ddb allocation changes for current CRTC, Watermark for other pipes
      are recalculated. But there is no change in DDB allocation of other pipe
      so watermark is also not changed, This leads to warning messages.
      WARN_ON(!wm_changed)
      
      This patch corrects this and check if DDB allocation for pipes is changed,
      then only recalculate watermarks.
      
      v2 (by Matt): Rebased to latest -nightly and fixed a typo
      Signed-off-by: NKumar, Mahesh <mahesh1.kumar@intel.com>
      Reviewed-by(v1): Ville Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      e6d90023
  9. 16 11月, 2015 1 次提交
  10. 02 11月, 2015 1 次提交
  11. 29 10月, 2015 2 次提交
  12. 27 10月, 2015 1 次提交
  13. 22 10月, 2015 6 次提交
  14. 21 10月, 2015 2 次提交
  15. 20 10月, 2015 1 次提交
    • M
      drm/i915/skl: Eliminate usage of pipe_wm_parameters from SKL-style WM (v4) · 024c9045
      Matt Roper 提交于
      Just pull the info out of the state structures rather than staging
      it in an additional set of structures.  To make this more
      straightforward, we change the signature of several internal WM
      functions to take the crtc state as a parameter.
      
      v2:
       - Don't forget to skip cursor planes on a loop in the DDB allocation
         function to match original behavior.  (Ander)
       - Change a use of intel_crtc->active to cstate->active.  They should
         be identical, but it's better to be consistent.  (Ander)
       - Rework more function signatures to pass states rather than crtc for
         consistency. (Ander)
      
      v3:
        - Add missing "+ 1" to skl_wm_plane_id()'s 'overlay' case. (Maarten)
        - Packed formats should pass '0' to drm_format_plane_cpp(), not 1.
          (Maarten)
        - Drop unwanted WARN_ON() for disabled planes when calculating data
          rate for SKL.  (Maarten)
      
      v4:
       - Don't include cursor plane in total relative data rate calculation;
         we've already handled the cursor allocation earlier.
       - Fix 'bytes_per_pixel' calculation braindamage.  Somehow I hardcoded
         the NV12 format as a parameter rather than the actual
         fb->pixel_format, and even then still managed to get the format plane
         wrong.  (Ville)
       - Use plane->state->fb rather than plane->fb in
         skl_allocate_pipe_ddb(); the plane->fb pointer isn't updated until
         after we've done our watermark recalculation, so it has stale
         values.  (Bob Paauwe)
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by(v3): Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Paauwe, Bob J <bob.j.paauwe@intel.com>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
      References: http://lists.freedesktop.org/archives/intel-gfx/2015-September/077060.html
      References: http://lists.freedesktop.org/archives/intel-gfx/2015-October/077721.html
      Smoke-tested-by(v4): Paulo Zanoni <paulo.r.zanoni@intel.com> (SKL)
      Link: http://patchwork.freedesktop.org/patch/61968/
      024c9045
  16. 13 10月, 2015 2 次提交
  17. 09 10月, 2015 1 次提交
  18. 07 10月, 2015 1 次提交
  19. 06 10月, 2015 1 次提交
  20. 30 9月, 2015 11 次提交