2012-03-28 13:39:43 -06:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2011 Texas Instruments, Inc
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
* copy of this software and associated documentation files (the "Software"),
|
|
|
|
* to deal in the Software without restriction, including without limitation
|
|
|
|
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
|
|
* and/or sell copies of the Software, and to permit persons to whom the
|
|
|
|
* Software is furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice (including the next
|
|
|
|
* paragraph) shall be included in all copies or substantial portions of the
|
|
|
|
* Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
|
|
* SOFTWARE.
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Rob Clark <rob@ti.com>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef OMAP_DRMIF_H_
|
|
|
|
#define OMAP_DRMIF_H_
|
|
|
|
|
|
|
|
#include <xf86drm.h>
|
|
|
|
#include <stdint.h>
|
|
|
|
#include <omap_drm.h>
|
|
|
|
|
|
|
|
struct omap_bo;
|
|
|
|
struct omap_device;
|
|
|
|
|
|
|
|
/* device related functions:
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct omap_device * omap_device_new(int fd);
|
omap: add refcnting and handle tracking
There can be scenarios, especially when re-importing an existing buffer,
where you end up with multiple 'struct omap_bo's wrapping a single GEM
object handle. Which causes badness when the first of the evil-clones
is omap_bo_del()'d.
To do this, introduce reference counting and a hashtable to track the
handles per fd.
First, to avoid bo's slipping through the crack if multiple 'struct
omap_device's are created for one drm fd, a hashtable mapping drm
fd to omap_device, and the omap_device itself is reference counted.
Per omap_device, we keep a handle_table mapping GEM handle to omap_bo.
When buffers are imported from flink name or dmabuf fd, the handle
table is consulted, and if an omap_bo already exists, it's refcnt is
incremented and it is returned. For good measure, to avoid the
handle_table being deleted before the omap_bo is freed, the omap_bo
holds a reference to the omap_device.
TODO: check the overhead of the hashtable. If too much we could maybe
get away with only tracking exported and imported bo's in the table.
TODO: all the import/export flink/dmabuf operations are generic DRM
ioctls. Really all this functionality could be handled by a generic
drm_bo and drm_device "base class" that could be extended by omap,
exynos, etc. That would also allow more common userspace code by
avoiding artificial libdrm_omap dependencies.
Signed-off-by: Rob Clark <rob@ti.com>
2012-07-13 15:18:25 -06:00
|
|
|
struct omap_device * omap_device_ref(struct omap_device *dev);
|
2012-03-28 13:39:43 -06:00
|
|
|
void omap_device_del(struct omap_device *dev);
|
|
|
|
int omap_get_param(struct omap_device *dev, uint64_t param, uint64_t *value);
|
|
|
|
int omap_set_param(struct omap_device *dev, uint64_t param, uint64_t value);
|
|
|
|
|
|
|
|
/* buffer-object related functions:
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct omap_bo * omap_bo_new(struct omap_device *dev,
|
|
|
|
uint32_t size, uint32_t flags);
|
|
|
|
struct omap_bo * omap_bo_new_tiled(struct omap_device *dev,
|
|
|
|
uint32_t width, uint32_t height, uint32_t flags);
|
omap: add refcnting and handle tracking
There can be scenarios, especially when re-importing an existing buffer,
where you end up with multiple 'struct omap_bo's wrapping a single GEM
object handle. Which causes badness when the first of the evil-clones
is omap_bo_del()'d.
To do this, introduce reference counting and a hashtable to track the
handles per fd.
First, to avoid bo's slipping through the crack if multiple 'struct
omap_device's are created for one drm fd, a hashtable mapping drm
fd to omap_device, and the omap_device itself is reference counted.
Per omap_device, we keep a handle_table mapping GEM handle to omap_bo.
When buffers are imported from flink name or dmabuf fd, the handle
table is consulted, and if an omap_bo already exists, it's refcnt is
incremented and it is returned. For good measure, to avoid the
handle_table being deleted before the omap_bo is freed, the omap_bo
holds a reference to the omap_device.
TODO: check the overhead of the hashtable. If too much we could maybe
get away with only tracking exported and imported bo's in the table.
TODO: all the import/export flink/dmabuf operations are generic DRM
ioctls. Really all this functionality could be handled by a generic
drm_bo and drm_device "base class" that could be extended by omap,
exynos, etc. That would also allow more common userspace code by
avoiding artificial libdrm_omap dependencies.
Signed-off-by: Rob Clark <rob@ti.com>
2012-07-13 15:18:25 -06:00
|
|
|
struct omap_bo * omap_bo_ref(struct omap_bo *bo);
|
2012-03-28 13:39:43 -06:00
|
|
|
struct omap_bo * omap_bo_from_name(struct omap_device *dev, uint32_t name);
|
2012-06-11 16:17:17 -06:00
|
|
|
struct omap_bo * omap_bo_from_dmabuf(struct omap_device *dev, int fd);
|
2012-03-28 13:39:43 -06:00
|
|
|
void omap_bo_del(struct omap_bo *bo);
|
|
|
|
int omap_bo_get_name(struct omap_bo *bo, uint32_t *name);
|
|
|
|
uint32_t omap_bo_handle(struct omap_bo *bo);
|
2012-04-11 08:51:36 -06:00
|
|
|
int omap_bo_dmabuf(struct omap_bo *bo);
|
2012-03-28 13:39:43 -06:00
|
|
|
uint32_t omap_bo_size(struct omap_bo *bo);
|
|
|
|
void * omap_bo_map(struct omap_bo *bo);
|
|
|
|
int omap_bo_cpu_prep(struct omap_bo *bo, enum omap_gem_op op);
|
|
|
|
int omap_bo_cpu_fini(struct omap_bo *bo, enum omap_gem_op op);
|
|
|
|
|
|
|
|
#endif /* OMAP_DRMIF_H_ */
|