1. 25 Aug, 2015 3 commits
  2. 21 Aug, 2015 2 commits
    • Alex Deucher's avatar
      drm/amdgpu: Don't link train DisplayPort on HPD until we get the dpcd · a887adad
      Alex Deucher authored
      This is a port of:
      DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd
      to amdgpu.
      Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      a887adad
    • Stephen Chandler Paul's avatar
      DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd · 924f92bf
      Stephen Chandler Paul authored
      Most of the time this isn't an issue since hotplugging an adaptor will
      trigger a crtc mode change which in turn, causes the driver to probe
      every DisplayPort for a dpcd. However, in cases where hotplugging
      doesn't cause a mode change (specifically when one unplugs a monitor
      from a DisplayPort connector, then plugs that same monitor back in
      seconds later on the same port without any other monitors connected), we
      never probe for the dpcd before starting the initial link training. What
      happens from there looks like this:
      
      	- GPU has only one monitor connected. It's connected via
      	  DisplayPort, and does not go through an adaptor of any sort.
      
      	- User unplugs DisplayPort connector from GPU.
      
      	- Change in HPD is detected by the driver, we probe every
      	  DisplayPort for a possible connection.
      
      	- Probe the port the user originally had the monitor connected
      	  on for it's dpcd. This fails, and we clear the first (and only
      	  the first) byte of the dpcd to indicate we no longer have a
      	  dpcd for this port.
      
      	- User plugs the previously disconnected monitor back into the
      	  same DisplayPort.
      
      	- radeon_connector_hotplug() is called before everyone else,
      	  and tries to handle the link training. Since only the first
      	  byte of the dpcd is zeroed, the driver is able to complete
      	  link training but does so against the wrong dpcd, causing it
      	  to initialize the link with the wrong settings.
      
      	- Display stays blank (usually), dpcd is probed after the
      	  initial link training, and the driver prints no obvious
      	  messages to the log.
      
      In theory, since only one byte of the dpcd is chopped off (specifically,
      the byte that contains the revision information for DisplayPort), it's
      not entirely impossible that this bug may not show on certain monitors.
      For instance, the only reason this bug was visible on my ASUS PB238
      monitor was due to the fact that this monitor using the enhanced framing
      symbol sequence, the flag for which is ignored if the radeon driver
      thinks that the DisplayPort version is below 1.1.
      Signed-off-by: default avatarStephen Chandler Paul <cpaul@redhat.com>
      Reviewed-by: default avatarJerome Glisse <jglisse@redhat.com>
      Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      924f92bf
  3. 20 Aug, 2015 14 commits
  4. 19 Aug, 2015 1 commit
    • Dave Airlie's avatar
      Merge branch 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux into drm-next · e2a8986f
      Dave Airlie authored
      amdgpu and radeon changes for 4.3. Highlights:
      - Fiji support for amdgpu.
      - CGS support for amdgpu.  This is a new driver
        internal cross-component API.
      - Initial GPU scheduler for amdgpu.  Still disabled
        by default.
      - Lots of bug fixes and optimizations
      
      * 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux: (130 commits)
        drm/amdgpu: wait on page directory changes. v2
        drm/amdgpu: Select BACKLIGHT_LCD_SUPPORT
        drm/radeon: Select BACKLIGHT_LCD_SUPPORT
        drm/amdgpu: cleanup sheduler rq handling v2
        drm/amdgpu: move prepare work out of scheduler to cs_ioctl
        drm/amdgpu: fix unnecessary wake up
        drm/amdgpu: fix duplicated mapping invoke bug
        drm/amdgpu: drop bo_list_clone when no scheduler
        drm/amdgpu: disable GPU reset by default
        drm/amdgpu: fix type mismatch error
        drm/amdgpu: add reference for **fence
        drm/amdgpu: fix waiting for all fences before flipping
        drm/amdgpu: fix UVD return code checking
        drm/amdgpu: remove scheduler fence list v2
        drm/amdgpu: remove amd_sched_wait_emit v2
        drm/amdgpu: remove unecessary scheduler fence callbacks
        drm/amdgpu: fix scheduler fence implementation
        drm/amdgpu: don't grab dev->struct_mutex in pm functions
        drm/amdgpu: Don't take dev->struct_mutex in bo_force_delete
        drm/radeon: Don't take dev->struct_mutex in pm functions
        ...
      e2a8986f
  5. 18 Aug, 2015 6 commits
  6. 17 Aug, 2015 14 commits