2011-10-04 10:19:01 +00:00
|
|
|
/* exynos_drm_drv.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-17 17:30:17 +00: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.
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _EXYNOS_DRM_DRV_H_
|
|
|
|
|
#define _EXYNOS_DRM_DRV_H_
|
|
|
|
|
|
2011-11-12 07:57:42 +00:00
|
|
|
#include <linux/module.h>
|
2011-10-04 10:19:01 +00:00
|
|
|
|
2012-03-21 01:55:26 +00:00
|
|
|
#define MAX_CRTC 3
|
2011-12-08 08:54:07 +00:00
|
|
|
#define MAX_PLANE 5
|
2012-03-21 01:55:26 +00:00
|
|
|
#define MAX_FB_BUFFER 4
|
2011-12-08 08:54:07 +00:00
|
|
|
#define DEFAULT_ZPOS -1
|
2011-10-04 10:19:01 +00:00
|
|
|
|
2012-08-20 10:55:14 +00:00
|
|
|
#define _wait_for(COND, MS) ({ \
|
|
|
|
|
unsigned long timeout__ = jiffies + msecs_to_jiffies(MS); \
|
|
|
|
|
int ret__ = 0; \
|
|
|
|
|
while (!(COND)) { \
|
|
|
|
|
if (time_after(jiffies, timeout__)) { \
|
|
|
|
|
ret__ = -ETIMEDOUT; \
|
|
|
|
|
break; \
|
|
|
|
|
} \
|
|
|
|
|
} \
|
|
|
|
|
ret__; \
|
|
|
|
|
})
|
|
|
|
|
|
|
|
|
|
#define wait_for(COND, MS) _wait_for(COND, MS)
|
|
|
|
|
|
2011-10-04 10:19:01 +00:00
|
|
|
struct drm_device;
|
|
|
|
|
struct exynos_drm_overlay;
|
|
|
|
|
struct drm_connector;
|
|
|
|
|
|
2011-12-16 12:31:12 +00:00
|
|
|
extern unsigned int drm_vblank_offdelay;
|
|
|
|
|
|
2011-10-04 10:19:01 +00:00
|
|
|
/* this enumerates display type. */
|
|
|
|
|
enum exynos_drm_output_type {
|
|
|
|
|
EXYNOS_DISPLAY_TYPE_NONE,
|
|
|
|
|
/* RGB or CPU Interface. */
|
|
|
|
|
EXYNOS_DISPLAY_TYPE_LCD,
|
|
|
|
|
/* HDMI Interface. */
|
|
|
|
|
EXYNOS_DISPLAY_TYPE_HDMI,
|
2012-03-21 01:55:26 +00:00
|
|
|
/* Virtual Display Interface. */
|
|
|
|
|
EXYNOS_DISPLAY_TYPE_VIDI,
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Exynos drm common overlay structure.
|
|
|
|
|
*
|
2011-10-14 04:29:46 +00:00
|
|
|
* @fb_x: offset x on a framebuffer to be displayed.
|
|
|
|
|
* - the unit is screen coordinates.
|
|
|
|
|
* @fb_y: offset y on a framebuffer to be displayed.
|
|
|
|
|
* - the unit is screen coordinates.
|
|
|
|
|
* @fb_width: width of a framebuffer.
|
|
|
|
|
* @fb_height: height of a framebuffer.
|
2012-04-24 09:43:10 +00:00
|
|
|
* @src_width: width of a partial image to be displayed from framebuffer.
|
|
|
|
|
* @src_height: height of a partial image to be displayed from framebuffer.
|
2011-10-14 04:29:46 +00:00
|
|
|
* @crtc_x: offset x on hardware screen.
|
|
|
|
|
* @crtc_y: offset y on hardware screen.
|
|
|
|
|
* @crtc_width: window width to be displayed (hardware screen).
|
|
|
|
|
* @crtc_height: window height to be displayed (hardware screen).
|
|
|
|
|
* @mode_width: width of screen mode.
|
|
|
|
|
* @mode_height: height of screen mode.
|
|
|
|
|
* @refresh: refresh rate.
|
|
|
|
|
* @scan_flag: interlace or progressive way.
|
|
|
|
|
* (it could be DRM_MODE_FLAG_*)
|
2011-10-04 10:19:01 +00:00
|
|
|
* @bpp: pixel size.(in bit)
|
2011-12-15 05:36:22 +00:00
|
|
|
* @pixel_format: fourcc pixel format of this overlay
|
|
|
|
|
* @dma_addr: array of bus(accessed by dma) address to the memory region
|
|
|
|
|
* allocated for a overlay.
|
2011-12-08 08:54:07 +00:00
|
|
|
* @zpos: order of overlay layer(z position).
|
2011-10-04 10:19:01 +00:00
|
|
|
* @default_win: a window to be enabled.
|
|
|
|
|
* @color_key: color key on or off.
|
|
|
|
|
* @index_color: if using color key feature then this value would be used
|
|
|
|
|
* as index color.
|
|
|
|
|
* @local_path: in case of lcd type, local path mode on or off.
|
|
|
|
|
* @transparency: transparency on or off.
|
|
|
|
|
* @activated: activated or not.
|
|
|
|
|
*
|
|
|
|
|
* this structure is common to exynos SoC and its contents would be copied
|
|
|
|
|
* to hardware specific overlay info.
|
|
|
|
|
*/
|
|
|
|
|
struct exynos_drm_overlay {
|
2011-10-14 04:29:46 +00:00
|
|
|
unsigned int fb_x;
|
|
|
|
|
unsigned int fb_y;
|
|
|
|
|
unsigned int fb_width;
|
|
|
|
|
unsigned int fb_height;
|
2012-04-24 09:43:10 +00:00
|
|
|
unsigned int src_width;
|
|
|
|
|
unsigned int src_height;
|
2011-10-14 04:29:46 +00:00
|
|
|
unsigned int crtc_x;
|
|
|
|
|
unsigned int crtc_y;
|
|
|
|
|
unsigned int crtc_width;
|
|
|
|
|
unsigned int crtc_height;
|
|
|
|
|
unsigned int mode_width;
|
|
|
|
|
unsigned int mode_height;
|
|
|
|
|
unsigned int refresh;
|
|
|
|
|
unsigned int scan_flag;
|
2011-10-04 10:19:01 +00:00
|
|
|
unsigned int bpp;
|
2011-10-14 04:29:46 +00:00
|
|
|
unsigned int pitch;
|
2011-12-15 05:36:22 +00:00
|
|
|
uint32_t pixel_format;
|
|
|
|
|
dma_addr_t dma_addr[MAX_FB_BUFFER];
|
2011-12-08 08:54:07 +00:00
|
|
|
int zpos;
|
2011-10-04 10:19:01 +00:00
|
|
|
|
|
|
|
|
bool default_win;
|
|
|
|
|
bool color_key;
|
|
|
|
|
unsigned int index_color;
|
|
|
|
|
bool local_path;
|
|
|
|
|
bool transparency;
|
|
|
|
|
bool activated;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Exynos DRM Display Structure.
|
|
|
|
|
* - this structure is common to analog tv, digital tv and lcd panel.
|
|
|
|
|
*
|
2014-01-30 21:19:03 +00:00
|
|
|
* @initialize: initializes the display with drm_dev
|
2014-02-19 12:02:55 +00:00
|
|
|
* @remove: cleans up the display for removal
|
|
|
|
|
* @mode_fixup: fix mode data comparing to hw specific display mode.
|
|
|
|
|
* @mode_set: convert drm_display_mode to hw specific display mode and
|
|
|
|
|
* would be called by encoder->mode_set().
|
2013-06-10 09:20:00 +00:00
|
|
|
* @check_mode: check if mode is valid or not.
|
2014-01-30 21:19:09 +00:00
|
|
|
* @dpms: display device on or off.
|
2014-02-19 12:02:55 +00:00
|
|
|
* @commit: apply changes to hw
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
2014-02-19 12:02:55 +00:00
|
|
|
struct exynos_drm_display;
|
2011-10-19 08:23:07 +00:00
|
|
|
struct exynos_drm_display_ops {
|
2014-02-19 12:02:55 +00:00
|
|
|
int (*initialize)(struct exynos_drm_display *display,
|
|
|
|
|
struct drm_device *drm_dev);
|
2014-02-24 10:15:38 +00:00
|
|
|
int (*create_connector)(struct exynos_drm_display *display,
|
|
|
|
|
struct drm_encoder *encoder);
|
2014-02-19 12:02:55 +00:00
|
|
|
void (*remove)(struct exynos_drm_display *display);
|
|
|
|
|
void (*mode_fixup)(struct exynos_drm_display *display,
|
|
|
|
|
struct drm_connector *connector,
|
|
|
|
|
const struct drm_display_mode *mode,
|
|
|
|
|
struct drm_display_mode *adjusted_mode);
|
|
|
|
|
void (*mode_set)(struct exynos_drm_display *display,
|
|
|
|
|
struct drm_display_mode *mode);
|
|
|
|
|
int (*check_mode)(struct exynos_drm_display *display,
|
|
|
|
|
struct drm_display_mode *mode);
|
|
|
|
|
void (*dpms)(struct exynos_drm_display *display, int mode);
|
|
|
|
|
void (*commit)(struct exynos_drm_display *display);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Exynos drm display structure, maps 1:1 with an encoder/connector
|
|
|
|
|
*
|
|
|
|
|
* @list: the list entry for this manager
|
|
|
|
|
* @type: one of EXYNOS_DISPLAY_TYPE_LCD and HDMI.
|
|
|
|
|
* @encoder: encoder object this display maps to
|
|
|
|
|
* @connector: connector object this display maps to
|
|
|
|
|
* @ops: pointer to callbacks for exynos drm specific functionality
|
|
|
|
|
* @ctx: A pointer to the display's implementation specific context
|
|
|
|
|
*/
|
|
|
|
|
struct exynos_drm_display {
|
|
|
|
|
struct list_head list;
|
2011-10-04 10:19:01 +00:00
|
|
|
enum exynos_drm_output_type type;
|
2014-02-19 12:02:55 +00:00
|
|
|
struct drm_encoder *encoder;
|
|
|
|
|
struct drm_connector *connector;
|
|
|
|
|
struct exynos_drm_display_ops *ops;
|
|
|
|
|
void *ctx;
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Exynos drm manager ops
|
|
|
|
|
*
|
2014-01-30 21:19:03 +00:00
|
|
|
* @initialize: initializes the manager with drm_dev
|
2014-02-19 12:02:55 +00:00
|
|
|
* @remove: cleans up the manager for removal
|
2011-12-06 02:06:54 +00:00
|
|
|
* @dpms: control device power.
|
2014-01-30 21:19:19 +00:00
|
|
|
* @mode_fixup: fix mode data before applying it
|
2014-01-30 21:19:18 +00:00
|
|
|
* @mode_set: set the given mode to the manager
|
2011-10-04 10:19:01 +00:00
|
|
|
* @commit: set current hw specific display mode to hw.
|
|
|
|
|
* @enable_vblank: specific driver callback for enabling vblank interrupt.
|
|
|
|
|
* @disable_vblank: specific driver callback for disabling vblank interrupt.
|
2012-12-06 14:46:00 +00:00
|
|
|
* @wait_for_vblank: wait for vblank interrupt to make sure that
|
|
|
|
|
* hardware overlay is updated.
|
2014-01-30 21:19:02 +00:00
|
|
|
* @win_mode_set: copy drm overlay info to hw specific overlay info.
|
|
|
|
|
* @win_commit: apply hardware specific overlay data to registers.
|
|
|
|
|
* @win_enable: enable hardware specific overlay.
|
|
|
|
|
* @win_disable: disable hardware specific overlay.
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
2014-01-30 21:19:06 +00:00
|
|
|
struct exynos_drm_manager;
|
2011-10-04 10:19:01 +00:00
|
|
|
struct exynos_drm_manager_ops {
|
2014-01-30 21:19:06 +00:00
|
|
|
int (*initialize)(struct exynos_drm_manager *mgr,
|
2014-02-19 12:02:55 +00:00
|
|
|
struct drm_device *drm_dev, int pipe);
|
|
|
|
|
void (*remove)(struct exynos_drm_manager *mgr);
|
2014-01-30 21:19:06 +00:00
|
|
|
void (*dpms)(struct exynos_drm_manager *mgr, int mode);
|
2014-01-30 21:19:19 +00:00
|
|
|
bool (*mode_fixup)(struct exynos_drm_manager *mgr,
|
|
|
|
|
const struct drm_display_mode *mode,
|
|
|
|
|
struct drm_display_mode *adjusted_mode);
|
2014-01-30 21:19:18 +00:00
|
|
|
void (*mode_set)(struct exynos_drm_manager *mgr,
|
|
|
|
|
const struct drm_display_mode *mode);
|
2014-01-30 21:19:06 +00:00
|
|
|
void (*commit)(struct exynos_drm_manager *mgr);
|
|
|
|
|
int (*enable_vblank)(struct exynos_drm_manager *mgr);
|
|
|
|
|
void (*disable_vblank)(struct exynos_drm_manager *mgr);
|
|
|
|
|
void (*wait_for_vblank)(struct exynos_drm_manager *mgr);
|
|
|
|
|
void (*win_mode_set)(struct exynos_drm_manager *mgr,
|
2014-01-30 21:19:02 +00:00
|
|
|
struct exynos_drm_overlay *overlay);
|
2014-01-30 21:19:06 +00:00
|
|
|
void (*win_commit)(struct exynos_drm_manager *mgr, int zpos);
|
|
|
|
|
void (*win_enable)(struct exynos_drm_manager *mgr, int zpos);
|
|
|
|
|
void (*win_disable)(struct exynos_drm_manager *mgr, int zpos);
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
2014-02-19 12:02:55 +00:00
|
|
|
* Exynos drm common manager structure, maps 1:1 with a crtc
|
2011-10-04 10:19:01 +00:00
|
|
|
*
|
2014-02-19 12:02:55 +00:00
|
|
|
* @list: the list entry for this manager
|
|
|
|
|
* @type: one of EXYNOS_DISPLAY_TYPE_LCD and HDMI.
|
|
|
|
|
* @drm_dev: pointer to the drm device
|
|
|
|
|
* @pipe: the pipe number for this crtc/manager
|
|
|
|
|
* @ops: pointer to callbacks for exynos drm specific functionality
|
2014-01-30 21:19:06 +00:00
|
|
|
* @ctx: A pointer to the manager's implementation specific context
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
|
|
|
|
struct exynos_drm_manager {
|
2014-02-19 12:02:55 +00:00
|
|
|
struct list_head list;
|
|
|
|
|
enum exynos_drm_output_type type;
|
|
|
|
|
struct drm_device *drm_dev;
|
2011-10-04 10:19:01 +00:00
|
|
|
int pipe;
|
|
|
|
|
struct exynos_drm_manager_ops *ops;
|
2014-01-30 21:19:06 +00:00
|
|
|
void *ctx;
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
2012-05-17 11:06:32 +00:00
|
|
|
struct exynos_drm_g2d_private {
|
|
|
|
|
struct device *dev;
|
|
|
|
|
struct list_head inuse_cmdlist;
|
|
|
|
|
struct list_head event_list;
|
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 13:48:52 +00:00
|
|
|
struct list_head userptr_list;
|
2012-05-17 11:06:32 +00:00
|
|
|
};
|
|
|
|
|
|
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 09:10:31 +00:00
|
|
|
struct exynos_drm_ipp_private {
|
|
|
|
|
struct device *dev;
|
|
|
|
|
struct list_head event_list;
|
|
|
|
|
};
|
|
|
|
|
|
2012-05-17 11:06:32 +00:00
|
|
|
struct drm_exynos_file_private {
|
|
|
|
|
struct exynos_drm_g2d_private *g2d_priv;
|
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 09:10:31 +00:00
|
|
|
struct exynos_drm_ipp_private *ipp_priv;
|
2013-12-20 10:16:24 +00:00
|
|
|
struct file *anon_filp;
|
2012-05-17 11:06:32 +00:00
|
|
|
};
|
|
|
|
|
|
2011-10-04 10:19:01 +00:00
|
|
|
/*
|
|
|
|
|
* Exynos drm private structure.
|
2012-10-20 14:53:42 +00:00
|
|
|
*
|
|
|
|
|
* @da_start: start address to device address space.
|
|
|
|
|
* with iommu, device address space starts from this address
|
|
|
|
|
* otherwise default one.
|
|
|
|
|
* @da_space_size: size of device address space.
|
|
|
|
|
* if 0 then default value is used for it.
|
|
|
|
|
* @da_space_order: order to device address space.
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
|
|
|
|
struct exynos_drm_private {
|
|
|
|
|
struct drm_fb_helper *fb_helper;
|
|
|
|
|
|
2011-10-14 04:29:51 +00:00
|
|
|
/* list head for new event to be added. */
|
2011-10-04 10:19:01 +00:00
|
|
|
struct list_head pageflip_event_list;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* created crtc object would be contained at this array and
|
|
|
|
|
* this array is used to be aware of which crtc did it request vblank.
|
|
|
|
|
*/
|
|
|
|
|
struct drm_crtc *crtc[MAX_CRTC];
|
2012-06-27 05:27:06 +00:00
|
|
|
struct drm_property *plane_zpos_property;
|
2012-06-27 05:27:11 +00:00
|
|
|
struct drm_property *crtc_mode_property;
|
2012-10-20 14:53:42 +00:00
|
|
|
|
|
|
|
|
unsigned long da_start;
|
|
|
|
|
unsigned long da_space_size;
|
|
|
|
|
unsigned long da_space_order;
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Exynos drm sub driver structure.
|
|
|
|
|
*
|
|
|
|
|
* @list: sub driver has its own list object to register to exynos drm driver.
|
2012-04-05 11:49:27 +00:00
|
|
|
* @dev: pointer to device object for subdrv device driver.
|
2011-10-04 10:19:01 +00:00
|
|
|
* @drm_dev: pointer to drm_device and this pointer would be set
|
|
|
|
|
* when sub driver calls exynos_drm_subdrv_register().
|
2012-04-05 11:49:27 +00:00
|
|
|
* @manager: subdrv has its own manager to control a hardware appropriately
|
|
|
|
|
* and we can access a hardware drawing on this manager.
|
2011-10-04 10:19:01 +00:00
|
|
|
* @probe: this callback would be called by exynos drm driver after
|
|
|
|
|
* subdrv is registered to it.
|
|
|
|
|
* @remove: this callback is used to release resources created
|
|
|
|
|
* by probe callback.
|
2012-03-16 09:47:09 +00:00
|
|
|
* @open: this would be called with drm device file open.
|
|
|
|
|
* @close: this would be called with drm device file close.
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
|
|
|
|
struct exynos_drm_subdrv {
|
|
|
|
|
struct list_head list;
|
2012-04-05 11:49:27 +00:00
|
|
|
struct device *dev;
|
2011-10-04 10:19:01 +00:00
|
|
|
struct drm_device *drm_dev;
|
|
|
|
|
|
2011-10-14 04:29:48 +00:00
|
|
|
int (*probe)(struct drm_device *drm_dev, struct device *dev);
|
2012-09-05 05:12:06 +00:00
|
|
|
void (*remove)(struct drm_device *drm_dev, struct device *dev);
|
2012-03-16 09:47:09 +00:00
|
|
|
int (*open)(struct drm_device *drm_dev, struct device *dev,
|
|
|
|
|
struct drm_file *file);
|
|
|
|
|
void (*close)(struct drm_device *drm_dev, struct device *dev,
|
|
|
|
|
struct drm_file *file);
|
2011-10-04 10:19:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* this function calls a probe callback registered to sub driver list and
|
|
|
|
|
* create its own encoder and connector and then set drm_device object
|
|
|
|
|
* to global one.
|
|
|
|
|
*/
|
|
|
|
|
int exynos_drm_device_register(struct drm_device *dev);
|
|
|
|
|
/*
|
|
|
|
|
* this function calls a remove callback registered to sub driver list and
|
|
|
|
|
* destroy its own encoder and connetor.
|
|
|
|
|
*/
|
|
|
|
|
int exynos_drm_device_unregister(struct drm_device *dev);
|
|
|
|
|
|
2014-02-19 12:02:55 +00:00
|
|
|
int exynos_drm_initialize_managers(struct drm_device *dev);
|
|
|
|
|
void exynos_drm_remove_managers(struct drm_device *dev);
|
|
|
|
|
int exynos_drm_initialize_displays(struct drm_device *dev);
|
|
|
|
|
void exynos_drm_remove_displays(struct drm_device *dev);
|
|
|
|
|
|
|
|
|
|
int exynos_drm_manager_register(struct exynos_drm_manager *manager);
|
|
|
|
|
int exynos_drm_manager_unregister(struct exynos_drm_manager *manager);
|
|
|
|
|
int exynos_drm_display_register(struct exynos_drm_display *display);
|
|
|
|
|
int exynos_drm_display_unregister(struct exynos_drm_display *display);
|
|
|
|
|
|
2011-10-04 10:19:01 +00:00
|
|
|
/*
|
|
|
|
|
* this function would be called by sub drivers such as display controller
|
|
|
|
|
* or hdmi driver to register this sub driver object to exynos drm driver
|
|
|
|
|
* and when a sub driver is registered to exynos drm driver a probe callback
|
2012-03-16 09:47:08 +00:00
|
|
|
* of the sub driver is called and creates its own encoder and connector.
|
2011-10-04 10:19:01 +00:00
|
|
|
*/
|
|
|
|
|
int exynos_drm_subdrv_register(struct exynos_drm_subdrv *drm_subdrv);
|
|
|
|
|
|
2012-03-16 09:47:08 +00:00
|
|
|
/* this function removes subdrv list from exynos drm driver */
|
2011-10-04 10:19:01 +00:00
|
|
|
int exynos_drm_subdrv_unregister(struct exynos_drm_subdrv *drm_subdrv);
|
|
|
|
|
|
2012-03-16 09:47:09 +00:00
|
|
|
int exynos_drm_subdrv_open(struct drm_device *dev, struct drm_file *file);
|
|
|
|
|
void exynos_drm_subdrv_close(struct drm_device *dev, struct drm_file *file);
|
|
|
|
|
|
2012-10-16 00:20:13 +00:00
|
|
|
/*
|
|
|
|
|
* this function registers exynos drm hdmi platform device. It ensures only one
|
|
|
|
|
* instance of the device is created.
|
|
|
|
|
*/
|
2013-04-22 09:40:34 +00:00
|
|
|
int exynos_platform_device_hdmi_register(void);
|
2012-10-16 00:20:13 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* this function unregisters exynos drm hdmi platform device if it exists.
|
|
|
|
|
*/
|
|
|
|
|
void exynos_platform_device_hdmi_unregister(void);
|
|
|
|
|
|
2013-04-23 05:02:53 +00:00
|
|
|
/*
|
|
|
|
|
* this function registers exynos drm ipp platform device.
|
|
|
|
|
*/
|
|
|
|
|
int exynos_platform_device_ipp_register(void);
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* this function unregisters exynos drm ipp platform device if it exists.
|
|
|
|
|
*/
|
|
|
|
|
void exynos_platform_device_ipp_unregister(void);
|
|
|
|
|
|
2014-03-17 12:03:56 +00:00
|
|
|
#ifdef CONFIG_DRM_EXYNOS_DPI
|
|
|
|
|
int exynos_dpi_probe(struct device *dev);
|
|
|
|
|
int exynos_dpi_remove(struct device *dev);
|
|
|
|
|
#else
|
|
|
|
|
static inline int exynos_dpi_probe(struct device *dev) { return 0; }
|
|
|
|
|
static inline int exynos_dpi_remove(struct device *dev) { return 0; }
|
|
|
|
|
#endif
|
|
|
|
|
|
2014-01-30 21:19:23 +00:00
|
|
|
extern struct platform_driver dp_driver;
|
2012-03-16 09:47:08 +00:00
|
|
|
extern struct platform_driver fimd_driver;
|
|
|
|
|
extern struct platform_driver hdmi_driver;
|
|
|
|
|
extern struct platform_driver mixer_driver;
|
|
|
|
|
extern struct platform_driver exynos_drm_common_hdmi_driver;
|
2012-03-21 01:55:26 +00:00
|
|
|
extern struct platform_driver vidi_driver;
|
2012-05-17 11:06:32 +00:00
|
|
|
extern struct platform_driver g2d_driver;
|
2012-12-14 08:58:55 +00:00
|
|
|
extern struct platform_driver fimc_driver;
|
2012-12-14 08:58:56 +00:00
|
|
|
extern struct platform_driver rotator_driver;
|
2012-12-14 08:58:57 +00:00
|
|
|
extern struct platform_driver gsc_driver;
|
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 09:10:31 +00:00
|
|
|
extern struct platform_driver ipp_driver;
|
2011-10-04 10:19:01 +00:00
|
|
|
#endif
|
