1. 04 6月, 2014 2 次提交
  2. 02 6月, 2014 5 次提交
  3. 20 4月, 2014 2 次提交
  4. 17 4月, 2014 2 次提交
  5. 08 4月, 2014 1 次提交
  6. 03 4月, 2014 2 次提交
  7. 02 4月, 2014 1 次提交
    • M
      drm: Replace crtc fb with primary plane fb (v3) · f4510a27
      Matt Roper 提交于
      Now that CRTC's have a primary plane, there's no need to track the
      framebuffer in the CRTC.  Replace all references to the CRTC fb with the
      primary plane's fb.
      
      This patch was generated by the Coccinelle semantic patching tool using
      the following rules:
      
              @@ struct drm_crtc C; @@
              -   (C).fb
              +   C.primary->fb
      
              @@ struct drm_crtc *C; @@
              -   (C)->fb
              +   C->primary->fb
      
      v3: Generate patch via coccinelle.  Actual removal of crtc->fb has been
          moved to a subsequent patch.
      
      v2: Fixup several lingering crtc->fb instances that were missed in the
          first patch iteration.  [Rob Clark]
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by: NRob Clark <robdclark@gmail.com>
      f4510a27
  8. 19 2月, 2014 1 次提交
  9. 20 1月, 2014 2 次提交
  10. 25 12月, 2013 1 次提交
    • A
      drm/radeon/pm: move pm handling into the asic specific code · 6c7bccea
      Alex Deucher 提交于
      We need more control over the ordering of dpm init with
      respect to the rest of the asic.  Specifically, the SMC
      has to be initialized before the rlc and cg/pg.  The pm
      code currently initializes late in the driver, but we need
      it to happen much earlier so move pm handling into the asic
      specific callbacks.
      
      This makes dpm more reliable and makes clockgating work
      properly on CIK parts and should help on SI parts as well.
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      6c7bccea
  11. 06 11月, 2013 1 次提交
  12. 02 11月, 2013 2 次提交
  13. 11 9月, 2013 1 次提交
  14. 31 8月, 2013 2 次提交
  15. 30 8月, 2013 1 次提交
  16. 27 6月, 2013 2 次提交
  17. 22 5月, 2013 1 次提交
  18. 01 2月, 2013 1 次提交
  19. 24 1月, 2013 1 次提交
  20. 20 1月, 2013 1 次提交
    • D
      drm/<drivers>: reorder framebuffer init sequence · c7d73f6a
      Daniel Vetter 提交于
      With more fine-grained locking we can no longer rely on the big
      mode_config lock to prevent concurrent access to mode resources
      like framebuffers. Instead a framebuffer becomes accessible to
      other threads as soon as it is added to the relevant lookup
      structures. Hence it needs to be fully set up by the time drivers
      call drm_framebuffer_init.
      
      This patch here is the drivers part of that reorg. Nothing really fancy
      going on safe for three special cases.
      
      - exynos needs to be careful to properly unref all handles.
      - nouveau gets a resource leak fixed for free: one of the error
        cases didn't cleanup the framebuffer, which is now moot since
        the framebuffer is only registered once it is fully set up.
      - vmwgfx requires a slight reordering of operations, I'm hoping I didn't
        break anything (but it's refcount management only, so should be safe).
      
      v2: Split out exynos, since it's a bit more hairy than expected.
      
      v3: Drop bogus cirrus hunk noticed by Richard Wilbur.
      
      v4: Split out vmwgfx since there's a small change in return values.
      
      Reviewed-by: Rob Clark <rob@ti.com> (core + omapdrm)
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      c7d73f6a
  21. 04 1月, 2013 1 次提交
  22. 14 12月, 2012 1 次提交
  23. 03 10月, 2012 1 次提交
  24. 20 7月, 2012 1 次提交
  25. 22 5月, 2012 1 次提交
  26. 17 5月, 2012 2 次提交
  27. 27 4月, 2012 1 次提交