1. 08 8月, 2014 14 次提交
  2. 07 8月, 2014 1 次提交
  3. 21 7月, 2014 1 次提交
  4. 12 7月, 2014 2 次提交
  5. 11 7月, 2014 4 次提交
  6. 10 7月, 2014 1 次提交
    • P
      drm/i915: fix D_COMP usage on BDW · 9ccd5aeb
      Paulo Zanoni 提交于
      On HSW, the D_COMP register can be accessed through the mailbox (read
      and write) or through MMIO on a MCHBAR offset (read only). On BDW, the
      access should be done through MMIO on another address. So to account
      for all these cases, create hsw_read_dcomp() with the correct
      implementation for reading, and also fix hsw_write_dcomp() to do the
      correct thing on BDW.
      
      With this patch, we can now get back from the PC8+ state on BDW. We
      were previously getting a black screen and lots of dmesg errors.
      Please notice that the bug only happens when you actually reach the
      PC8+ states, not when you only allow it.
      
      Testcase: igt/pm_rpm/rte
      Signed-off-by: NPaulo Zanoni <paulo.r.zanoni@intel.com>
      Reviewed-by: NDamien Lespiau <damien.lespiau@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      9ccd5aeb
  7. 09 7月, 2014 2 次提交
  8. 08 7月, 2014 2 次提交
    • B
      drm/i915/bdw: implement semaphore wait · 5ee426ca
      Ben Widawsky 提交于
      Semaphore waits use a new instruction, MI_SEMAPHORE_WAIT. The seqno to
      wait on is all well defined by the table in the previous patch. There is
      nothing else different from previous GEN's semaphore synchronization
      code.
      
      v2: Update macros to not require the other ring's ring->id (Chris)
      
      v3: Add missing VCS2 gen8_ring_wait init besides
          s/ring_buffer/engine_cs (Rodrigo)
      Reviewed-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      Signed-off-by: NBen Widawsky <ben@bwidawsk.net>
      Signed-off-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      5ee426ca
    • B
      drm/i915/bdw: implement semaphore signal · 3e78998a
      Ben Widawsky 提交于
      Semaphore signalling works similarly to previous GENs with the exception
      that the per ring mailboxes no longer exist. Instead you must define
      your own space, somewhere in the GTT.
      
      The comments in the code define the layout I've opted for, which should
      be fairly future proof. Ie. I tried to define offsets in abstract terms
      (NUM_RINGS, seqno size, etc).
      
      NOTE: If one wanted to move this to the HWSP they could. I've decided
      one 4k object would be easier to deal with, and provide potential wins
      with cache locality, but that's all speculative.
      
      v2: Update the macro to not need the other ring's ring->id (Chris)
      Update the comment to use the correct formula (Chris)
      
      v3: Move the macros the ringbuffer.h to prevent churn in next patch
      (Ville)
      
      v4: Fixed compilation rebase conflict
      commit 1ec9e26d
      Author: Daniel Vetter <daniel.vetter@ffwll.ch>
      Date:   Fri Feb 14 14:01:11 2014 +0100
      
          drm/i915: Consolidate binding parameters into flags
      
      v5: VCS2 rebase
      Replace hweight_long with hweight32
      
      v6 (Rodrigo): * Add missed VC2 gen8 ring signal init
         	      * fixing conflicst on rebase
          	      * minor fixes on address table
      	      * remove WARN_ON
      Reviewed-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      Signed-off-by: NBen Widawsky <ben@bwidawsk.net>
      Signed-off-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      [danvet: s/BUG_ON/WARN_ON/]
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      3e78998a
  9. 07 7月, 2014 1 次提交
  10. 18 6月, 2014 1 次提交
  11. 17 6月, 2014 1 次提交
  12. 13 6月, 2014 2 次提交
  13. 11 6月, 2014 8 次提交