linux-toradex.git/include/drm/vmwgfx_drm.h, branch v3.3.8

vmwgfx: Reinstate the update_layout ioctl

2011-11-02T08:30:31+00:00

We need to redefine a connector as "connected" if it matches a window
in the host preferred GUI layout.
Otherwise "smart" window managers would turn on Xorg outputs that we don't
want to be on.

This reinstates the update_layout and adds the following information to
the modesetting system.
a) Connection status <-> Equivalent to real hardware connection status
b) Preferred mode <-> Equivalent to real hardware reading EDID
c) Host window position <-> Equivalent to a real hardware scanout address
dynamic register.

It should be noted that there is no assumption here about what should be
displayed and where. Only how to access the host windows.

This also bumps minor to signal availability of the new IOCTL.

Based on code originally written by Jakob Bornecrantz

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

vmwgfx: Add fence events

2011-10-10T14:46:55+00:00

Add a way to send DRM events down the gpu fifo by attaching them to
fence objects. This may be useful for Xserver swapbuffer throttling and
page-flip done notifications.

Bump version to 2.2 to signal the availability of the FENCE_EVENT ioctl.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Add present and readback ioctls

2011-10-05T09:17:17+00:00

Signed-off-by: Jakob Bornecrantz 
Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

vmwgfx: Bump major

2011-09-06T10:51:12+00:00

This bumps driver major version as a result of previous incompatible
interface changes.

In addition, a leftover command definition is removed from the
vmwgfx_drm.h header.

Also a strict version check is enforced on the exebuf ioctl.

This is intended to be the last major bump before exiting staging.

Signed-off-by: Thomas Hellstrom 
Signed-off-by: Dave Airlie

vmwgfx: Implement fence objects

2011-09-06T10:51:11+00:00

Will be needed for queries and drm event-driven throttling.

As a benefit, they help avoid stale user-space fence handles.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Fix confusion caused by using "fence" in various places

2011-09-06T10:48:40+00:00

This is needed before we introduce the fence objects.
Otherwise this will be even more confusing. The plan is to use the following:

seqno: A 32-bit sequence number that may be passed in the fifo.
marker: Objects, carrying a seqno, that track fifo submission time. They
are used for fifo lag based throttling.
fence objects: Kernel space objects, possibly accessible from user-space and
carrying a 32-bit seqno together with signaled status.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Add functionality to get 3D caps

2011-09-06T10:48:35+00:00

Since we don't allow user-space to map the fifo anymore,
add a parameter to get fifo hw version and
an ioctl to copy the 3D capabilities.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecranz 
Signed-off-by: Dave Airlie

vmwgfx: Remove the possibility to map the fifo from user-space

2011-09-06T10:48:34+00:00

This was previously used by user-space to check whether a fence
sequence had passed or not.
With fence objects that's not needed anymore.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Remove the update layout IOCTL.

2011-09-06T10:48:33+00:00

It doesn't seem like its needed. If this turns out to be an incorrect
assumption, we can reinstate it.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie

vmwgfx: Remove the fifo debug ioctl

2011-09-06T10:48:32+00:00

It was only used for bringup debugging, and probably doesn't work
anymore. Remove it.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Dave Airlie