1. 01 10月, 2014 1 次提交
  2. 05 8月, 2014 3 次提交
  3. 02 7月, 2014 1 次提交
  4. 01 7月, 2014 1 次提交
  5. 10 6月, 2014 1 次提交
  6. 04 6月, 2014 2 次提交
  7. 02 6月, 2014 3 次提交
  8. 08 4月, 2014 1 次提交
  9. 25 3月, 2014 2 次提交
  10. 21 1月, 2014 1 次提交
  11. 20 1月, 2014 1 次提交
  12. 08 1月, 2014 4 次提交
  13. 06 11月, 2013 1 次提交
  14. 02 11月, 2013 2 次提交
  15. 11 9月, 2013 1 次提交
  16. 31 8月, 2013 1 次提交
  17. 09 7月, 2013 1 次提交
  18. 28 6月, 2013 4 次提交
  19. 27 6月, 2013 4 次提交
  20. 20 5月, 2013 1 次提交
  21. 09 4月, 2013 1 次提交
  22. 04 1月, 2013 1 次提交
  23. 03 1月, 2013 1 次提交
  24. 23 10月, 2012 1 次提交
    • D
      drm: extract dp link train delay functions from radeon · 1a644cd4
      Daniel Vetter 提交于
      This requires a few changes since that dpcd value is above the
      range currently cached by radeon. I've check the dp specs, and
      above 0xf there's a big gap and nothing that looks like we should
      cache it while a given device is plugged in. It's also the same value
      that i915.ko uses.
      
      Hence extend the various dpcd arrays in the radeon driver, use
      proper symbolic constants where applicable (one place overallocated
      the dpcd array to 25 bytes). Then also drop the rd_interval cache -
      radeon_dp_link_train_init re-reads the dpcd block, so the values we'll
      consume in train_cr and train_ce will always be fresh.
      
      To avoid needless diff-churn, #define the old size of dpcd as the new
      one and keep it around.
      
      v2: Alex Deucher noticed one place where I've forgotten to replace 8
      with DP_RECEIVER_CAP_SIZE.
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      Acked-by: NDave Airlie <airlied@gmail.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      1a644cd4