Lines Matching refs:media

1 Linux kernel media framework
4 This document describes the Linux kernel media framework, its data structures,
11 The media controller API is documented in DocBook format in
12 Documentation/DocBook/media/v4l/media-controller.xml. This document will focus
13 on the kernel-side implementation of the media framework.
16 Abstract media device model
20 of the goals of the media framework. To achieve this, hardware devices are
24 An entity is a basic media hardware building block. It can correspond to
43 A media device is represented by a struct media_device instance, defined in
44 include/media/media-device.h. Allocation of the structure is handled by the
45 media device driver, usually by embedding the media_device instance in a
48 Drivers register media device instances by calling
83 Upon successful registration a character device named media[0-9]+ is created.
87 Drivers unregister media device instances by calling
91 Unregistering a media device that hasn't been registered is *NOT* safe.
100 include/media/media-entity.h. The structure is usually embedded into a
127 Drivers register entities with a media device by calling
134 media controller framework to assign an ID automatically. Drivers that provide
145 When a media device is unregistered, all its entities are unregistered
165 field belongs to the media device driver and must not by touched by entity
171 	- ALSA, VBI and video nodes that carry the same media stream
177 include/media/media-entity.h. Each entity stores its pads in a pads array
196 include/media/media-entity.h. Each entity stores all links originating at or
213 	to transfer media data. When two or more links target a sink pad, only
224 The media framework provides APIs to iterate over entities in a graph.
226 To iterate over all entities belonging to a media device, drivers can use the
227 media_device_for_each_entity macro, defined in include/media/media-device.h.
237 reached only through enabled links starting at a given entity. The media
277 the media controller does not implement power management. However, the
278 media_entity structure includes a use_count field that media drivers can use to
281 The use_count field is owned by media drivers and must not be touched by entity
282 drivers. Access to the field must be protected by the media device graph_mutex
298 When a link is enabled or disabled, the media framework calls the
318 Pipelines and media streams