linux-toradex.git/drivers/gpu/drm/drm_gem.c, branch v3.5.7

drm/prime: add exported buffers to current fprivs imported buffer list (v2)

2012-05-23T09:46:03+00:00

If userspace attempts to import a buffer it exported on the same device,
we need to return the same GEM handle for it, not a new handle pointing
at the same GEM object.

v2: move removals into a single fn, no need to set to NULL. (Chris Wilson)

Signed-off-by: Dave Airlie

drm: Don't initialize local ret variable when not needed

2012-05-22T09:32:58+00:00

Signed-off-by: Laurent Pinchart 
Reviewed-by: Alex Deucher 
Signed-off-by: Dave Airlie

drm: pass dev to drm_vm_{open,close}_locked()

2012-05-11T16:37:46+00:00

Previously these functions would assume that vma->vm_file was the
drm_file.  Although if in some cases if the drm driver needs to use
something else for the backing file (such as the tmpfs filp) then this
assumption is no longer true.  But vma->vm_private_data is still the
GEM object.

With this change, now the drm_device comes from the GEM object rather
than the drm_file so the driver is more free to play with vma->vm_file.

The scenario where this comes up is for mmap'ing of cached dmabuf's
for non-coherent systems, where the driver needs to use fault handling
and PTE shootdown to simulate coherency.  We can't use the vma->vm_file
of the dmabuf, which is using anon_inode's address_space.  The most
straightforward thing to do is to use the GEM object's obj->filp for
vma->vm_file in all cases, for which we need this patch.

Signed-off-by: Rob Clark 
Signed-off-by: Dave Airlie

drm: Unify and fix idr error handling

2012-04-24T08:50:20+00:00

The error handling code w.r.t. idr usage looks inconsistent.

In the case of drm_mode_object_get() and drm_ctxbitmap_next() the error
handling is also incomplete.

Unify the code to follow the same pattern always.

Signed-off-by: Ville Syrjälä 
Signed-off-by: Dave Airlie

drm: base prime/dma-buf support (v5)

2012-03-30T10:52:44+00:00

This adds the basic drm dma-buf interface layer, called PRIME. This
commit doesn't add any driver support, it is simply and agreed upon starting
point so we can work towards merging driver support for the next merge window.

Current drivers with work done are nouveau, i915, udl, exynos and omap.

The main APIs exposed to userspace allow translating a 32-bit object handle
to a file descriptor, and a file descriptor to a 32-bit object handle.

The flags value is currently limited to O_CLOEXEC.

Acknowledgements:
Daniel Vetter: lots of review
Rob Clark: cleaned up lots of the internals and did lifetime review.

v2: rename some functions after Chris preferred a green shed
fix IS_ERR_OR_NULL -> IS_ERR
v3: Fix Ville pointed out using buffer + kmalloc
v4: add locking as per ickle review
v5: allow re-exporting the original dma-buf (Daniel)

Reviewed-by: Daniel Vetter 
Reviewed-by: Rob Clark 
Reviewed-by: Sumit Semwal 
Reviewed-by: Inki Dae 
Acked-by: Ben Widawsky 
Signed-off-by: Dave Airlie

drm: add core support for unplugging a device (v2)

2012-03-15T13:35:33+00:00

Two parts to this, one is simple unplug from sysfs for the device node.

The second adds an unplugged state, if we have device opens, we
just set the unplugged state and return, if we have no device
opens we drop the drm device.

If after a lastclose we discover we are unplugged we then
drop the drm device.

v2: use an atomic for unplugged and wrap it for users,
add checks on open + mmap + ioctl entry points.

Signed-off-by: Dave Airlie

drm: drop setting vm_file to filp

2012-03-05T11:19:08+00:00

Talking to Al Viro on irc, we can see no possible reason for doing
this, the upper mmap code does it. The code has been there since
first import into drm tree I can find.

Al tracked down this as a requirement pre 2.3.51 hasn't been needed since.

Acked-by: Al Viro 
Signed-off-by: Dave Airlie

drm: Pass the real error code back during GEM bo initialisation

2012-01-30T09:31:42+00:00

In particular, I found I was hitting the max-file limit in the VFS,
and the EFILE was being magically transformed into ENOMEM. Confusion
reigns.

Signed-off-by: Chris Wilson 
Reviewed-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm/gem: add functions for mmap offset creation

2011-08-30T10:06:06+00:00

Signed-off-by: Rob Clark 
Signed-off-by: Dave Airlie

drm/gem: add support for private objects

2011-07-25T11:07:15+00:00

These small changes should allow GEM to be used with non shmem objects as
well as shmem objects. In the GMA500 case it allows the base framebuffer to
appear as a GEM object and thus acquire a handle and work with KMS.

For i915 it ought to be trivial to get back the wasted memory but putting the
system fb back into stolen RAM and in general I can imagine it allowing the
use of GEM and thus KMS with all the older cards that have their framebuffer
firmly placed in video RAM.

Signed-off-by: Alan Cox 
Tested-by: Rob Clark 
Signed-off-by: Dave Airlie