1. 27 6月, 2013 5 次提交
  2. 20 5月, 2013 1 次提交
  3. 02 4月, 2013 1 次提交
  4. 06 2月, 2013 1 次提交
  5. 08 12月, 2012 1 次提交
  6. 28 11月, 2012 1 次提交
    • J
      radeon: fix pll/ctrc mapping on dce2 and dce3 hardware · fc58acdb
      Jerome Glisse 提交于
      This fix black screen on resume issue that some people are
      experiencing. There is a bug in the atombios code regarding
      pll/crtc mapping. The atombios code reverse the logic for
      the pll and crtc mapping.
      
      agd5f: drop unnecessary crtc id check, cc stable in case
      we miss 3.7.
      
      This fixes the root cause that was worked around by commits:
      drm/radeon: allocate PPLLs from low to high
      drm/radeon/dce3: switch back to old pll allocation order for discrete
      Signed-off-by: NJerome Glisse <jglisse@redhat.com>
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      fc58acdb
  7. 07 11月, 2012 1 次提交
  8. 16 10月, 2012 1 次提交
  9. 27 9月, 2012 2 次提交
    • A
      drm/radeon: validate PPLL in crtc fixup · c0fd0834
      Alex Deucher 提交于
      This allows us to bail if we can't support the requested
      setup from a PPLL perspective.  Prevents broken setups
      from being attempted.
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      c0fd0834
    • 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
  10. 21 9月, 2012 7 次提交
  11. 18 9月, 2012 1 次提交
  12. 14 9月, 2012 1 次提交
  13. 30 8月, 2012 2 次提交
  14. 22 8月, 2012 1 次提交
  15. 20 8月, 2012 1 次提交
  16. 13 8月, 2012 2 次提交
  17. 20 7月, 2012 1 次提交
  18. 18 7月, 2012 2 次提交
  19. 21 6月, 2012 1 次提交
  20. 28 4月, 2012 1 次提交
  21. 27 4月, 2012 1 次提交
  22. 24 4月, 2012 1 次提交
  23. 26 3月, 2012 1 次提交
  24. 21 3月, 2012 3 次提交