linux-toradex.git/drivers/gpu/drm, branch v3.18.21

drm/dp-mst: Remove debug WARN_ON

2015-08-19T17:17:44+00:00

[ Upstream commit 42639ba554655c280ae6cb72df0522b1201f2961 ]

Apparently been in there since forever and fairly easy to hit when
hotplugging really fast. I can do that since my mst hub has a manual
button to flick the hpd line for reprobing. The resulting WARNING spam
isn't pretty.

Cc: Dave Airlie 
Cc: stable@vger.kernel.org
Reviewed-by: Thierry Reding 
Reviewed-by: Ander Conselvan de Oliveira 
Signed-off-by: Daniel Vetter 
Signed-off-by: Sasha Levin

drm/radeon/combios: add some validation of lvds values

2015-08-19T17:17:29+00:00

[ Upstream commit 0a90a0cff9f429f886f423967ae053150dce9259 ]

Fixes a broken hsync start value uncovered by:
abc0b1447d4974963548777a5ba4a4457c82c426
(drm: Perform basic sanity checks on probed modes)

The driver handled the bad hsync start elsewhere, but
the above commit prevented it from getting added.

bug:
https://bugs.freedesktop.org/show_bug.cgi?id=91401

Signed-off-by: Alex Deucher 
Cc: stable@vger.kernel.org
Signed-off-by: Sasha Levin

drm/i915: Replace WARN inside I915_READ64_2x32 with retry loop

2015-08-19T17:16:50+00:00

[ Upstream commit ee0a227b7ac6e75f28e10269f81c7ec6eb600952 ]

Since we may conceivably encounter situations where the upper part of the
64bit register changes between reads, for example when a timestamp
counter overflows, change the WARN into a retry loop.

Signed-off-by: Chris Wilson 
Cc: Michał Winiarski 
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Vetter 
Signed-off-by: Sasha Levin

drm: add a check for x/y in drm_mode_setcrtc

2015-08-04T18:27:42+00:00

[ Upstream commit 01447e9f04ba1c49a9534ae6a5a6f26c2bb05226 ]

legacy setcrtc ioctl does take a 32 bit value which might indeed
overflow

the checks of crtc_req->x > INT_MAX and crtc_req->y > INT_MAX aren't
needed any more with this

v2: -polish the annotation according to Daniel's comment

Cc: Daniel Vetter 
Signed-off-by: Zhao Junwang 
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Vetter 
Signed-off-by: Sasha Levin

drm/radeon: add a dpm quirk for Sapphire Radeon R9 270X 2GB GDDR5

2015-08-04T18:27:24+00:00

[ Upstream commit 5dfc71bc44d91d1620505c064fa22b0b3db58a9d ]

bug:
https://bugs.freedesktop.org/show_bug.cgi?id=76490

Signed-off-by: Alex Deucher 
Cc: stable@vger.kernel.org
Signed-off-by: Sasha Levin

drm/radeon: SDMA fix hibernation (CI GPU family).

2015-07-05T14:12:54+00:00

[ Upstream commit 2ba8d1bb8f6b589037f7db1f01144fc80750e8f7 ]

In order for hibernation to reliably work we need to properly turn
off the SDMA block, sadly after numerous attemps i haven't not found
proper sequence for clean and full shutdown. So simply reset both
SDMA block, this makes hibernation works reliably on sea island GPU
family (CI)

Hibernation and suspend to ram were tested (several times) on :
Bonaire
Hawaii
Mullins
Kaveri
Kabini

Cc: stable@vger.kernel.org
Signed-off-by: Jérôme Glisse 
Reviewed-by: Christian König 
Signed-off-by: Alex Deucher 
Signed-off-by: Sasha Levin

drm/radeon: compute ring fix hibernation (CI GPU family) v2.

2015-07-05T14:12:53+00:00

[ Upstream commit 161569deaa03cf3c00ed63352006193f250b0648 ]

In order for hibernation to reliably work we need to cleanup more
thoroughly the compute ring. Hibernation is different from suspend
resume as when we resume from hibernation the hardware is first
fully initialize by regular kernel then freeze callback happens
(which correspond to a suspend inside the radeon kernel driver)
and turn off each of the block. It turns out we were not cleanly
shutting down the compute ring. This patch fix that.

Hibernation and suspend to ram were tested (several times) on :
Bonaire
Hawaii
Mullins
Kaveri
Kabini

Changed since v1:
  - Factor the ring stop logic into a function taking ring as arg.

Cc: stable@vger.kernel.org
Signed-off-by: Jérôme Glisse 
Reviewed-by: Christian König 
Signed-off-by: Alex Deucher 
Signed-off-by: Sasha Levin

drm/dp/mst: take lock around looking up the branch device on hpd irq

2015-07-05T14:12:48+00:00

[ Upstream commit 9eb1e57f564d4e6e10991402726cc83fe0b9172f ]

If we are doing an MST transaction and we've gotten HPD and we
lookup the device from the incoming msg, we should take the mgr
lock around it, so that mst_primary and mstb->ports are valid.

Reviewed-by: Daniel Vetter 
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie 
Signed-off-by: Sasha Levin

drm/dp/mst: make sure mst_primary mstb is valid in work function

2015-07-05T14:12:47+00:00

[ Upstream commit 9254ec496a1dbdddeab50021a8138dc627a8166a ]

This validates the mst_primary under the lock, and then calls
into the check and send function. This makes the code a lot
easier to understand the locking rules in.

Signed-off-by: Daniel Vetter 
Reviewed-by: Daniel Vetter 
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie 
Signed-off-by: Sasha Levin

drm/qxl: Do not leak memory if qxl_release_list_add fails

2015-07-04T03:02:24+00:00

[ Upstream commit 8451cc964c1d193b989c41a44e5e77109cc696f8 ]

If the function fails reference counter to the object is not decremented
causing leaks.
This is hard to spot as it happens only on very low memory situations.

Signed-off-by: Frediano Ziglio 
Cc: stable@vger.kernel.org
Reviewed-by: Dave Airlie 
Signed-off-by: Dave Airlie 
Signed-off-by: Sasha Levin