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

drm/vmwgfx: Reorder device takedown somewhat

2015-04-09T11:14:14+00:00

commit 3458390b9f0ba784481d23134798faee27b5f16f upstream.

To take down the MOB and GMR memory types, the driver may have to issue
fence objects and thus make sure that the fence manager is taken down
after those memory types.
Reorder device init accordingly.

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

drm/vmwgfx: Fix fence event code

2015-01-26T13:39:22+00:00

commit 89669e7a7f96be3ee8d9a22a071d7c0d3b4428fc upstream.

The commit "vmwgfx: Rework fence event action" introduced a number of bugs
that are fixed with this commit:

a) A forgotten return stateemnt.
b) An if statement with identical branches.

Reported-by: Rob Clark 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Reviewed-by: Sinclair Yeh 
Signed-off-by: Jiri Slaby

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/vmwgfx: Fix a potential infinite spin waiting for fifo idle

2014-10-13T12:25:36+00:00

commit f01ea0c3d9db536c64d47922716d8b3b8f21d850 upstream.

The code waiting for fifo idle was incorrect and could possibly spin
forever under certain circumstances.

Signed-off-by: Thomas Hellstrom 
Reported-by: Mark Sheldon 
Reviewed-by: Jakob Bornecrantz 
Reivewed-by: Mark Sheldon 
Signed-off-by: Jiri Slaby

drm/vmwgfx: Fix incorrect write to read-only register v2:

2014-07-17T13:04:37+00:00

commit 4e578080ed3262ed2c3985868539bc66218d25c0 upstream.

Commit "drm/vmwgfx: correct fb_fix_screeninfo.line_length", while fixing a
vmwgfx fbdev bug, also writes the pitch to a supposedly read-only register:
SVGA_REG_BYTES_PER_LINE, while it should be (and also in fact is) written to
SVGA_REG_PITCHLOCK.

This patch is Cc'd stable because of the unknown effects writing to this
register might have, particularly on older device versions.

v2: Updated log message.

Cc: Christopher Friedt 
Tested-by: Christopher Friedt 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Jiri Slaby

drm/vmwgfx: Make sure user-space can't DMA across buffer object boundaries v2

2014-05-29T09:38:25+00:00

commit cbd75e97a525e3819c02dc18bc2d67aa544c9e45 upstream.

We already check that the buffer object we're accessing is registered with
the file. Now also make sure that we can't DMA across buffer object boundaries.

v2: Code commenting update.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Jiri Slaby

drm/vmwgfx: correct fb_fix_screeninfo.line_length

2014-05-29T09:38:25+00:00

commit aa6de142c901cd2d90ef08db30ae87da214bedcc upstream.

Previously, the vmwgfx_fb driver would allow users to call FBIOSET_VINFO, but it would not adjust
the FINFO properly, resulting in distorted screen rendering. The patch corrects that behaviour.

See https://bugs.gentoo.org/show_bug.cgi?id=494794 for examples.

Signed-off-by: Christopher Friedt 
Reviewed-by: Thomas Hellstrom 
Signed-off-by: Jiri Slaby

drm/vmwgfx: Fix regression caused by "drm/ttm: make ttm reservation calls behave like reservation calls"

2014-02-13T21:50:24+00:00

commit cf5e3413337309050c05e13dcebe85b7194a21e5 upstream.

The call to ttm_eu_backoff_reservation() as part of an error path would cause
a lock imbalance if the reservation ticket was not initialized. This error is
easily triggered from user-space by submitting a bogus command stream.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Cc: Maarten Lankhorst 
Cc: Jerome Glisse 
Cc: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Resource evict fixes

2013-12-04T19:05:41+00:00

commit ea029c28deadc33d2af4baf26810dd5fc44d4926 upstream.

Fix an error message that was incorrectly blaming device resource id
shortage.

Also make sure we correctly catch resource eviction errors, that
could otherwise lead to evictable resources temporarily not being on the
LRU list.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Don't kill clients on VT switch

2013-10-15T18:46:53+00:00

DRI clients that tried to grab the TTM lock when the master (X server) was
switched away during a VT switch were sent the SIGTERM signal by the
kernel. Fix this so that they are only sent that signal when the master has
exited.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie