STRUCT MEDIA_PIPELINE(9)
π¦ struct media_pipeline(9) π¦
okay bestie, welcome to the glow-up era of struct media_pipeline(9) β straight out of the Kernel API Manual, no cap. it's the little struct that holds all the media pipeline related information, and honestly? it's giving backstage-pass energy. π
β¨ NAME β¨
struct media_pipeline β Media pipeline related information π
πΈ SYNOPSIS πΈ
struct media_pipeline {
bool allocated;
struct media_device *mdev;
struct list_head pads;
int start_count;
};
look at her. four fields. immaculate. π
π Members π
allocatedβ Media pipeline allocated and freed by the framework β¨ like, she doesn't book her own hotel room, the framework handles that for her, periodtmdevβ The media device the pipeline is part of π«Ά that's her home base, the device she belongs topadsβ List ofmedia_pipeline_padπ yup, a whole list of them, that's the vibestart_countβ Media pipeline start - stop count π’ literally what it says: the start/stop counter, keeping tally like a main character with a notes app
π SEE ALSO π
Kernel file ./include/media/media-entity.h π§ β and the whole friend group, because she does not travel alone:
enum media_gobj_type(9)struct media_gobj(9)struct media_entity_enum(9)struct media_graph(9)struct media_pipeline_pad(9)struct media_pipeline_pad_iter(9)struct media_pipeline_entity_iter(9)struct media_link(9)enum media_pad_signal_type(9)struct media_pad(9)struct media_entity_operations(9)enum media_entity_type(9)struct media_entity(9)media_entity_for_each_pad(9)struct media_interface(9)struct media_intf_devnode(9)media_entity_id(9)media_type(9)media_id(9)media_gobj_gen_id(9)is_media_entity_v4l2_video_device(9)is_media_entity_v4l2_subdev(9)media_entity_enum_init(9)media_entity_enum_cleanup(9)media_entity_enum_zero(9)media_entity_enum_set(9)media_entity_enum_clear(9)media_entity_enum_test(9)media_entity_enum_test_and_set(9)media_entity_enum_empty(9)media_entity_enum_intersects(9)gobj_to_entity(9)gobj_to_pad(9)gobj_to_link(9)gobj_to_intf(9)intf_to_devnode(9)media_gobj_create(9)media_gobj_destroy(9)media_entity_pads_init(9)media_entity_cleanup(9)media_get_pad_index(9)media_create_pad_link(9)media_create_pad_links(9)media_entity_remove_links(9)__media_entity_setup_link(9)media_entity_setup_link(9)media_entity_find_link(9)media_pad_remote_pad_first(9)media_pad_remote_pad_unique(9)media_entity_remote_pad_unique(9)media_entity_remote_source_pad_unique(9)media_pad_is_streaming(9)media_entity_is_streaming(9)media_entity_pipeline(9)media_pad_pipeline(9)media_entity_get_fwnode_pad(9)media_graph_walk_init(9)media_graph_walk_cleanup(9)media_graph_walk_start(9)media_graph_walk_next(9)media_pipeline_start(9)__media_pipeline_start(9)media_pipeline_stop(9)__media_pipeline_stop(9)media_pipeline_for_each_pad(9)media_pipeline_entity_iter_init(9)media_pipeline_entity_iter_cleanup(9)media_pipeline_for_each_entity(9)media_pipeline_alloc_start(9)media_devnode_create(9)media_devnode_remove(9)media_create_intf_link(9)__media_remove_intf_link(9)media_remove_intf_link(9)__media_remove_intf_links(9)media_remove_intf_links(9)media_entity_call(9)media_create_ancillary_link(9)__media_entity_next_link(9)for_each_media_entity_data_link(9)
bestie that's a LOT of cross-references and yes you should read the relevant ones before you go poking at pipelines, i'm just being honest with you π«Ά
and that's the whole page, mwah π β this edition came from ./include/media, dated October 2026, and it's brought to you by the Kernel API Manual. slay, go read some kernel headers now. ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms