drivers/media/test-drivers/vidtv/vidtv_pes.h
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/vidtv/vidtv_pes.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/vidtv/vidtv_pes.h- Extension
.h- Size
- 5371 bytes
- Lines
- 194
- 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
linux/types.hvidtv_common.h
Detected Declarations
struct vidtv_pes_optional_ptsstruct vidtv_pes_optional_pts_dtsstruct vidtv_pes_optionalstruct vidtv_mpeg_pesstruct pes_header_write_argsstruct pes_ts_header_write_argsstruct pes_write_args
Annotated Snippet
struct vidtv_pes_optional_pts {
u8 pts1;
__be16 pts2;
__be16 pts3;
} __packed;
/* Used when sending both PTS and DTS */
struct vidtv_pes_optional_pts_dts {
u8 pts1;
__be16 pts2;
__be16 pts3;
u8 dts1;
__be16 dts2;
__be16 dts3;
} __packed;
/* PES optional flags */
struct vidtv_pes_optional {
/*
* These flags show which components are actually
* present in the "optional fields" in the optional PES
* header and which are not
*
* u16 two:2; //0x2
* u16 PES_scrambling_control:2;
* u16 PES_priority:1;
* u16 data_alignment_indicator:1; // unused
* u16 copyright:1;
* u16 original_or_copy:1;
* u16 PTS_DTS:2;
* u16 ESCR:1;
* u16 ES_rate:1;
* u16 DSM_trick_mode:1;
* u16 additional_copy_info:1;
* u16 PES_CRC:1;
* u16 PES_extension:1;
*/
__be16 bitfield;
u8 length;
} __packed;
/* The PES header */
struct vidtv_mpeg_pes {
__be32 bitfield; /* packet_start_code_prefix:24, stream_id: 8 */
/* after this field until the end of the PES data payload */
__be16 length;
struct vidtv_pes_optional optional[];
} __packed;
/**
* struct pes_header_write_args - Arguments to write a PES header.
* @dest_buf: The buffer to write into.
* @dest_offset: where to start writing in the dest_buffer.
* @dest_buf_sz: The size of the dest_buffer
* @encoder_id: Encoder id (see vidtv_encoder.h)
* @send_pts: Should we send PTS?
* @pts: PTS value to send.
* @send_dts: Should we send DTS?
* @dts: DTS value to send.
* @stream_id: The stream id to use. Ex: Audio streams (0xc0-0xdf), Video
* streams (0xe0-0xef).
* @n_pes_h_s_bytes: Padding bytes. Might be used by an encoder if needed, gets
* discarded by the decoder.
* @access_unit_len: The size of _one_ access unit (with any headers it might need)
*/
struct pes_header_write_args {
void *dest_buf;
u32 dest_offset;
u32 dest_buf_sz;
u32 encoder_id;
bool send_pts;
u64 pts;
bool send_dts;
u64 dts;
u16 stream_id;
/* might be used by an encoder if needed, gets discarded by decoder */
u32 n_pes_h_s_bytes;
u32 access_unit_len;
};
/**
* struct pes_ts_header_write_args - Arguments to write a TS header.
* @dest_buf: The buffer to write into.
* @dest_offset: where to start writing in the dest_buffer.
* @dest_buf_sz: The size of the dest_buffer
* @pid: The PID to use for the TS packets.
Annotation
- Immediate include surface: `linux/types.h`, `vidtv_common.h`.
- Detected declarations: `struct vidtv_pes_optional_pts`, `struct vidtv_pes_optional_pts_dts`, `struct vidtv_pes_optional`, `struct vidtv_mpeg_pes`, `struct pes_header_write_args`, `struct pes_ts_header_write_args`, `struct pes_write_args`.
- 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.