summaryrefslogtreecommitdiff
path: root/freedreno/freedreno_drmif.h
diff options
context:
space:
mode:
authorRob Clark <robclark@freedesktop.org>2014-01-12 08:27:36 -0500
committerRob Clark <robclark@freedesktop.org>2014-01-12 09:00:51 -0500
commit8279c8fb498785ea2700c6cc4a3456d7e1134665 (patch)
tree3c18768a0b69bf294fd0bc3db5d59d3dbacdbc07 /freedreno/freedreno_drmif.h
parentde0970203091618834e4753c14d5169770797800 (diff)
freedreno: add fd_device_new_dup()
There seem to be some cases (I've noticed this switching resolution in some games, for example) where the fd can get closed() before the device and all it's bo's are destroyed. Which, if the drm device is opened again and bo's are allocated with the same handles, results that when the first pipe_screen/pipe_context is destroyed causes the first dev to close handles for bo's allocated by the second device. The easy solution to that is to add a mode where the fd_device creates it's own private fd (a dup()). Signed-off-by: Rob Clark <robclark@freedesktop.org>
Diffstat (limited to 'freedreno/freedreno_drmif.h')
-rw-r--r--freedreno/freedreno_drmif.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/freedreno/freedreno_drmif.h b/freedreno/freedreno_drmif.h
index 6a40ab8f..f3a01aff 100644
--- a/freedreno/freedreno_drmif.h
+++ b/freedreno/freedreno_drmif.h
@@ -72,6 +72,7 @@ enum fd_param_id {
*/
struct fd_device * fd_device_new(int fd);
+struct fd_device * fd_device_new_dup(int fd);
struct fd_device * fd_device_ref(struct fd_device *dev);
void fd_device_del(struct fd_device *dev);