1. 07 May, 2012 11 commits
  2. 03 May, 2012 27 commits
  3. 02 May, 2012 2 commits
    • Dave Airlie's avatar
      drm/kms: reduce some messages to debug level (v2) · 1aa1b11c
      Dave Airlie authored
      These can all be trigged from userspace if you pass the right values.
      
      v2: rebase on later kernel.
      Reviewed-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      1aa1b11c
    • Dave Airlie's avatar
      Merge tag 'drm-intel-next-2012-04-23' of... · 5bc69bf9
      Dave Airlie authored
      Merge tag 'drm-intel-next-2012-04-23' of git://people.freedesktop.org/~danvet/drm-intel into drm-core-next
      
      Daniel Vetter writes:
      
      A new drm-intel-next pull. Highlights:
      - More gmbus patches from Daniel Kurtz, I think gmbus is now ready, all
       known issues fixed.
      - Fencing cleanup and pipelined fencing removal from Chris.
      - rc6 residency interface from Ben, useful for powertop.
      - Cleanups and code reorg around the ringbuffer code (Ben&me).
      - Use hw semaphores in the pageflip code from Ben.
      - More vlv stuff from Jesse, unfortunately his vlv cpu is doa, so less
       merged than I've hoped for - we still have the unused function warning :(
      - More hsw patches from Eugeni, again, not yet enabled fully.
      - intel_pm.c refactoring from Eugeni.
      - Ironlake sprite support from Chris.
      - And various smaller improvements/fixes all over the place.
      
      Note that this pull request also contains a backmerge of -rc3 to sort out
      a few things in -next. I've also had to frob the shortlog a bit to exclude
      anything that -rc3 brings in with this pull.
      
      Regression wise we have a few strange bugs going on, but for all of them
      closer inspection revealed that they've been pre-existing, just now
      slightly more likely to be hit. And for most of them we have a patch
      already. Otherwise QA has not reported any regressions, and I'm also not
      aware of anything bad happening in 3.4.
      
      * tag 'drm-intel-next-2012-04-23' of git://people.freedesktop.org/~danvet/drm-intel: (420 commits)
        drm/i915: rc6 residency (fix the fix)
        drm/i915/tv: fix open-coded ARRAY_SIZE.
        drm/i915: invalidate render cache on gen2
        drm/i915: Silence the change of LVDS sync polarity
        drm/i915: add generic power management initialization
        drm/i915: move clock gating functionality into intel_pm module
        drm/i915: move emon functionality into intel_pm module
        drm/i915: move drps, rps and rc6-related functions to intel_pm
        drm/i915: fix line breaks in intel_pm
        drm/i915: move watermarks settings into intel_pm module
        drm/i915: move fbc-related functionality into intel_pm module
        drm/i915: Refactor get_fence() to use the common fence writing routine
        drm/i915: Refactor fence clearing to use the common fence writing routine
        drm/i915: Refactor put_fence() to use the common fence writing routine
        drm/i915: Prepare to consolidate fence writing
        drm/i915: Remove the unsightly "optimisation" from flush_fence()
        drm/i915: Simplify fence finding
        drm/i915: Discard the unused obj->last_fenced_ring
        drm/i915: Remove unused ring->setup_seqno
        drm/i915: Remove fence pipelining
        ...
      5bc69bf9