1. 19 10月, 2013 1 次提交
  2. 10 10月, 2013 4 次提交
  3. 26 9月, 2013 1 次提交
  4. 31 8月, 2013 3 次提交
  5. 08 8月, 2013 2 次提交
  6. 14 7月, 2013 1 次提交
  7. 12 6月, 2013 1 次提交
    • A
      drm/radeon: fix AVI infoframe generation · f100380e
      Alex Deucher 提交于
      - remove adding 2 to checksum, this is incorrect.
      
      This was incorrectly introduced in:
      92db7f6c
      http://lists.freedesktop.org/archives/dri-devel/2011-December/017717.html
      However, the off by 2 was due to adding the version twice.
      From the examples in the URL above:
      
      [Rafał Miłecki][RV620] fglrx:
      0x7454: 00 A8 5E 79     R600_HDMI_VIDEOINFOFRAME_0
      0x7458: 00 28 00 10     R600_HDMI_VIDEOINFOFRAME_1
      0x745C: 00 48 00 28     R600_HDMI_VIDEOINFOFRAME_2
      0x7460: 02 00 00 48     R600_HDMI_VIDEOINFOFRAME_3
      ===================
      (0x82 + 0x2 + 0xD) + 0x1F8 = 0x289
      -0x289 = 0x77
      
      However, the payload sum is not 0x1f8, it's 0x1f6.
      00 + A8 + 5E + 00 +
      00 + 28 + 00 + 10 +
      00 + 48 + 00 + 28 +
      00 + 48 =
      0x1f6
      
      Bits 25:24 of HDMI_VIDEOINFOFRAME_3 are the packet version, not part
      of the payload.  So the total would be:
      (0x82 + 0x2 + 0xD) + 0x1f6 = 0x287
      -0x287 = 0x79
      
      - properly emit the AVI infoframe version.  This was not being
      emitted previous which is probably what caused the issue above.
      
      This should fix blank screen when HDMI audio is enabled on
      certain monitors.
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      Cc: Rafał Miłecki <zajec5@gmail.com>
      f100380e
  8. 20 5月, 2013 1 次提交
  9. 24 4月, 2013 3 次提交
  10. 22 4月, 2013 3 次提交
  11. 22 2月, 2013 1 次提交
  12. 20 2月, 2013 1 次提交
  13. 03 10月, 2012 1 次提交
  14. 21 9月, 2012 1 次提交
  15. 21 6月, 2012 1 次提交
    • C
      drm/radeon: apply Murphy's law to the kms irq code v3 · fb98257a
      Christian Koenig 提交于
      1. It is really dangerous to have more than one
         spinlock protecting the same information.
      
      2. radeon_irq_set sometimes wasn't called with lock
         protection, so it can happen that more than one
         CPU would tamper with the irq regs at the same
         time.
      
      3. The pm.gui_idle variable was assuming that the 3D
         engine wasn't becoming idle between testing the
         register and setting the variable. So just remove
         it and test the register directly.
      
      v2: Also handle the hpd irq code the same way.
      v3: Rename hpd parameter for clarification.
      Signed-off-by: NChristian Koenig <christian.koenig@amd.com>
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      fb98257a
  16. 16 6月, 2012 1 次提交
  17. 05 6月, 2012 1 次提交
  18. 22 5月, 2012 1 次提交
  19. 17 5月, 2012 1 次提交
  20. 13 5月, 2012 6 次提交
  21. 01 5月, 2012 4 次提交
  22. 24 4月, 2012 1 次提交