[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2013 Texas Instruments Inc.
|
|
|
|
|
*
|
|
|
|
|
* David Griego, <dagriego@biglakesoftware.com>
|
|
|
|
|
* Dale Farnsworth, <dale@farnsworth.org>
|
|
|
|
|
* Archit Taneja, <archit@ti.com>
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
|
* under the terms of the GNU General Public License version 2 as published by
|
|
|
|
|
* the Free Software Foundation.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __TI_VPDMA_H_
|
|
|
|
|
#define __TI_VPDMA_H_
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* A vpdma_buf tracks the size, DMA address and mapping status of each
|
|
|
|
|
* driver DMA area.
|
|
|
|
|
*/
|
|
|
|
|
struct vpdma_buf {
|
|
|
|
|
void *addr;
|
|
|
|
|
dma_addr_t dma_addr;
|
|
|
|
|
size_t size;
|
|
|
|
|
bool mapped;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct vpdma_desc_list {
|
|
|
|
|
struct vpdma_buf buf;
|
|
|
|
|
void *next;
|
|
|
|
|
int type;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct vpdma_data {
|
|
|
|
|
void __iomem *base;
|
|
|
|
|
|
|
|
|
|
struct platform_device *pdev;
|
|
|
|
|
|
2014-03-13 11:44:04 +00:00
|
|
|
/* callback to VPE driver when the firmware is loaded */
|
|
|
|
|
void (*cb)(struct platform_device *pdev);
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
};
|
|
|
|
|
|
2013-12-12 08:36:04 +00:00
|
|
|
enum vpdma_data_format_type {
|
|
|
|
|
VPDMA_DATA_FMT_TYPE_YUV,
|
|
|
|
|
VPDMA_DATA_FMT_TYPE_RGB,
|
|
|
|
|
VPDMA_DATA_FMT_TYPE_MISC,
|
|
|
|
|
};
|
|
|
|
|
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
struct vpdma_data_format {
|
2013-12-12 08:36:04 +00:00
|
|
|
enum vpdma_data_format_type type;
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
int data_type;
|
|
|
|
|
u8 depth;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define VPDMA_DESC_ALIGN 16 /* 16-byte descriptor alignment */
|
2013-12-03 11:51:13 +00:00
|
|
|
#define VPDMA_STRIDE_ALIGN 16 /*
|
|
|
|
|
* line stride of source and dest
|
|
|
|
|
* buffers should be 16 byte aligned
|
|
|
|
|
*/
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
#define VPDMA_DTD_DESC_SIZE 32 /* 8 words */
|
|
|
|
|
#define VPDMA_CFD_CTD_DESC_SIZE 16 /* 4 words */
|
|
|
|
|
|
|
|
|
|
#define VPDMA_LIST_TYPE_NORMAL 0
|
|
|
|
|
#define VPDMA_LIST_TYPE_SELF_MODIFYING 1
|
|
|
|
|
#define VPDMA_LIST_TYPE_DOORBELL 2
|
|
|
|
|
|
|
|
|
|
enum vpdma_yuv_formats {
|
|
|
|
|
VPDMA_DATA_FMT_Y444 = 0,
|
|
|
|
|
VPDMA_DATA_FMT_Y422,
|
|
|
|
|
VPDMA_DATA_FMT_Y420,
|
|
|
|
|
VPDMA_DATA_FMT_C444,
|
|
|
|
|
VPDMA_DATA_FMT_C422,
|
|
|
|
|
VPDMA_DATA_FMT_C420,
|
|
|
|
|
VPDMA_DATA_FMT_YC422,
|
|
|
|
|
VPDMA_DATA_FMT_YC444,
|
|
|
|
|
VPDMA_DATA_FMT_CY422,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum vpdma_rgb_formats {
|
|
|
|
|
VPDMA_DATA_FMT_RGB565 = 0,
|
|
|
|
|
VPDMA_DATA_FMT_ARGB16_1555,
|
|
|
|
|
VPDMA_DATA_FMT_ARGB16,
|
|
|
|
|
VPDMA_DATA_FMT_RGBA16_5551,
|
|
|
|
|
VPDMA_DATA_FMT_RGBA16,
|
|
|
|
|
VPDMA_DATA_FMT_ARGB24,
|
|
|
|
|
VPDMA_DATA_FMT_RGB24,
|
|
|
|
|
VPDMA_DATA_FMT_ARGB32,
|
|
|
|
|
VPDMA_DATA_FMT_RGBA24,
|
|
|
|
|
VPDMA_DATA_FMT_RGBA32,
|
|
|
|
|
VPDMA_DATA_FMT_BGR565,
|
|
|
|
|
VPDMA_DATA_FMT_ABGR16_1555,
|
|
|
|
|
VPDMA_DATA_FMT_ABGR16,
|
|
|
|
|
VPDMA_DATA_FMT_BGRA16_5551,
|
|
|
|
|
VPDMA_DATA_FMT_BGRA16,
|
|
|
|
|
VPDMA_DATA_FMT_ABGR24,
|
|
|
|
|
VPDMA_DATA_FMT_BGR24,
|
|
|
|
|
VPDMA_DATA_FMT_ABGR32,
|
|
|
|
|
VPDMA_DATA_FMT_BGRA24,
|
|
|
|
|
VPDMA_DATA_FMT_BGRA32,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum vpdma_misc_formats {
|
|
|
|
|
VPDMA_DATA_FMT_MV = 0,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
extern const struct vpdma_data_format vpdma_yuv_fmts[];
|
|
|
|
|
extern const struct vpdma_data_format vpdma_rgb_fmts[];
|
|
|
|
|
extern const struct vpdma_data_format vpdma_misc_fmts[];
|
|
|
|
|
|
|
|
|
|
enum vpdma_frame_start_event {
|
|
|
|
|
VPDMA_FSEVENT_HDMI_FID = 0,
|
|
|
|
|
VPDMA_FSEVENT_DVO2_FID,
|
|
|
|
|
VPDMA_FSEVENT_HDCOMP_FID,
|
|
|
|
|
VPDMA_FSEVENT_SD_FID,
|
|
|
|
|
VPDMA_FSEVENT_LM_FID0,
|
|
|
|
|
VPDMA_FSEVENT_LM_FID1,
|
|
|
|
|
VPDMA_FSEVENT_LM_FID2,
|
|
|
|
|
VPDMA_FSEVENT_CHANNEL_ACTIVE,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* VPDMA channel numbers
|
|
|
|
|
*/
|
|
|
|
|
enum vpdma_channel {
|
|
|
|
|
VPE_CHAN_LUMA1_IN,
|
|
|
|
|
VPE_CHAN_CHROMA1_IN,
|
|
|
|
|
VPE_CHAN_LUMA2_IN,
|
|
|
|
|
VPE_CHAN_CHROMA2_IN,
|
|
|
|
|
VPE_CHAN_LUMA3_IN,
|
|
|
|
|
VPE_CHAN_CHROMA3_IN,
|
|
|
|
|
VPE_CHAN_MV_IN,
|
|
|
|
|
VPE_CHAN_MV_OUT,
|
|
|
|
|
VPE_CHAN_LUMA_OUT,
|
|
|
|
|
VPE_CHAN_CHROMA_OUT,
|
|
|
|
|
VPE_CHAN_RGB_OUT,
|
|
|
|
|
};
|
|
|
|
|
|
2013-10-16 05:36:46 +00:00
|
|
|
/* flags for VPDMA data descriptors */
|
|
|
|
|
#define VPDMA_DATA_ODD_LINE_SKIP (1 << 0)
|
|
|
|
|
#define VPDMA_DATA_EVEN_LINE_SKIP (1 << 1)
|
|
|
|
|
#define VPDMA_DATA_FRAME_1D (1 << 2)
|
|
|
|
|
#define VPDMA_DATA_MODE_TILED (1 << 3)
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* client identifiers used for configuration descriptors
|
|
|
|
|
*/
|
|
|
|
|
#define CFD_MMR_CLIENT 0
|
|
|
|
|
#define CFD_SC_CLIENT 4
|
|
|
|
|
|
|
|
|
|
/* Address data block header format */
|
|
|
|
|
struct vpdma_adb_hdr {
|
|
|
|
|
u32 offset;
|
|
|
|
|
u32 nwords;
|
|
|
|
|
u32 reserved0;
|
|
|
|
|
u32 reserved1;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* helpers for creating ADB headers for config descriptors MMRs as client */
|
|
|
|
|
#define ADB_ADDR(dma_buf, str, fld) ((dma_buf)->addr + offsetof(str, fld))
|
|
|
|
|
#define MMR_ADB_ADDR(buf, str, fld) ADB_ADDR(&(buf), struct str, fld)
|
|
|
|
|
|
|
|
|
|
#define VPDMA_SET_MMR_ADB_HDR(buf, str, hdr, regs, offset_a) \
|
|
|
|
|
do { \
|
|
|
|
|
struct vpdma_adb_hdr *h; \
|
|
|
|
|
struct str *adb = NULL; \
|
|
|
|
|
h = MMR_ADB_ADDR(buf, str, hdr); \
|
|
|
|
|
h->offset = (offset_a); \
|
|
|
|
|
h->nwords = sizeof(adb->regs) >> 2; \
|
|
|
|
|
} while (0)
|
|
|
|
|
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
/* vpdma descriptor buffer allocation and management */
|
|
|
|
|
int vpdma_alloc_desc_buf(struct vpdma_buf *buf, size_t size);
|
|
|
|
|
void vpdma_free_desc_buf(struct vpdma_buf *buf);
|
|
|
|
|
int vpdma_map_desc_buf(struct vpdma_data *vpdma, struct vpdma_buf *buf);
|
|
|
|
|
void vpdma_unmap_desc_buf(struct vpdma_data *vpdma, struct vpdma_buf *buf);
|
|
|
|
|
|
|
|
|
|
/* vpdma descriptor list funcs */
|
|
|
|
|
int vpdma_create_desc_list(struct vpdma_desc_list *list, size_t size, int type);
|
|
|
|
|
void vpdma_reset_desc_list(struct vpdma_desc_list *list);
|
|
|
|
|
void vpdma_free_desc_list(struct vpdma_desc_list *list);
|
|
|
|
|
int vpdma_submit_descs(struct vpdma_data *vpdma, struct vpdma_desc_list *list);
|
|
|
|
|
|
2013-10-16 05:36:46 +00:00
|
|
|
/* helpers for creating vpdma descriptors */
|
|
|
|
|
void vpdma_add_cfd_block(struct vpdma_desc_list *list, int client,
|
|
|
|
|
struct vpdma_buf *blk, u32 dest_offset);
|
|
|
|
|
void vpdma_add_cfd_adb(struct vpdma_desc_list *list, int client,
|
|
|
|
|
struct vpdma_buf *adb);
|
|
|
|
|
void vpdma_add_sync_on_channel_ctd(struct vpdma_desc_list *list,
|
|
|
|
|
enum vpdma_channel chan);
|
2014-03-13 11:44:08 +00:00
|
|
|
void vpdma_add_out_dtd(struct vpdma_desc_list *list, int width,
|
|
|
|
|
const struct v4l2_rect *c_rect,
|
2013-10-16 05:36:46 +00:00
|
|
|
const struct vpdma_data_format *fmt, dma_addr_t dma_addr,
|
|
|
|
|
enum vpdma_channel chan, u32 flags);
|
2014-03-13 11:44:08 +00:00
|
|
|
void vpdma_add_in_dtd(struct vpdma_desc_list *list, int width,
|
|
|
|
|
const struct v4l2_rect *c_rect,
|
2013-10-16 05:36:46 +00:00
|
|
|
const struct vpdma_data_format *fmt, dma_addr_t dma_addr,
|
2014-03-13 11:44:08 +00:00
|
|
|
enum vpdma_channel chan, int field, u32 flags, int frame_width,
|
|
|
|
|
int frame_height, int start_h, int start_v);
|
2013-10-16 05:36:46 +00:00
|
|
|
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
/* vpdma list interrupt management */
|
|
|
|
|
void vpdma_enable_list_complete_irq(struct vpdma_data *vpdma, int list_num,
|
|
|
|
|
bool enable);
|
|
|
|
|
void vpdma_clear_list_stat(struct vpdma_data *vpdma);
|
|
|
|
|
|
|
|
|
|
/* vpdma client configuration */
|
|
|
|
|
void vpdma_set_line_mode(struct vpdma_data *vpdma, int line_mode,
|
|
|
|
|
enum vpdma_channel chan);
|
|
|
|
|
void vpdma_set_frame_start_event(struct vpdma_data *vpdma,
|
|
|
|
|
enum vpdma_frame_start_event fs_event, enum vpdma_channel chan);
|
|
|
|
|
|
|
|
|
|
void vpdma_dump_regs(struct vpdma_data *vpdma);
|
|
|
|
|
|
|
|
|
|
/* initialize vpdma, passed with VPE's platform device pointer */
|
2014-03-13 11:44:04 +00:00
|
|
|
struct vpdma_data *vpdma_create(struct platform_device *pdev,
|
|
|
|
|
void (*cb)(struct platform_device *pdev));
|
[media] v4l: ti-vpe: Create a vpdma helper library
The primary function of VPDMA is to move data between external memory
and internal processing modules(in our case, VPE) that source or sink
data. VPDMA is capable of buffering this data and then delivering the
data as demanded to the modules as programmed. The modules that source
or sink data are referred to as clients or ports. A channel is setup
inside the VPDMA to connect a specific memory buffer to a specific
client. The VPDMA centralizes the DMA control functions and buffering
required to allow all the clients to minimize the effect of long latency
times.
Add the following to the VPDMA helper:
- A data struct which describe VPDMA channels. For now, these channels
are the ones used only by VPE, the list of channels will increase when
VIP(Video Input Port) also uses the VPDMA library. This channel
information will be used to populate fields required by data
descriptors.
- Data structs which describe the different data types supported by
VPDMA. This data type information will be used to populate fields
required by data descriptors and used by the VPE driver to map a V4L2
format to the corresponding VPDMA data type.
- Provide VPDMA register offset definitions, functions to read, write
and modify VPDMA registers.
- Functions to create and submit a VPDMA list. A list is a group of
descriptors that makes up a set of DMA transfers that need to be
completed. Each descriptor will either perform a DMA transaction to
fetch input buffers and write to output buffers(data descriptors), or
configure the MMRs of sub blocks of VPE(configuration descriptors), or
provide control information to VPDMA (control descriptors).
- Functions to allocate, map and unmap buffers needed for the descriptor
list, payloads containing MMR values and scaler coefficients. These use
the DMA mapping APIs to ensure exclusive access to VPDMA.
- Functions to enable VPDMA interrupts. VPDMA can trigger an interrupt
on the VPE interrupt line when a descriptor list is parsed completely
and the DMA transactions are completed. This requires masking the events
in VPDMA registers and configuring some top level VPE interrupt
registers.
- Enable some VPDMA specific parameters: frame start event(when to start
DMA for a client) and line mode(whether each line fetched should be
mirrored or not).
- Function to load firmware required by VPDMA. VPDMA requires a firmware
for it's internal list manager. We add the required request_firmware
apis to fetch this firmware from user space.
- Function to dump VPDMA registers.
- A function to initialize and create a VPDMA instance, this will be
called by the VPE driver with it's platform device pointer, this
function will take care of loading VPDMA firmware and returning a
vpdma_data instance back to the VPE driver. The VIP driver will also
call the same init function to initialize it's own VPDMA instance.
Signed-off-by: Archit Taneja <archit@ti.com>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Kamil Debski <k.debski@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
2013-10-16 05:36:45 +00:00
|
|
|
|
|
|
|
|
#endif
|