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

TOMOYO Linux Cross Reference
Linux/Documentation/userspace-api/media/mediactl/media-controller-intro.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 ] ~

Diff markup

Differences between /Documentation/userspace-api/media/mediactl/media-controller-intro.rst (Architecture m68k) and /Documentation/userspace-api/media/mediactl/media-controller-intro.rst (Architecture alpha)


  1 .. SPDX-License-Identifier: GFDL-1.1-no-invari      1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
  2                                                     2 
  3 .. _media-controller-intro:                         3 .. _media-controller-intro:
  4                                                     4 
  5 Introduction                                        5 Introduction
  6 ============                                        6 ============
  7                                                     7 
  8 Media devices increasingly handle multiple rel      8 Media devices increasingly handle multiple related functions. Many USB
  9 cameras include microphones, video capture har      9 cameras include microphones, video capture hardware can also output
 10 video, or SoC camera interfaces also perform m     10 video, or SoC camera interfaces also perform memory-to-memory operations
 11 similar to video codecs.                           11 similar to video codecs.
 12                                                    12 
 13 Independent functions, even when implemented i     13 Independent functions, even when implemented in the same hardware, can
 14 be modelled as separate devices. A USB camera      14 be modelled as separate devices. A USB camera with a microphone will be
 15 presented to userspace applications as V4L2 an     15 presented to userspace applications as V4L2 and ALSA capture devices.
 16 The devices' relationships (when using a webca     16 The devices' relationships (when using a webcam, end-users shouldn't
 17 have to manually select the associated USB mic     17 have to manually select the associated USB microphone), while not made
 18 available directly to applications by the driv     18 available directly to applications by the drivers, can usually be
 19 retrieved from sysfs.                              19 retrieved from sysfs.
 20                                                    20 
 21 With more and more advanced SoC devices being      21 With more and more advanced SoC devices being introduced, the current
 22 approach will not scale. Device topologies are     22 approach will not scale. Device topologies are getting increasingly
 23 complex and can't always be represented by a t     23 complex and can't always be represented by a tree structure. Hardware
 24 blocks are shared between different functions,     24 blocks are shared between different functions, creating dependencies
 25 between seemingly unrelated devices.               25 between seemingly unrelated devices.
 26                                                    26 
 27 Kernel abstraction APIs such as V4L2 and ALSA      27 Kernel abstraction APIs such as V4L2 and ALSA provide means for
 28 applications to access hardware parameters. As     28 applications to access hardware parameters. As newer hardware expose an
 29 increasingly high number of those parameters,      29 increasingly high number of those parameters, drivers need to guess what
 30 applications really require based on limited i     30 applications really require based on limited information, thereby
 31 implementing policies that belong to userspace     31 implementing policies that belong to userspace.
 32                                                    32 
 33 The media controller API aims at solving those     33 The media controller API aims at solving those problems.
                                                      

~ [ 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