Searched full:applications (Results 1 – 25 of 2082) sorted by relevance
12345678910>>...84
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-parm.rst | 38 Applications can request a different frame interval. The capture or
53 To get and set the streaming parameters applications call the
105 - Set by drivers and applications, see :ref:`parm-flags`.
120 Applications store here the desired frame period, drivers return
125 period. To reset manually applications can just set this field to
133 applications and drivers must set this field to zero. Applications
138 - Applications set this field to the desired number of buffers used
146 - Reserved for future extensions. Drivers and applications must set
164 - Set by drivers and applications, see :ref:`parm-flags`.
180 Applications store here the desired frame period, drivers return
[all …]
|
| D | format.rst | 13 Different devices exchange different kinds of data with applications,
18 applications should always negotiate a data format before engaging in
21 to satisfy the request. Of course applications can also just query the
35 initialization sequence. Prior to this point multiple panel applications
53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
66 All drivers exchanging data with applications must support the
78 by all drivers exchanging image data with applications.
85 routine or library for integration into applications.
90 seems useless, but there are applications serving as proxy between
91 drivers and the actual video applications for which this is useful.
|
| D | vidioc-g-priority.rst | 38 To query the current access priority applications call the
42 To request an access priority applications store the desired priority in
60 - Lowest priority, usually applications running in background, for
62 in user space will be necessary if multiple applications want to
69 - Medium priority, usually applications started and interactively
71 or just "panel" applications to change the channel or video
78 applications which must not be interrupted, like video recording.
|
| D | app-pri.rst | 9 When multiple applications share a device it may be desirable to assign
12 applications from changing video controls or switching the current TV
13 channel. Another objective is to permit low priority applications
15 applications and automatically regain control of the device at a later
23 V4L2 and drivers not supporting these ioctls. Applications requiring a
|
| D | dev-overlay.rst | 34 Applications should use different file descriptors for capturing and
66 Before overlay can commence applications must program the driver with
75 supposed to run TV applications as root or with SUID bit set. A small
124 To get the current parameters applications set the ``type`` field of a
131 To program the overlay window applications set the ``type`` field of a
167 Applications set this field to determine which video field shall be
175 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` applications set this field
186 applications can set this field to point to an array of clipping
192 height, and they must not overlap. If possible applications
209 applications can set this field to point to a clipping bit mask.
[all …]
|
| D | vidioc-g-fbuf.rst | 38 Applications can use the :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` and :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBU…
52 To get the current parameters applications call the :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
57 To set the parameters for a *Video Output Overlay*, applications must
67 applications must initialize the ``flags`` field, the ``fmt``
72 For a *destructive Video Overlay* applications must additionally provide
108 *destructive Video Overlays* applications must provide a base
111 the driver must return a valid base address, so applications can
139 - For *destructive Video Overlays* applications must initialize this
155 - Drivers and applications shall ignore this field. If applicable,
168 For *destructive Video Overlays* both applications and drivers can
[all …]
|
| D | vidioc-enum-dv-timings.rst | 40 applications can enumerate a list of known supported timings. Call
45 To query the available timings, applications initialize the ``index``
51 DV timings, applications shall begin at index zero, incrementing by one
62 or outputs (for DV transmitters), applications must specify the desired
84 video node applications must set this field to zero.
87 - Reserved for future extensions. Drivers and applications must set
|
| D | dev-subdev.rst | 17 media entities. Applications will be able to enumerate the sub-devices
22 make them directly configurable by applications. When both the
46 Applications can control all sub-devices through a single interface.
55 Applications can access those hidden controls through the sub-device
68 V4L2 sub-devices can notify applications of events as described in
84 V4L2 applications do *not* need to use the API described in this
120 configured differently. Applications need to configure the formats at
124 can expose pad-level image format configuration to applications. When
125 they do, applications can use the
130 Applications are responsible for configuring coherent parameters on the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-parm.rst | 38 Applications can request a different frame interval. The capture or
53 To get and set the streaming parameters applications call the
104 - Set by drivers and applications, see :ref:`parm-flags`.
119 Applications store here the desired frame period, drivers return
124 period. To reset manually applications can just set this field to
132 applications and drivers must set this field to zero. Applications
137 - Applications set this field to the desired number of buffers used
145 - Reserved for future extensions. Drivers and applications must set
163 - Set by drivers and applications, see :ref:`parm-flags`.
179 Applications store here the desired frame period, drivers return
[all …]
|
| D | format.rst | 13 Different devices exchange different kinds of data with applications,
18 applications should always negotiate a data format before engaging in
21 to satisfy the request. Of course applications can also just query the
35 initialization sequence. Prior to this point multiple panel applications
53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
66 All drivers exchanging data with applications must support the
78 by all drivers exchanging image data with applications.
85 routine or library for integration into applications.
90 seems useless, but there are applications serving as proxy between
91 drivers and the actual video applications for which this is useful.
|
| D | vidioc-g-priority.rst | 38 To query the current access priority applications call the
42 To request an access priority applications store the desired priority in
60 - Lowest priority, usually applications running in background, for
62 in user space will be necessary if multiple applications want to
69 - Medium priority, usually applications started and interactively
71 or just "panel" applications to change the channel or video
78 applications which must not be interrupted, like video recording.
|
| D | app-pri.rst | 9 When multiple applications share a device it may be desirable to assign
12 applications from changing video controls or switching the current TV
13 channel. Another objective is to permit low priority applications
15 applications and automatically regain control of the device at a later
23 V4L2 and drivers not supporting these ioctls. Applications requiring a
|
| D | dev-overlay.rst | 34 Applications should use different file descriptors for capturing and
71 Before overlay can commence applications must program the driver with
80 supposed to run TV applications as root or with SUID bit set. A small
131 To get the current parameters applications set the ``type`` field of a
138 To program the overlay window applications set the ``type`` field of a
174 Applications set this field to determine which video field shall be
182 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` applications set this field
194 applications can set this field to point to an array of clipping
200 height, and they must not overlap. If possible applications
219 applications can set this field to point to a clipping bit mask.
[all …]
|
| D | vidioc-enum-dv-timings.rst | 40 applications can enumerate a list of known supported timings. Call
45 To query the available timings, applications initialize the ``index``
51 DV timings, applications shall begin at index zero, incrementing by one
62 or outputs (for DV transmitters), applications must specify the desired
84 video node applications must set this field to zero.
87 - Reserved for future extensions. Drivers and applications must set
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | megaraid.rst | 11 user applications in a similar way. They understand the same firmware control
12 commands. Furthermore, the applications also can treat different classes of
14 interfaces with the applications on one side and all the low level drivers
23 iv. Applications have to interface with only module instead of
63 The applications interface with the common module via the character device
68 applications into uioc_t. After driver handles the uioc_t, the common module
69 will convert that back into the old format before returning to applications.
71 As new applications evolve and replace the old ones, the old packet format
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | megaraid.rst | 11 user applications in a similar way. They understand the same firmware control
12 commands. Furthermore, the applications also can treat different classes of
14 interfaces with the applications on one side and all the low level drivers
23 iv. Applications have to interface with only module instead of
63 The applications interface with the common module via the character device
68 applications into uioc_t. After driver handles the uioc_t, the common module
69 will convert that back into the old format before returning to applications.
71 As new applications evolve and replace the old ones, the old packet format
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | api.rst | 11 This document describes the frame buffer API used by applications to interact
17 the recommended API implementation, but applications should be prepared to
46 Pixels are stored in memory in hardware-dependent formats. Applications need
148 Screen information are queried by applications using the FBIOGET_FSCREENINFO
154 be directly modified by applications, but can be changed by the driver when an
222 To modify variable information, applications call the FBIOPUT_VSCREENINFO
227 applications should call the FBIOGET_VSCREENINFO ioctl and modify only the
240 for applications when using RGB and grayscale formats, as well as legacy
243 To select a format, applications set the fb_var_screeninfo bits_per_pixel field
247 - For grayscale formats, applications set the grayscale field to one. The red,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/fb/ |
| D | api.rst | 11 This document describes the frame buffer API used by applications to interact
17 the recommended API implementation, but applications should be prepared to
46 Pixels are stored in memory in hardware-dependent formats. Applications need
148 Screen information are queried by applications using the FBIOGET_FSCREENINFO
154 be directly modified by applications, but can be changed by the driver when an
222 To modify variable information, applications call the FBIOPUT_VSCREENINFO
227 applications should call the FBIOGET_VSCREENINFO ioctl and modify only the
240 for applications when using RGB and grayscale formats, as well as legacy
243 To select a format, applications set the fb_var_screeninfo bits_per_pixel field
247 - For grayscale formats, applications set the grayscale field to one. The red,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 13 devices directly to applications, in a manner that allows the numerous and
17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
39 - Enable/Disable reporting of RIO port-write events to user-space applications
58 as user-space applications while using remaining functionality provided by
99 5. User-space Applications and API
102 API library and applications that use this device driver are available from
|
| D | rio_cm.rst | 16 to applications, in a manner that allows the numerous and varied RapidIO
19 This driver (RIO_CM) provides to user-space applications shared access to
26 have reduced number of messaging mailboxes. RapidIO aware applications must
31 operations using a single messaging mailbox. This allows applications to
39 Following ioctl commands are available to user-space applications:
87 user-space applications are defined in 'include/uapi/linux/rio_cm_cdev.h'.
126 5. User-space Applications and API Library
129 Messaging API library and applications that use this device driver are available
|
| /kernel/linux/linux-6.6/Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 13 devices directly to applications, in a manner that allows the numerous and
17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
39 - Enable/Disable reporting of RIO port-write events to user-space applications
58 as user-space applications while using remaining functionality provided by
99 5. User-space Applications and API
102 API library and applications that use this device driver are available from
|
| D | rio_cm.rst | 16 to applications, in a manner that allows the numerous and varied RapidIO
19 This driver (RIO_CM) provides to user-space applications shared access to
26 have reduced number of messaging mailboxes. RapidIO aware applications must
31 operations using a single messaging mailbox. This allows applications to
39 Following ioctl commands are available to user-space applications:
87 user-space applications are defined in 'include/uapi/linux/rio_cm_cdev.h'.
126 5. User-space Applications and API Library
129 Messaging API library and applications that use this device driver are available
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-platform-dell-privacy-wmi | 14 Identifies the local microphone can be muted by hardware, no applications
44 consumed by various applications interested in knowing the Privacy
49 Identifies the local microphone can be muted by hardware, no applications
60 and cannot send stream to OS applications
65 and camera module to OS applications
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | bfq-iosched.rst | 10 low latency for time-sensitive applications, such as audio or video
81 Low latency for interactive applications
99 applications experience high latencies, or even become unresponsive
102 Low latency for soft real-time applications
104 Also soft real-time applications, such as audio and video
106 of the background I/O workload. As a consequence, these applications
130 among I/O-bound applications in proportion their weights, with any
135 applications that would otherwise cause a throughput loss.
149 * real-time recording of data in live-dumping applications (e.g.,
211 real-time applications (e.g., video or audio players/streamers),
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | media-controller-intro.rst | 15 presented to userspace applications as V4L2 and ALSA capture devices.
18 available directly to applications by the drivers, can usually be
28 applications to access hardware parameters. As newer hardware expose an
30 applications really require based on limited information, thereby
|
12345678910>>...84