Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 08 4月, 2014 1 次提交
  3. 25 3月, 2014 2 次提交
  5. 21 1月, 2014 1 次提交
  7. 20 1月, 2014 1 次提交
  9. 08 1月, 2014 4 次提交
  11. 06 11月, 2013 1 次提交
  13. 02 11月, 2013 2 次提交
  15. 11 9月, 2013 1 次提交
  17. 31 8月, 2013 1 次提交
  19. 09 7月, 2013 1 次提交
  21. 28 6月, 2013 4 次提交
  23. 27 6月, 2013 4 次提交
  25. 20 5月, 2013 1 次提交
  27. 09 4月, 2013 1 次提交
  29. 04 1月, 2013 1 次提交
  31. 03 1月, 2013 1 次提交
  33. 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
  35. 03 10月, 2012 2 次提交
  37. 27 9月, 2012 2 次提交
    • A
      drm/radeon: restore backlight level on resume · bced76f2
      由 Alex Deucher 提交于 
      Restore the backlight level on resume.  Some systems
need to explicitly restore the backlight level on
resume.

Fixes panel resume on my Trinity laptop and may fix the
following bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=43829
https://bugzilla.kernel.org/show_bug.cgi?id=46241Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      bced76f2
    • A
      drm/radeon: work around KMS modeset limitations in PLL allocation (v2) · 57b35e29
      由 Alex Deucher 提交于 
      Since the current KMS API sets the mode independantly on
each crtc, we may end up with resource conflicts.  The PLL
allocation is one of those cases.  In the following example
we have 3 crtcs in use driving 2 DVI connectors and 1 DP
connector.  On the initial kernel modeset for fbdev, the
display topology ends up as follows:

crtc0 -> DP-0
crtc1 -> DVI-0
crtc2 -> DVI-1

Because this is the first modeset, all of the PLLs are
available as none have been assigned.  So we end up with
the following:

crtc0 uses DCPLL
crtc1 uses PPLL2
crtc2 uses PPLL1

When X starts, it assigns a different topology:

crtc0 -> DVI-0
crtc1 -> DP-0
crtc2 -> DVI-1

However, since the KMS API is per crtc, we set the mode on each
crtc independantly.  When it comes time to set the mode on crtc0,
the topology for crtc1 and crtc2 are still intact.  crtc1 and
crtc2 are already assigned PPLL2 and PPLL1 so when it comes time
to set the mode on crtc0, crtc1 and crtc2 have not been torn down
yet, so there appears to be no PLLs available.  In reality, we
are reconfiguring the entire display topology, however, since
each crtc is handled independantly, we don't know that in the
driver at each crtc mode set time.

This patch checks to see if the same connector is being driven by
another crtc, and if so, uses the PLL already associated with it.

v2: store connector in the radeon crtc struct, simplify checking.
Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      57b35e29
  39. 21 9月, 2012 6 次提交
  41. 13 8月, 2012 1 次提交
  43. 20 7月, 2012 1 次提交