linux-toradex.git/drivers/gpu, branch v3.12.33

When screen objects are enabled, the bpp is assumed to be 32, otherwise it is set to 16.

2014-11-14T12:24:17+00:00

v2:
* Use u32 instead of u64 for assumed_bpp.
* Fixed mechanism to check for screen objects
* Limit the back buffer size to VRAM.

v3:
* Backported for 3.12-stable

Signed-off-by: Sinclair Yeh 
Reviewed-by: Thomas Hellstrom 
Cc: 
Signed-off-by: Jiri Slaby

drm/radeon/dpm: disable ulv support on SI

2014-11-13T18:03:04+00:00

commit 6fa455935ab956248b165f150ec6ae9106210077 upstream.

Causes problems on some boards.

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

Signed-off-by: Alex Deucher 
Signed-off-by: Jiri Slaby

qxl: don't create too large primary surface

2014-11-13T18:02:32+00:00

commit c572aaf46f71f63ae5914d4e194a955e0ba1b519 upstream.

Limit primary to qemu vgamem size, to avoid reaching
qemu guest bug "requested primary larger than framebuffer"
on resizing screen too large to fit.

Remove unneeded and misleading variables.

Related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1127552

Signed-off-by: Marc-André Lureau 
Signed-off-by: Dave Airlie 
Signed-off-by: Jiri Slaby

drm/nouveau/bios: memset dcb struct to zero before parsing

2014-11-13T18:02:24+00:00

commit 595d373f1e9c9ce0fc946457fdb488e8a58972cd upstream.

Fixes type/mask calculation being based on uninitialised data for VGA
outputs.

Signed-off-by: Ben Skeggs 
Signed-off-by: Jiri Slaby

drm/ast: Fix HW cursor image

2014-11-13T18:02:24+00:00

commit 1e99cfa8de0f0879091e33cd65fd60418d006ad9 upstream.

The translation from the X driver to the KMS one typo'ed a couple
of array indices, causing the HW cursor to look weird (blocky with
leaking edge colors). This fixes it.

Signed-off-by: Benjamin Herrenschmidt 
Signed-off-by: Dave Airlie 
Signed-off-by: Jiri Slaby

drm/cirrus: bind also to qemu-xen-traditional

2014-11-13T18:02:20+00:00

commit c0c3e735fa7bae29c6623511127fd021b2d6d849 upstream.

qemu as used by xend/xm toolstack uses a different subvendor id.
Bind the drm driver also to this emulated card.

Signed-off-by: Olaf Hering 
Signed-off-by: Dave Airlie 
Signed-off-by: Jiri Slaby

drm/i915: provide interface for audio driver to query cdclk

2014-11-05T09:03:19+00:00

commit c149dcb5c60bfea8871f16dfcc0690255eeb825f upstream.

For Haswell and Broadwell, if the display power well has been disabled,
the display audio controller divider values EM4 M VALUE and EM5 N VALUE
will have been lost. The CDCLK frequency is required for reprogramming them
to generate 24MHz HD-A link BCLK. So provide a private interface for the
audio driver to query CDCLK.

This is a stopgap solution until a more generic interface between audio
and display drivers has been implemented.

Signed-off-by: Jani Nikula 
Reviewed-by: Damien Lespiau 
Signed-off-by: Mengdong Lin 
Cc: 
Signed-off-by: Takashi Iwai 
Signed-off-by: Jiri Slaby

drm/i915, HD-audio: Don't continue probing when nomodeset is given

2014-11-05T09:03:19+00:00

commit 74b0c2d75fb4cc89173944e6d8f9eb47aca0c343 upstream.

When a machine is booted with nomodeset option, i915 driver skips the
whole initialization.  Meanwhile, HD-audio tries to bind wth i915 just
by request_symbol() without knowing that the initialization was
skipped, and eventually it hits WARN_ON() in i915_request_power_well()
and i915_release_power_well() wrongly but still continues probing,
even though it doesn't work at all.

In this patch, both functions are changed to return an error in case
of uninitialized state instead of WARN_ON(), so that HD-audio driver
can give up HDMI controller initialization at the right time.

Acked-by: Daniel Vetter 
Cc:  [3.15]
Signed-off-by: Takashi Iwai 
Signed-off-by: Jiri Slaby

drm/tilcdc: Fix the error path in tilcdc_load()

2014-10-31T14:11:32+00:00

commit b478e336b3e75505707a11e78ef8b964ef0a03af upstream.

The current error path calls tilcdc_unload() in case of an error to release
the resources. However, this is wrong because not all resources have been
allocated by the time an error occurs in tilcdc_load().

To fix it, this commit adds proper labels to bail out at the different
stages in the load function, and release only the resources actually allocated.

Tested-by: Darren Etheridge 
Tested-by: Johannes Pointner 
Signed-off-by: Ezequiel Garcia 
Signed-off-by: Dave Airlie 
Signed-off-by: Jiri Slaby

drm/i915: Flush the PTEs after updating them before suspend

2014-10-13T14:09:19+00:00

commit 91e56499304f3d612053a9cf17f350868182c7d8 upstream.

As we use WC updates of the PTE, we are responsible for notifying the
hardware when to flush its TLBs. Do so after we zap all the PTEs before
suspend (and the BIOS tries to read our GTT).

Fixes a regression from

commit 828c79087cec61eaf4c76bb32c222fbe35ac3930
Author: Ben Widawsky 
Date:   Wed Oct 16 09:21:30 2013 -0700

    drm/i915: Disable GGTT PTEs on GEN6+ suspend

that survived and continue to cause harm even after

commit e568af1c626031925465a5caaab7cca1303d55c7
Author: Daniel Vetter 
Date:   Wed Mar 26 20:08:20 2014 +0100

    drm/i915: Undo gtt scratch pte unmapping again

v2: Trivial rebase.
v3: Fixes requires pointer dances.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=82340
Tested-by: ming.yao@intel.com
Signed-off-by: Chris Wilson 
Cc: Takashi Iwai 
Cc: Paulo Zanoni 
Cc: Todd Previte 
Cc: Daniel Vetter 
Reviewed-by: Daniel Vetter 
Signed-off-by: Jani Nikula 
Signed-off-by: Jiri Slaby