1. 01 5月, 2013 1 次提交
    • V
      drm/i915: Implement proper clipping for video sprites · 1731693a
      Ville Syrjälä 提交于
      Properly clip the source when the destination gets clipped
      by the pipe dimensions.
      
      Sadly the video sprite hardware is rather limited so it can't do proper
      sub-pixel postitioning. Resort to truncating the source coordinates to
      (macro)pixel boundary.
      
      The scaling checks are done using the strict drm_region functions.
      Which means that an error is returned when the min/max scaling
      ratios are exceeded.
      
      Also do some additional checking against various hardware limits.
      
      v2: Truncate src coords instead of rounding to avoid increasing src
          viewport size, and adapt to changes in drm_calc_{h,v}scale().
      v3: Adapt to drm_region->drm_rect rename. Fix misaligned crtc_w for
          packed YUV formats when scaling isn't supported.
      v4: Use stricter scaling checks, use drm_rect_equals()
      v5: If sprite is below min size, make it invisible instead returning
          an error.
          Use WARN_ON() instead if BUG_ON(), and add one to sanity check the
          src viewport size.
      v6: Add comments to remind about src and dst coordinate types
      Reviewed-by: NChris Wilson <chris@chris-wilson.co.uk>
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      1731693a
  2. 25 4月, 2013 1 次提交
  3. 03 4月, 2013 1 次提交
  4. 28 3月, 2013 2 次提交
  5. 27 3月, 2013 1 次提交
  6. 22 2月, 2013 1 次提交
  7. 20 2月, 2013 1 次提交
    • V
      drm/i915: Implement pipe CSC based limited range RGB output · 86d3efce
      Ville Syrjälä 提交于
      HSW no longer has the PIPECONF bit for limited range RGB output.
      Instead the pipe CSC unit must be used to perform that task.
      
      The CSC pre offset are set to 0, since the incoming data is full
      [0:255] range RGB, the coefficients are programmed to compress the
      data into [0:219] range, and then we use either the CSC_MODE black
      screen offset bit, or the CSC post offsets to shift the data to
      the correct [16:235] range.
      
      Also have to change the confiuration of all planes so that the
      data is sent through the pipe CSC unit. For simplicity send the
      plane data through the pipe CSC unit always, and in case full
      range output is requested, the pipe CSC unit is set up with an
      identity transform to pass the plane data through unchanged.
      
      I've been told by some hardware people that the use of the pipe
      CSC unit shouldn't result in any measurable increase in power
      consumption numbers.
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Reviewed-by: NPaulo Zanoni <paulo.r.zanoni@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      86d3efce
  8. 15 2月, 2013 1 次提交
  9. 21 1月, 2013 1 次提交
    • D
      drm/i915: use drm_modeset_lock_all · a0e99e68
      Daniel Vetter 提交于
      Two exceptions:
      - debugfs files only read information which is not related to crtc, so
        can stay on the modeset_config lock.
      - Same holds for the edp vdd work in intel_dp.c. Add a corresponding
        WARN_ON and a comment next to the intel_dp struct fields for
        documentation.
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      a0e99e68
  10. 09 1月, 2013 1 次提交
  11. 12 11月, 2012 5 次提交
  12. 27 10月, 2012 1 次提交
  13. 26 10月, 2012 1 次提交
  14. 24 10月, 2012 1 次提交
    • D
      drm/i915: Don't try to use SPR_SCALE when we don't have a sprite scaler · 2d354c34
      Damien Lespiau 提交于
      Haswell does not have a scaler in the sprite pipeline anymore, so let's
      ensure:
        1/ We bail out of update_plate() when someone is trying to ask to
           display a scaled framebuffer,
        2/ We never write to the nonexistent SPR_SCALE register
      
      v2: Smash in the fixup from Damien in the disable_plane function.
      
      Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> (for v1)
      Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org> (for v1)
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      2d354c34
  15. 03 10月, 2012 1 次提交
  16. 23 8月, 2012 1 次提交
  17. 20 7月, 2012 1 次提交
  18. 27 6月, 2012 3 次提交
  19. 14 6月, 2012 1 次提交
  20. 03 5月, 2012 2 次提交
  21. 17 4月, 2012 3 次提交
  22. 13 4月, 2012 1 次提交
  23. 10 4月, 2012 1 次提交
  24. 03 4月, 2012 1 次提交
  25. 08 3月, 2012 1 次提交
  26. 30 1月, 2012 1 次提交
  27. 14 1月, 2012 1 次提交
  28. 05 1月, 2012 1 次提交
    • R
      drm: add support for private planes · 0a7eb243
      Rob Clark 提交于
      In cases where the scanout hw is sufficiently similar between "overlay"
      and traditional crtc layers, it might be convenient to allow the driver
      to create internal drm_plane helper objects used by the drm_crtc
      implementation, rather than duplicate code between the plane and crtc.
      A private plane is not exposed to userspace.
      Signed-off-by: NRob Clark <rob@ti.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      0a7eb243
  29. 04 1月, 2012 2 次提交