2017-11-01 21:09:13 +07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
|
2012-10-05 00:21:50 +07:00
|
|
|
/* exynos_drm.h
|
|
|
|
|
*
|
|
|
|
|
* Copyright (c) 2011 Samsung Electronics Co., Ltd.
|
|
|
|
|
* Authors:
|
|
|
|
|
* Inki Dae <inki.dae@samsung.com>
|
|
|
|
|
* Joonyoung Shim <jy0922.shim@samsung.com>
|
|
|
|
|
* Seung-Woo Kim <sw0312.kim@samsung.com>
|
|
|
|
|
*
|
2012-12-18 00:30:17 +07:00
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
|
* Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
|
* option) any later version.
|
2012-10-05 00:21:50 +07:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _UAPI_EXYNOS_DRM_H_
|
|
|
|
|
#define _UAPI_EXYNOS_DRM_H_
|
|
|
|
|
|
2015-11-30 21:10:45 +07:00
|
|
|
#include "drm.h"
|
2012-10-05 00:21:50 +07:00
|
|
|
|
2016-04-08 00:58:35 +07:00
|
|
|
#if defined(__cplusplus)
|
|
|
|
|
extern "C" {
|
|
|
|
|
#endif
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
/**
|
|
|
|
|
* User-desired buffer creation information structure.
|
|
|
|
|
*
|
|
|
|
|
* @size: user-desired memory allocation size.
|
|
|
|
|
* - this size value would be page-aligned internally.
|
|
|
|
|
* @flags: user request for setting memory type or cache attributes.
|
|
|
|
|
* @handle: returned a handle to created gem object.
|
|
|
|
|
* - this handle will be set by gem module of kernel side.
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_gem_create {
|
2014-08-31 18:07:31 +07:00
|
|
|
__u64 size;
|
2016-02-12 19:13:59 +07:00
|
|
|
__u32 flags;
|
|
|
|
|
__u32 handle;
|
2012-10-05 00:21:50 +07:00
|
|
|
};
|
|
|
|
|
|
2016-03-08 12:12:59 +07:00
|
|
|
/**
|
|
|
|
|
* A structure for getting a fake-offset that can be used with mmap.
|
|
|
|
|
*
|
|
|
|
|
* @handle: handle of gem object.
|
|
|
|
|
* @reserved: just padding to be 64-bit aligned.
|
|
|
|
|
* @offset: a fake-offset of gem object.
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_gem_map {
|
|
|
|
|
__u32 handle;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
__u64 offset;
|
|
|
|
|
};
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
/**
|
|
|
|
|
* A structure to gem information.
|
|
|
|
|
*
|
|
|
|
|
* @handle: a handle to gem object created.
|
|
|
|
|
* @flags: flag value including memory type and cache attribute and
|
|
|
|
|
* this value would be set by driver.
|
|
|
|
|
* @size: size to memory region allocated by gem and this size would
|
|
|
|
|
* be set by driver.
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_gem_info {
|
2016-02-12 19:13:59 +07:00
|
|
|
__u32 handle;
|
|
|
|
|
__u32 flags;
|
2014-08-31 18:07:31 +07:00
|
|
|
__u64 size;
|
2012-10-05 00:21:50 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* A structure for user connection request of virtual display.
|
|
|
|
|
*
|
|
|
|
|
* @connection: indicate whether doing connetion or not by user.
|
|
|
|
|
* @extensions: if this value is 1 then the vidi driver would need additional
|
|
|
|
|
* 128bytes edid data.
|
|
|
|
|
* @edid: the edid data pointer from user side.
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_vidi_connection {
|
2016-02-12 19:13:59 +07:00
|
|
|
__u32 connection;
|
|
|
|
|
__u32 extensions;
|
2014-08-31 18:07:31 +07:00
|
|
|
__u64 edid;
|
2012-10-05 00:21:50 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* memory type definitions. */
|
|
|
|
|
enum e_drm_exynos_gem_mem_type {
|
|
|
|
|
/* Physically Continuous memory and used as default. */
|
|
|
|
|
EXYNOS_BO_CONTIG = 0 << 0,
|
|
|
|
|
/* Physically Non-Continuous memory. */
|
|
|
|
|
EXYNOS_BO_NONCONTIG = 1 << 0,
|
|
|
|
|
/* non-cachable mapping and used as default. */
|
|
|
|
|
EXYNOS_BO_NONCACHABLE = 0 << 1,
|
|
|
|
|
/* cachable mapping. */
|
|
|
|
|
EXYNOS_BO_CACHABLE = 1 << 1,
|
|
|
|
|
/* write-combine mapping. */
|
|
|
|
|
EXYNOS_BO_WC = 1 << 2,
|
|
|
|
|
EXYNOS_BO_MASK = EXYNOS_BO_NONCONTIG | EXYNOS_BO_CACHABLE |
|
|
|
|
|
EXYNOS_BO_WC
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct drm_exynos_g2d_get_ver {
|
|
|
|
|
__u32 major;
|
|
|
|
|
__u32 minor;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct drm_exynos_g2d_cmd {
|
|
|
|
|
__u32 offset;
|
|
|
|
|
__u32 data;
|
|
|
|
|
};
|
|
|
|
|
|
drm/exynos: add userptr feature for g2d module
This patch adds userptr feautre for G2D module.
The userptr means user space address allocated by malloc().
And the purpose of this feature is to make G2D's dma able
to access the user space region.
To user this feature, user should flag G2D_BUF_USRPTR to
offset variable of struct drm_exynos_g2d_cmd and fill
struct drm_exynos_g2d_userptr with user space address
and size for it and then should set a pointer to
drm_exynos_g2d_userptr object to data variable of struct
drm_exynos_g2d_cmd. The last bit of offset variable is used
to check if the cmdlist's buffer type is userptr or not.
If userptr, the g2d driver gets user space address and size
and then gets pages through get_user_pages().
(another case is counted as gem handle)
Below is sample codes:
static void set_cmd(struct drm_exynos_g2d_cmd *cmd,
unsigned long offset, unsigned long data)
{
cmd->offset = offset;
cmd->data = data;
}
static int solid_fill_test(int x, int y, unsigned long userptr)
{
struct drm_exynos_g2d_cmd cmd_gem[5];
struct drm_exynos_g2d_userptr g2d_userptr;
unsigned int gem_nr = 0;
...
g2d_userptr.userptr = userptr;
g2d_userptr.size = x * y * 4;
set_cmd(&cmd_gem[gem_nr++], DST_BASE_ADDR_REG |
G2D_BUF_USERPTR,
(unsigned long)&g2d_userptr);
...
}
int main(int argc, char **argv)
{
unsigned long addr;
...
addr = malloc(x * y * 4);
...
solid_fill_test(x, y, addr);
...
}
And next, the pages are mapped with iommu table and the device
address is set to cmdlist so that G2D's dma can access it.
As you may know, the pages from get_user_pages() are pinned.
In other words, they CAN NOT be migrated and also swapped out.
So the dma access would be safe.
But the use of userptr feature has performance overhead so
this patch also has memory pool to the userptr feature.
Please, assume that user sends cmdlist filled with userptr
and size every time to g2d driver, and the get_user_pages
funcion will be called every time.
The memory pool has maximum 64MB size and the userptr that
user had ever sent, is holded in the memory pool.
This meaning is that if the userptr from user is same as one
in the memory pool, device address to the userptr in the memory
pool is set to cmdlist.
And last, the pages from get_user_pages() will be freed once
user calls free() and the dma access is completed. Actually,
get_user_pages() takes 2 reference counts if the user process
has never accessed user region allocated by malloc(). Then, if
the user calls free(), the page reference count becomes 1 and
becomes 0 with put_page() call. And the reverse holds as well.
This means how the pages backed are used by dma and freed.
This patch is based on "drm/exynos: add iommu support for g2d",
https://patchwork.kernel.org/patch/1629481/
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
2012-11-04 20:48:52 +07:00
|
|
|
enum drm_exynos_g2d_buf_type {
|
|
|
|
|
G2D_BUF_USERPTR = 1 << 31,
|
|
|
|
|
};
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
enum drm_exynos_g2d_event_type {
|
|
|
|
|
G2D_EVENT_NOT,
|
|
|
|
|
G2D_EVENT_NONSTOP,
|
|
|
|
|
G2D_EVENT_STOP, /* not yet */
|
|
|
|
|
};
|
|
|
|
|
|
drm/exynos: add userptr feature for g2d module
This patch adds userptr feautre for G2D module.
The userptr means user space address allocated by malloc().
And the purpose of this feature is to make G2D's dma able
to access the user space region.
To user this feature, user should flag G2D_BUF_USRPTR to
offset variable of struct drm_exynos_g2d_cmd and fill
struct drm_exynos_g2d_userptr with user space address
and size for it and then should set a pointer to
drm_exynos_g2d_userptr object to data variable of struct
drm_exynos_g2d_cmd. The last bit of offset variable is used
to check if the cmdlist's buffer type is userptr or not.
If userptr, the g2d driver gets user space address and size
and then gets pages through get_user_pages().
(another case is counted as gem handle)
Below is sample codes:
static void set_cmd(struct drm_exynos_g2d_cmd *cmd,
unsigned long offset, unsigned long data)
{
cmd->offset = offset;
cmd->data = data;
}
static int solid_fill_test(int x, int y, unsigned long userptr)
{
struct drm_exynos_g2d_cmd cmd_gem[5];
struct drm_exynos_g2d_userptr g2d_userptr;
unsigned int gem_nr = 0;
...
g2d_userptr.userptr = userptr;
g2d_userptr.size = x * y * 4;
set_cmd(&cmd_gem[gem_nr++], DST_BASE_ADDR_REG |
G2D_BUF_USERPTR,
(unsigned long)&g2d_userptr);
...
}
int main(int argc, char **argv)
{
unsigned long addr;
...
addr = malloc(x * y * 4);
...
solid_fill_test(x, y, addr);
...
}
And next, the pages are mapped with iommu table and the device
address is set to cmdlist so that G2D's dma can access it.
As you may know, the pages from get_user_pages() are pinned.
In other words, they CAN NOT be migrated and also swapped out.
So the dma access would be safe.
But the use of userptr feature has performance overhead so
this patch also has memory pool to the userptr feature.
Please, assume that user sends cmdlist filled with userptr
and size every time to g2d driver, and the get_user_pages
funcion will be called every time.
The memory pool has maximum 64MB size and the userptr that
user had ever sent, is holded in the memory pool.
This meaning is that if the userptr from user is same as one
in the memory pool, device address to the userptr in the memory
pool is set to cmdlist.
And last, the pages from get_user_pages() will be freed once
user calls free() and the dma access is completed. Actually,
get_user_pages() takes 2 reference counts if the user process
has never accessed user region allocated by malloc(). Then, if
the user calls free(), the page reference count becomes 1 and
becomes 0 with put_page() call. And the reverse holds as well.
This means how the pages backed are used by dma and freed.
This patch is based on "drm/exynos: add iommu support for g2d",
https://patchwork.kernel.org/patch/1629481/
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
2012-11-04 20:48:52 +07:00
|
|
|
struct drm_exynos_g2d_userptr {
|
|
|
|
|
unsigned long userptr;
|
|
|
|
|
unsigned long size;
|
|
|
|
|
};
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
struct drm_exynos_g2d_set_cmdlist {
|
|
|
|
|
__u64 cmd;
|
drm/exynos: add userptr feature for g2d module
This patch adds userptr feautre for G2D module.
The userptr means user space address allocated by malloc().
And the purpose of this feature is to make G2D's dma able
to access the user space region.
To user this feature, user should flag G2D_BUF_USRPTR to
offset variable of struct drm_exynos_g2d_cmd and fill
struct drm_exynos_g2d_userptr with user space address
and size for it and then should set a pointer to
drm_exynos_g2d_userptr object to data variable of struct
drm_exynos_g2d_cmd. The last bit of offset variable is used
to check if the cmdlist's buffer type is userptr or not.
If userptr, the g2d driver gets user space address and size
and then gets pages through get_user_pages().
(another case is counted as gem handle)
Below is sample codes:
static void set_cmd(struct drm_exynos_g2d_cmd *cmd,
unsigned long offset, unsigned long data)
{
cmd->offset = offset;
cmd->data = data;
}
static int solid_fill_test(int x, int y, unsigned long userptr)
{
struct drm_exynos_g2d_cmd cmd_gem[5];
struct drm_exynos_g2d_userptr g2d_userptr;
unsigned int gem_nr = 0;
...
g2d_userptr.userptr = userptr;
g2d_userptr.size = x * y * 4;
set_cmd(&cmd_gem[gem_nr++], DST_BASE_ADDR_REG |
G2D_BUF_USERPTR,
(unsigned long)&g2d_userptr);
...
}
int main(int argc, char **argv)
{
unsigned long addr;
...
addr = malloc(x * y * 4);
...
solid_fill_test(x, y, addr);
...
}
And next, the pages are mapped with iommu table and the device
address is set to cmdlist so that G2D's dma can access it.
As you may know, the pages from get_user_pages() are pinned.
In other words, they CAN NOT be migrated and also swapped out.
So the dma access would be safe.
But the use of userptr feature has performance overhead so
this patch also has memory pool to the userptr feature.
Please, assume that user sends cmdlist filled with userptr
and size every time to g2d driver, and the get_user_pages
funcion will be called every time.
The memory pool has maximum 64MB size and the userptr that
user had ever sent, is holded in the memory pool.
This meaning is that if the userptr from user is same as one
in the memory pool, device address to the userptr in the memory
pool is set to cmdlist.
And last, the pages from get_user_pages() will be freed once
user calls free() and the dma access is completed. Actually,
get_user_pages() takes 2 reference counts if the user process
has never accessed user region allocated by malloc(). Then, if
the user calls free(), the page reference count becomes 1 and
becomes 0 with put_page() call. And the reverse holds as well.
This means how the pages backed are used by dma and freed.
This patch is based on "drm/exynos: add iommu support for g2d",
https://patchwork.kernel.org/patch/1629481/
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
2012-11-04 20:48:52 +07:00
|
|
|
__u64 cmd_buf;
|
2012-10-05 00:21:50 +07:00
|
|
|
__u32 cmd_nr;
|
drm/exynos: add userptr feature for g2d module
This patch adds userptr feautre for G2D module.
The userptr means user space address allocated by malloc().
And the purpose of this feature is to make G2D's dma able
to access the user space region.
To user this feature, user should flag G2D_BUF_USRPTR to
offset variable of struct drm_exynos_g2d_cmd and fill
struct drm_exynos_g2d_userptr with user space address
and size for it and then should set a pointer to
drm_exynos_g2d_userptr object to data variable of struct
drm_exynos_g2d_cmd. The last bit of offset variable is used
to check if the cmdlist's buffer type is userptr or not.
If userptr, the g2d driver gets user space address and size
and then gets pages through get_user_pages().
(another case is counted as gem handle)
Below is sample codes:
static void set_cmd(struct drm_exynos_g2d_cmd *cmd,
unsigned long offset, unsigned long data)
{
cmd->offset = offset;
cmd->data = data;
}
static int solid_fill_test(int x, int y, unsigned long userptr)
{
struct drm_exynos_g2d_cmd cmd_gem[5];
struct drm_exynos_g2d_userptr g2d_userptr;
unsigned int gem_nr = 0;
...
g2d_userptr.userptr = userptr;
g2d_userptr.size = x * y * 4;
set_cmd(&cmd_gem[gem_nr++], DST_BASE_ADDR_REG |
G2D_BUF_USERPTR,
(unsigned long)&g2d_userptr);
...
}
int main(int argc, char **argv)
{
unsigned long addr;
...
addr = malloc(x * y * 4);
...
solid_fill_test(x, y, addr);
...
}
And next, the pages are mapped with iommu table and the device
address is set to cmdlist so that G2D's dma can access it.
As you may know, the pages from get_user_pages() are pinned.
In other words, they CAN NOT be migrated and also swapped out.
So the dma access would be safe.
But the use of userptr feature has performance overhead so
this patch also has memory pool to the userptr feature.
Please, assume that user sends cmdlist filled with userptr
and size every time to g2d driver, and the get_user_pages
funcion will be called every time.
The memory pool has maximum 64MB size and the userptr that
user had ever sent, is holded in the memory pool.
This meaning is that if the userptr from user is same as one
in the memory pool, device address to the userptr in the memory
pool is set to cmdlist.
And last, the pages from get_user_pages() will be freed once
user calls free() and the dma access is completed. Actually,
get_user_pages() takes 2 reference counts if the user process
has never accessed user region allocated by malloc(). Then, if
the user calls free(), the page reference count becomes 1 and
becomes 0 with put_page() call. And the reverse holds as well.
This means how the pages backed are used by dma and freed.
This patch is based on "drm/exynos: add iommu support for g2d",
https://patchwork.kernel.org/patch/1629481/
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
2012-11-04 20:48:52 +07:00
|
|
|
__u32 cmd_buf_nr;
|
2012-10-05 00:21:50 +07:00
|
|
|
|
|
|
|
|
/* for g2d event */
|
|
|
|
|
__u64 event_type;
|
|
|
|
|
__u64 user_data;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct drm_exynos_g2d_exec {
|
|
|
|
|
__u64 async;
|
|
|
|
|
};
|
|
|
|
|
|
drm/exynos: ipp: Add IPP v2 framework
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging operation modes of obsolete IPP v1 API (framebuffer
writeback and local-path output with image processing) can be implemented
using standard DRM features: writeback connectors and additional DRM planes
with scaling features.
V2 IPP userspace API is based on stateless approach, which much better fits
to memory-to-memory image processing model. It also provides support for
all image formats, which are both already defined in DRM API and supported
by the existing IPP hardware modules.
The API consists of the following ioctls:
- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image
processing modules,
- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image
formats of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for
selected image format of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the
provided structures (source and destination buffers, operation rectangle,
transformation, etc).
The proposed userspace API is extensible. In the future more advanced image
processing operations can be defined to support for example blending.
Userspace API is fully functional also on DRM render nodes, so it is not
limited to the root/privileged client.
Internal driver API also has been completely rewritten. New IPP core
performs all possible input validation, checks and object life-time
control. The drivers can focus only on writing configuration to hardware
registers. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifies
the driver API. Minimal driver needs to provide a single callback for
starting processing and an array with supported image formats.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
Merge conflict so merged manually.
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2018-05-10 06:46:36 +07:00
|
|
|
/* Exynos DRM IPP v2 API */
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Enumerate available IPP hardware modules.
|
|
|
|
|
*
|
|
|
|
|
* @count_ipps: size of ipp_id array / number of ipp modules (set by driver)
|
|
|
|
|
* @reserved: padding
|
|
|
|
|
* @ipp_id_ptr: pointer to ipp_id array or NULL
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ioctl_ipp_get_res {
|
|
|
|
|
__u32 count_ipps;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
__u64 ipp_id_ptr;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum drm_exynos_ipp_format_type {
|
|
|
|
|
DRM_EXYNOS_IPP_FORMAT_SOURCE = 0x01,
|
|
|
|
|
DRM_EXYNOS_IPP_FORMAT_DESTINATION = 0x02,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct drm_exynos_ipp_format {
|
|
|
|
|
__u32 fourcc;
|
|
|
|
|
__u32 type;
|
|
|
|
|
__u64 modifier;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum drm_exynos_ipp_capability {
|
|
|
|
|
DRM_EXYNOS_IPP_CAP_CROP = 0x01,
|
|
|
|
|
DRM_EXYNOS_IPP_CAP_ROTATE = 0x02,
|
|
|
|
|
DRM_EXYNOS_IPP_CAP_SCALE = 0x04,
|
|
|
|
|
DRM_EXYNOS_IPP_CAP_CONVERT = 0x08,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Get IPP hardware capabilities and supported image formats.
|
|
|
|
|
*
|
|
|
|
|
* @ipp_id: id of IPP module to query
|
|
|
|
|
* @capabilities: bitmask of drm_exynos_ipp_capability (set by driver)
|
|
|
|
|
* @reserved: padding
|
|
|
|
|
* @formats_count: size of formats array (in entries) / number of filled
|
|
|
|
|
* formats (set by driver)
|
|
|
|
|
* @formats_ptr: pointer to formats array or NULL
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ioctl_ipp_get_caps {
|
|
|
|
|
__u32 ipp_id;
|
|
|
|
|
__u32 capabilities;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
__u32 formats_count;
|
|
|
|
|
__u64 formats_ptr;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum drm_exynos_ipp_limit_type {
|
|
|
|
|
/* size (horizontal/vertial) limits, in pixels (min, max, alignment) */
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_TYPE_SIZE = 0x0001,
|
|
|
|
|
/* scale ratio (horizonta/vertial), 16.16 fixed point (min, max) */
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_TYPE_SCALE = 0x0002,
|
|
|
|
|
|
|
|
|
|
/* image buffer area */
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_SIZE_BUFFER = 0x0001 << 16,
|
|
|
|
|
/* src/dst rectangle area */
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_SIZE_AREA = 0x0002 << 16,
|
|
|
|
|
/* src/dst rectangle area when rotation enabled */
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_SIZE_ROTATED = 0x0003 << 16,
|
|
|
|
|
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_TYPE_MASK = 0x000f,
|
|
|
|
|
DRM_EXYNOS_IPP_LIMIT_SIZE_MASK = 0x000f << 16,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct drm_exynos_ipp_limit_val {
|
|
|
|
|
__u32 min;
|
|
|
|
|
__u32 max;
|
|
|
|
|
__u32 align;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* IPP module limitation.
|
|
|
|
|
*
|
|
|
|
|
* @type: limit type (see drm_exynos_ipp_limit_type enum)
|
|
|
|
|
* @reserved: padding
|
|
|
|
|
* @h: horizontal limits
|
|
|
|
|
* @v: vertical limits
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ipp_limit {
|
|
|
|
|
__u32 type;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
struct drm_exynos_ipp_limit_val h;
|
|
|
|
|
struct drm_exynos_ipp_limit_val v;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Get IPP limits for given image format.
|
|
|
|
|
*
|
|
|
|
|
* @ipp_id: id of IPP module to query
|
|
|
|
|
* @fourcc: image format code (see DRM_FORMAT_* in drm_fourcc.h)
|
|
|
|
|
* @modifier: image format modifier (see DRM_FORMAT_MOD_* in drm_fourcc.h)
|
|
|
|
|
* @type: source/destination identifier (drm_exynos_ipp_format_flag enum)
|
|
|
|
|
* @limits_count: size of limits array (in entries) / number of filled entries
|
|
|
|
|
* (set by driver)
|
|
|
|
|
* @limits_ptr: pointer to limits array or NULL
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ioctl_ipp_get_limits {
|
|
|
|
|
__u32 ipp_id;
|
|
|
|
|
__u32 fourcc;
|
|
|
|
|
__u64 modifier;
|
|
|
|
|
__u32 type;
|
|
|
|
|
__u32 limits_count;
|
|
|
|
|
__u64 limits_ptr;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum drm_exynos_ipp_task_id {
|
|
|
|
|
/* buffer described by struct drm_exynos_ipp_task_buffer */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_BUFFER = 0x0001,
|
|
|
|
|
/* rectangle described by struct drm_exynos_ipp_task_rect */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_RECTANGLE = 0x0002,
|
|
|
|
|
/* transformation described by struct drm_exynos_ipp_task_transform */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_TRANSFORM = 0x0003,
|
|
|
|
|
/* alpha configuration described by struct drm_exynos_ipp_task_alpha */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_ALPHA = 0x0004,
|
|
|
|
|
|
|
|
|
|
/* source image data (for buffer and rectangle chunks) */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_TYPE_SOURCE = 0x0001 << 16,
|
|
|
|
|
/* destination image data (for buffer and rectangle chunks) */
|
|
|
|
|
DRM_EXYNOS_IPP_TASK_TYPE_DESTINATION = 0x0002 << 16,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Memory buffer with image data.
|
|
|
|
|
*
|
|
|
|
|
* @id: must be DRM_EXYNOS_IPP_TASK_BUFFER
|
|
|
|
|
* other parameters are same as for AddFB2 generic DRM ioctl
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ipp_task_buffer {
|
|
|
|
|
__u32 id;
|
|
|
|
|
__u32 fourcc;
|
|
|
|
|
__u32 width, height;
|
|
|
|
|
__u32 gem_id[4];
|
|
|
|
|
__u32 offset[4];
|
|
|
|
|
__u32 pitch[4];
|
|
|
|
|
__u64 modifier;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Rectangle for processing.
|
|
|
|
|
*
|
|
|
|
|
* @id: must be DRM_EXYNOS_IPP_TASK_RECTANGLE
|
|
|
|
|
* @reserved: padding
|
|
|
|
|
* @x,@y: left corner in pixels
|
|
|
|
|
* @w,@h: width/height in pixels
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ipp_task_rect {
|
|
|
|
|
__u32 id;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
__u32 x;
|
|
|
|
|
__u32 y;
|
|
|
|
|
__u32 w;
|
|
|
|
|
__u32 h;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Image tranformation description.
|
|
|
|
|
*
|
|
|
|
|
* @id: must be DRM_EXYNOS_IPP_TASK_TRANSFORM
|
|
|
|
|
* @rotation: DRM_MODE_ROTATE_* and DRM_MODE_REFLECT_* values
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ipp_task_transform {
|
|
|
|
|
__u32 id;
|
|
|
|
|
__u32 rotation;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Image global alpha configuration for formats without alpha values.
|
|
|
|
|
*
|
|
|
|
|
* @id: must be DRM_EXYNOS_IPP_TASK_ALPHA
|
|
|
|
|
* @value: global alpha value (0-255)
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ipp_task_alpha {
|
|
|
|
|
__u32 id;
|
|
|
|
|
__u32 value;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum drm_exynos_ipp_flag {
|
|
|
|
|
/* generate DRM event after processing */
|
|
|
|
|
DRM_EXYNOS_IPP_FLAG_EVENT = 0x01,
|
|
|
|
|
/* dry run, only check task parameters */
|
|
|
|
|
DRM_EXYNOS_IPP_FLAG_TEST_ONLY = 0x02,
|
|
|
|
|
/* non-blocking processing */
|
|
|
|
|
DRM_EXYNOS_IPP_FLAG_NONBLOCK = 0x04,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define DRM_EXYNOS_IPP_FLAGS (DRM_EXYNOS_IPP_FLAG_EVENT |\
|
|
|
|
|
DRM_EXYNOS_IPP_FLAG_TEST_ONLY | DRM_EXYNOS_IPP_FLAG_NONBLOCK)
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Perform image processing described by array of drm_exynos_ipp_task_*
|
|
|
|
|
* structures (parameters array).
|
|
|
|
|
*
|
|
|
|
|
* @ipp_id: id of IPP module to run the task
|
|
|
|
|
* @flags: bitmask of drm_exynos_ipp_flag values
|
|
|
|
|
* @reserved: padding
|
|
|
|
|
* @params_size: size of parameters array (in bytes)
|
|
|
|
|
* @params_ptr: pointer to parameters array or NULL
|
|
|
|
|
* @user_data: (optional) data for drm event
|
|
|
|
|
*/
|
|
|
|
|
struct drm_exynos_ioctl_ipp_commit {
|
|
|
|
|
__u32 ipp_id;
|
|
|
|
|
__u32 flags;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
__u32 params_size;
|
|
|
|
|
__u64 params_ptr;
|
|
|
|
|
__u64 user_data;
|
|
|
|
|
};
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
#define DRM_EXYNOS_GEM_CREATE 0x00
|
2016-03-08 12:12:59 +07:00
|
|
|
#define DRM_EXYNOS_GEM_MAP 0x01
|
2012-10-05 00:21:50 +07:00
|
|
|
/* Reserved 0x03 ~ 0x05 for exynos specific gem ioctl */
|
|
|
|
|
#define DRM_EXYNOS_GEM_GET 0x04
|
|
|
|
|
#define DRM_EXYNOS_VIDI_CONNECTION 0x07
|
|
|
|
|
|
|
|
|
|
/* G2D */
|
|
|
|
|
#define DRM_EXYNOS_G2D_GET_VER 0x20
|
|
|
|
|
#define DRM_EXYNOS_G2D_SET_CMDLIST 0x21
|
|
|
|
|
#define DRM_EXYNOS_G2D_EXEC 0x22
|
|
|
|
|
|
drm/exynos: ipp: Remove Exynos DRM IPP subsystem
Exynos DRM IPP subsystem is in fact non-functional and frankly speaking
dead-code. This patch clearly marks that Exynos DRM IPP subsystem is
broken and never really functional. It will be replaced by a completely
rewritten API.
Exynos DRM IPP user-space API can be obsoleted for the following
reasons:
1. Exynos DRM IPP user-space API can be optional in Exynos DRM, so
userspace should not rely that it is always available and should have
a software fallback in case it is not there.
2. The only mode which was initially semi-working was memory-to-memory
image processing. The remaining modes (LCD-"writeback" and "output")
were never operational due to missing code (both in mainline and even
vendor kernels).
3. Exynos DRM IPP mainline user-space API compatibility for
memory-to-memory got broken very early by commit 083500baefd5 ("drm:
remove DRM_FORMAT_NV12MT", which removed the support for tiled formats,
the main feature which made this API somehow useful on Exynos platforms
(video codec that time produced only tiled frames, to implement xvideo
or any other video overlay, one has to de-tile them for proper
display).
4. Broken drivers. Especially once support for IOMMU has been added,
it revealed that drivers don't configure DMA operations properly and in
many cases operate outside the provided buffers trashing memory around.
5. Need for external patches. Although IPP user-space API has been used
in some vendor kernels, but in such cases there were additional patches
applied (like reverting mentioned 083500baefd5 patch) what means that
those userspace apps which might use it, still won't work with the
mainline kernel version.
We don't have time machines, so we cannot change it, but Exynos DRM IPP
extension should never have been merged to mainline in that form.
Exynos IPP subsystem and user-space API will be rewritten, so remove
current IPP core code and mark existing drivers as BROKEN.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Daniel Stone <daniels@collabora.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2017-12-14 22:10:15 +07:00
|
|
|
/* Reserved 0x30 ~ 0x33 for obsolete Exynos IPP ioctls */
|
drm/exynos: ipp: Add IPP v2 framework
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging operation modes of obsolete IPP v1 API (framebuffer
writeback and local-path output with image processing) can be implemented
using standard DRM features: writeback connectors and additional DRM planes
with scaling features.
V2 IPP userspace API is based on stateless approach, which much better fits
to memory-to-memory image processing model. It also provides support for
all image formats, which are both already defined in DRM API and supported
by the existing IPP hardware modules.
The API consists of the following ioctls:
- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image
processing modules,
- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image
formats of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for
selected image format of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the
provided structures (source and destination buffers, operation rectangle,
transformation, etc).
The proposed userspace API is extensible. In the future more advanced image
processing operations can be defined to support for example blending.
Userspace API is fully functional also on DRM render nodes, so it is not
limited to the root/privileged client.
Internal driver API also has been completely rewritten. New IPP core
performs all possible input validation, checks and object life-time
control. The drivers can focus only on writing configuration to hardware
registers. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifies
the driver API. Minimal driver needs to provide a single callback for
starting processing and an array with supported image formats.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
Merge conflict so merged manually.
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2018-05-10 06:46:36 +07:00
|
|
|
/* IPP - Image Post Processing */
|
|
|
|
|
#define DRM_EXYNOS_IPP_GET_RESOURCES 0x40
|
|
|
|
|
#define DRM_EXYNOS_IPP_GET_CAPS 0x41
|
|
|
|
|
#define DRM_EXYNOS_IPP_GET_LIMITS 0x42
|
|
|
|
|
#define DRM_EXYNOS_IPP_COMMIT 0x43
|
drm/exynos: add ipp subsystem
This patch adds Image Post Processing(IPP) support for exynos drm driver.
IPP supports image scaler/rotator and input/output DMA operations
using IPP subsystem framework to control FIMC, Rotator and GSC hardware
and supports some user interfaces for user side.
And each IPP-based drivers support Memory to Memory operations
with various converting. And in case of FIMC hardware, it also supports
Writeback and Display output operations through local path.
Features:
- Memory to Memory operation support.
- Various pixel formats support.
- Image scaling support.
- Color Space Conversion support.
- Image crop operation support.
- Rotate operation support to 90, 180 or 270 degree.
- Flip operation support to vertical, horizontal or both.
- Writeback operation support to display blended image of FIMD fifo on screen
A summary to IPP Subsystem operations:
First of all, user should get property capabilities from IPP subsystem
and set these properties to hardware registers for desired operations.
The properties could be pixel format, position, rotation degree and
flip operation.
And next, user should set source and destination buffer data using
DRM_EXYNOS_IPP_QUEUE_BUF ioctl command with gem handles to source and
destinition buffers.
And next, user can control user-desired hardware with desired operations
such as play, stop, pause and resume controls.
And finally, user can aware of dma operation completion and also get
destination buffer that it contains user-desried result through dequeue
command.
IOCTL commands:
- DRM_EXYNOS_IPP_GET_PROPERTY
. get ipp driver capabilitis and id.
- DRM_EXYNOS_IPP_SET_PROPERTY
. set format, position, rotation, flip to source and destination buffers
- DRM_EXYNOS_IPP_QUEUE_BUF
. enqueue/dequeue buffer and make event list.
- DRM_EXYNOS_IPP_CMD_CTRL
. play/stop/pause/resume control.
Event:
- DRM_EXYNOS_IPP_EVENT
. a event to notify dma operation completion to user side.
Basic control flow:
Open -> Get properties -> User choose desired IPP sub driver(FIMC, Rotator
or GSCALER) -> Set Property -> Create gem handle -> Enqueue to source and
destination buffers -> Command control(Play) -> Event is notified to User
-> User gets destinition buffer complated -> (Enqueue to source and
destination buffers -> Event is notified to User) * N -> Queue/Dequeue to
source and destination buffers -> Command control(Stop) -> Free gem handle
-> Close
Changelog v1 ~ v5:
- added comments, code fixups and cleanups.
Signed-off-by: Eunchul Kim <chulspro.kim@samsung.com>
Signed-off-by: Jinyoung Jeon <jy0.jeon@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
2012-12-14 16:10:31 +07:00
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
#define DRM_IOCTL_EXYNOS_GEM_CREATE DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_GEM_CREATE, struct drm_exynos_gem_create)
|
2016-03-08 12:12:59 +07:00
|
|
|
#define DRM_IOCTL_EXYNOS_GEM_MAP DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_GEM_MAP, struct drm_exynos_gem_map)
|
2012-10-05 00:21:50 +07:00
|
|
|
#define DRM_IOCTL_EXYNOS_GEM_GET DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_GEM_GET, struct drm_exynos_gem_info)
|
|
|
|
|
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_VIDI_CONNECTION DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_VIDI_CONNECTION, struct drm_exynos_vidi_connection)
|
|
|
|
|
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_G2D_GET_VER DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_G2D_GET_VER, struct drm_exynos_g2d_get_ver)
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_G2D_SET_CMDLIST DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_G2D_SET_CMDLIST, struct drm_exynos_g2d_set_cmdlist)
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_G2D_EXEC DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_G2D_EXEC, struct drm_exynos_g2d_exec)
|
|
|
|
|
|
drm/exynos: ipp: Add IPP v2 framework
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging operation modes of obsolete IPP v1 API (framebuffer
writeback and local-path output with image processing) can be implemented
using standard DRM features: writeback connectors and additional DRM planes
with scaling features.
V2 IPP userspace API is based on stateless approach, which much better fits
to memory-to-memory image processing model. It also provides support for
all image formats, which are both already defined in DRM API and supported
by the existing IPP hardware modules.
The API consists of the following ioctls:
- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image
processing modules,
- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image
formats of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for
selected image format of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the
provided structures (source and destination buffers, operation rectangle,
transformation, etc).
The proposed userspace API is extensible. In the future more advanced image
processing operations can be defined to support for example blending.
Userspace API is fully functional also on DRM render nodes, so it is not
limited to the root/privileged client.
Internal driver API also has been completely rewritten. New IPP core
performs all possible input validation, checks and object life-time
control. The drivers can focus only on writing configuration to hardware
registers. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifies
the driver API. Minimal driver needs to provide a single callback for
starting processing and an array with supported image formats.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
Merge conflict so merged manually.
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2018-05-10 06:46:36 +07:00
|
|
|
#define DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_IPP_GET_RESOURCES, \
|
|
|
|
|
struct drm_exynos_ioctl_ipp_get_res)
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_IPP_GET_CAPS DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_IPP_GET_CAPS, struct drm_exynos_ioctl_ipp_get_caps)
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_IPP_GET_LIMITS DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_IPP_GET_LIMITS, \
|
|
|
|
|
struct drm_exynos_ioctl_ipp_get_limits)
|
|
|
|
|
#define DRM_IOCTL_EXYNOS_IPP_COMMIT DRM_IOWR(DRM_COMMAND_BASE + \
|
|
|
|
|
DRM_EXYNOS_IPP_COMMIT, struct drm_exynos_ioctl_ipp_commit)
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
/* EXYNOS specific events */
|
|
|
|
|
#define DRM_EXYNOS_G2D_EVENT 0x80000000
|
drm/exynos: ipp: Add IPP v2 framework
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging operation modes of obsolete IPP v1 API (framebuffer
writeback and local-path output with image processing) can be implemented
using standard DRM features: writeback connectors and additional DRM planes
with scaling features.
V2 IPP userspace API is based on stateless approach, which much better fits
to memory-to-memory image processing model. It also provides support for
all image formats, which are both already defined in DRM API and supported
by the existing IPP hardware modules.
The API consists of the following ioctls:
- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image
processing modules,
- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image
formats of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for
selected image format of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the
provided structures (source and destination buffers, operation rectangle,
transformation, etc).
The proposed userspace API is extensible. In the future more advanced image
processing operations can be defined to support for example blending.
Userspace API is fully functional also on DRM render nodes, so it is not
limited to the root/privileged client.
Internal driver API also has been completely rewritten. New IPP core
performs all possible input validation, checks and object life-time
control. The drivers can focus only on writing configuration to hardware
registers. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifies
the driver API. Minimal driver needs to provide a single callback for
starting processing and an array with supported image formats.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
Merge conflict so merged manually.
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2018-05-10 06:46:36 +07:00
|
|
|
#define DRM_EXYNOS_IPP_EVENT 0x80000002
|
2012-10-05 00:21:50 +07:00
|
|
|
|
|
|
|
|
struct drm_exynos_g2d_event {
|
|
|
|
|
struct drm_event base;
|
|
|
|
|
__u64 user_data;
|
|
|
|
|
__u32 tv_sec;
|
|
|
|
|
__u32 tv_usec;
|
|
|
|
|
__u32 cmdlist_no;
|
|
|
|
|
__u32 reserved;
|
|
|
|
|
};
|
|
|
|
|
|
drm/exynos: ipp: Add IPP v2 framework
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging operation modes of obsolete IPP v1 API (framebuffer
writeback and local-path output with image processing) can be implemented
using standard DRM features: writeback connectors and additional DRM planes
with scaling features.
V2 IPP userspace API is based on stateless approach, which much better fits
to memory-to-memory image processing model. It also provides support for
all image formats, which are both already defined in DRM API and supported
by the existing IPP hardware modules.
The API consists of the following ioctls:
- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image
processing modules,
- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image
formats of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for
selected image format of given IPP module,
- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the
provided structures (source and destination buffers, operation rectangle,
transformation, etc).
The proposed userspace API is extensible. In the future more advanced image
processing operations can be defined to support for example blending.
Userspace API is fully functional also on DRM render nodes, so it is not
limited to the root/privileged client.
Internal driver API also has been completely rewritten. New IPP core
performs all possible input validation, checks and object life-time
control. The drivers can focus only on writing configuration to hardware
registers. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifies
the driver API. Minimal driver needs to provide a single callback for
starting processing and an array with supported image formats.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Tested-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
Merge conflict so merged manually.
Signed-off-by: Inki Dae <inki.dae@samsung.com>
2018-05-10 06:46:36 +07:00
|
|
|
struct drm_exynos_ipp_event {
|
|
|
|
|
struct drm_event base;
|
|
|
|
|
__u64 user_data;
|
|
|
|
|
__u32 tv_sec;
|
|
|
|
|
__u32 tv_usec;
|
|
|
|
|
__u32 ipp_id;
|
|
|
|
|
__u32 sequence;
|
|
|
|
|
__u64 reserved;
|
|
|
|
|
};
|
|
|
|
|
|
2016-04-08 00:58:35 +07:00
|
|
|
#if defined(__cplusplus)
|
|
|
|
|
}
|
|
|
|
|
#endif
|
|
|
|
|
|
2012-10-05 00:21:50 +07:00
|
|
|
#endif /* _UAPI_EXYNOS_DRM_H_ */
|