drivers/media/platform/mediatek/vcodec/encoder/venc_drv_if.h
Source file repositories/reference/linux-study-clean/drivers/media/platform/mediatek/vcodec/encoder/venc_drv_if.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/mediatek/vcodec/encoder/venc_drv_if.h- Extension
.h- Size
- 5061 bytes
- Lines
- 170
- Domain
- Driver Families
- Bucket
- drivers/media
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
mtk_vcodec_enc_drv.h
Detected Declarations
struct venc_enc_paramstruct venc_frame_infostruct venc_frm_bufstruct venc_done_resultenum venc_yuv_fmtenum venc_start_optenum venc_set_param_type
Annotated Snippet
struct venc_enc_param {
enum venc_yuv_fmt input_yuv_fmt;
unsigned int h264_profile;
unsigned int h264_level;
unsigned int width;
unsigned int height;
unsigned int buf_width;
unsigned int buf_height;
unsigned int frm_rate;
unsigned int intra_period;
unsigned int bitrate;
unsigned int gop_size;
};
/**
* struct venc_frame_info - per-frame information to pass to the firmware.
*
* @frm_count: sequential number for this frame
* @skip_frm_count: number of frames skipped so far while decoding
* @frm_type: type of the frame, from enum venc_h264_frame_type
*/
struct venc_frame_info {
unsigned int frm_count; /* per frame update */
unsigned int skip_frm_count; /* per frame update */
unsigned int frm_type; /* per frame update */
};
/*
* struct venc_frm_buf - frame buffer information used in venc_if_encode()
* @fb_addr: plane frame buffer addresses
*/
struct venc_frm_buf {
struct mtk_vcodec_fb fb_addr[MTK_VCODEC_MAX_PLANES];
};
/*
* struct venc_done_result - This is return information used in venc_if_encode()
* @bs_size: output bitstream size
* @is_key_frm: output is key frame or not
*/
struct venc_done_result {
unsigned int bs_size;
bool is_key_frm;
};
extern const struct venc_common_if venc_h264_if;
extern const struct venc_common_if venc_vp8_if;
/*
* venc_if_init - Create the driver handle
* @ctx: device context
* @fourcc: encoder input format
* Return: 0 if creating handle successfully, otherwise it is failed.
*/
int venc_if_init(struct mtk_vcodec_enc_ctx *ctx, unsigned int fourcc);
/*
* venc_if_deinit - Release the driver handle
* @ctx: device context
* Return: 0 if releasing handle successfully, otherwise it is failed.
*/
int venc_if_deinit(struct mtk_vcodec_enc_ctx *ctx);
/*
* venc_if_set_param - Set parameter to driver
* @ctx: device context
* @type: parameter type
* @in: input parameter
* Return: 0 if setting param successfully, otherwise it is failed.
*/
int venc_if_set_param(struct mtk_vcodec_enc_ctx *ctx,
enum venc_set_param_type type,
struct venc_enc_param *in);
/*
* venc_if_encode - Encode one frame
* @ctx: device context
* @opt: encode frame option
* @frm_buf: input frame buffer information
* @bs_buf: output bitstream buffer information
* @result: encode result
* Return: 0 if encoding frame successfully, otherwise it is failed.
*/
int venc_if_encode(struct mtk_vcodec_enc_ctx *ctx,
enum venc_start_opt opt,
struct venc_frm_buf *frm_buf,
struct mtk_vcodec_mem *bs_buf,
struct venc_done_result *result);
#endif /* _VENC_DRV_IF_H_ */
Annotation
- Immediate include surface: `mtk_vcodec_enc_drv.h`.
- Detected declarations: `struct venc_enc_param`, `struct venc_frame_info`, `struct venc_frm_buf`, `struct venc_done_result`, `enum venc_yuv_fmt`, `enum venc_start_opt`, `enum venc_set_param_type`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.