~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/userspace-api/media/mediactl/media-controller-model.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
  2 
  3 .. _media-controller-model:
  4 
  5 Media device model
  6 ==================
  7 
  8 Discovering a device internal topology, and configuring it at runtime,
  9 is one of the goals of the media controller API. To achieve this,
 10 hardware devices and Linux Kernel interfaces are modelled as graph
 11 objects on an oriented graph. The object types that constitute the graph
 12 are:
 13 
 14 -  An **entity** is a basic media hardware or software building block.
 15    It can correspond to a large variety of logical blocks such as
 16    physical hardware devices (CMOS sensor for instance), logical
 17    hardware devices (a building block in a System-on-Chip image
 18    processing pipeline), DMA channels or physical connectors.
 19 
 20 -  An **interface** is a graph representation of a Linux Kernel
 21    userspace API interface, like a device node or a sysfs file that
 22    controls one or more entities in the graph.
 23 
 24 -  A **pad** is a data connection endpoint through which an entity can
 25    interact with other entities. Data (not restricted to video) produced
 26    by an entity flows from the entity's output to one or more entity
 27    inputs. Pads should not be confused with physical pins at chip
 28    boundaries.
 29 
 30 -  A **data link** is a point-to-point oriented connection between two
 31    pads, either on the same entity or on different entities. Data flows
 32    from a source pad to a sink pad.
 33 
 34 -  An **interface link** is a point-to-point bidirectional control
 35    connection between a Linux Kernel interface and an entity.
 36 
 37 - An **ancillary link** is a point-to-point connection denoting that two
 38   entities form a single logical unit. For example this could represent the
 39   fact that a particular camera sensor and lens controller form a single
 40   physical module, meaning this lens controller drives the lens for this
 41   camera sensor.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php