mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-26 05:45:13 +07:00
54f38fcae5
Since 2017, there is an space reserved for userspace API,
created by changeset 1d596dee38 ("docs: Create a user-space API guide").
As the media subsystem was one of the first subsystems to use
Sphinx, until this patch, we were keeping things on a separate
place.
Let's just use the new location, as having all uAPI altogether
will likely make things easier for developers.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
38 lines
1.7 KiB
ReStructuredText
38 lines
1.7 KiB
ReStructuredText
.. Permission is granted to copy, distribute and/or modify this
|
|
.. document under the terms of the GNU Free Documentation License,
|
|
.. Version 1.1 or any later version published by the Free Software
|
|
.. Foundation, with no Invariant Sections, no Front-Cover Texts
|
|
.. and no Back-Cover Texts. A copy of the license is included at
|
|
.. Documentation/userspace-api/media/fdl-appendix.rst.
|
|
..
|
|
.. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
|
|
|
|
.. _app-pri:
|
|
|
|
********************
|
|
Application Priority
|
|
********************
|
|
|
|
When multiple applications share a device it may be desirable to assign
|
|
them different priorities. Contrary to the traditional "rm -rf /" school
|
|
of thought, a video recording application could for example block other
|
|
applications from changing video controls or switching the current TV
|
|
channel. Another objective is to permit low priority applications
|
|
working in background, which can be preempted by user controlled
|
|
applications and automatically regain control of the device at a later
|
|
time.
|
|
|
|
Since these features cannot be implemented entirely in user space V4L2
|
|
defines the :ref:`VIDIOC_G_PRIORITY <VIDIOC_G_PRIORITY>` and
|
|
:ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctls to request and
|
|
query the access priority associate with a file descriptor. Opening a
|
|
device assigns a medium priority, compatible with earlier versions of
|
|
V4L2 and drivers not supporting these ioctls. Applications requiring a
|
|
different priority will usually call :ref:`VIDIOC_S_PRIORITY
|
|
<VIDIOC_G_PRIORITY>` after verifying the device with the
|
|
:ref:`VIDIOC_QUERYCAP` ioctl.
|
|
|
|
Ioctls changing driver properties, such as
|
|
:ref:`VIDIOC_S_INPUT <VIDIOC_G_INPUT>`, return an ``EBUSY`` error code
|
|
after another application obtained higher priority.
|