linux.git/drivers/gpu, branch v3.18-rc3

drm/exynos: correct connector->dpms field before resuming

2014-11-02T16:51:28+00:00

During system suspend after connector switch off its dpms field
is set to connector previous dpms state. To properly resume dpms field
should be set to its actual state (off) before resuming to previous dpms state.

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/exynos: enable vblank after DPMS on

2014-11-02T16:51:28+00:00

Before DPMS off driver disables vblank.
It should be balanced by vblank enable after DPMS on.
The patch fixes issue with page_flip ioctl not being able
to acquire vblank counter introduced by patch:
drm: Always reject drm_vblank_get() after drm_vblank_off()

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/exynos: init kms poll at the end of initialization

2014-11-02T16:51:28+00:00

HPD events can be generated by components even if drm_dev is not fully
initialized, to skip such events kms poll initialization should
be performed at the end of load callback followed directly by forced
connection detection.

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/exynos: propagate plane initialization errors

2014-11-02T16:51:28+00:00

In case of error during plane initialization load callback
incorrectly return success, this patch fixes it.

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/exynos: vidi: fix build warning

2014-11-02T16:51:27+00:00

encoder object isn't used anymore so remove it.

Signed-off-by: Inki Dae

drm/exynos: remove explicit encoder/connector de-initialization

2014-11-02T16:51:27+00:00

All KMS objects are destroyed by drm_mode_config_cleanup in proper order
so component drivers should not care about it.

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/exynos: init vblank with real number of crtcs

2014-11-02T16:51:27+00:00

Initialization of vblank with MAX_CRTC caused attempts
to disabling vblanks for non-existing crtcs in case
drm used fewer crtcs. The patch fixes it.

Signed-off-by: Andrzej Hajda 
Signed-off-by: Inki Dae

drm/vmwgfx: Filter out modes those cannot be supported by the current VRAM size.

2014-10-31T08:58:06+00:00

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

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

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

drm/vmwgfx: Fix hash key computation

2014-10-31T08:54:22+00:00

The hash key computation in vmw_cmdbuf_res_remove incorrectly didn't take
the resource type into account, contrary to all the other related functions.
This becomes important when the cmdbuf resource manager handles more than
one resource type.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Brian Paul

drm/vmwgfx: fix lock breakage

2014-10-31T08:44:35+00:00

After:

commit d059f652e73c35678d28d4cd09ab2cec89696af9
Author:     Daniel Vetter 
AuthorDate: Fri Jul 25 18:07:40 2014 +0200

    drm: Handle legacy per-crtc locking with full acquire ctx

drm_mode_cursor_common() was switched to use drm_modeset_(un)lock_crtc()
which uses full aquire ctx.  So dropping/reaquiring the lock via
drm_modeset_(un)lock() directly isn't the right thing to do, as lockdep
kindly points out.

The 'FIXME's about sorting out whether vmwgfx *really* needs to lock-all
for cursor updates still apply.

Signed-off-by: Rob Clark 
Reviewed-by: Jakob Bornecrantz 
Tested-by: Thomas Hellstrom