Searched full:applications (Results 1 – 25 of 1956) sorted by relevance
12345678910>>...79
| /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-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 | 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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-g-parm.rst | 40 applications can request frame skipping or duplicating on the driver
49 To get and set the streaming parameters applications call the
106 - Set by drivers and applications, see :ref:`parm-flags`.
113 Applications store here the desired frame period, drivers return
119 period. To reset manually applications can just set this field to
127 applications and drivers must set this field to zero. Applications
132 - Applications set this field to the desired number of buffers used
140 - Reserved for future extensions. Drivers and applications must set
159 - Set by drivers and applications, see :ref:`parm-flags`.
170 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
79 by all drivers exchanging image data with applications.
86 routine or library for integration into applications.
91 seems useless, but there are applications serving as proxy between
92 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
61 - Lowest priority, usually applications running in background, for
63 in user space will be necessary if multiple applications want to
70 - Medium priority, usually applications started and interactively
72 or just "panel" applications to change the channel or video
79 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 | vidioc-qbuf.rst | 38 Applications call the ``VIDIOC_QBUF`` ioctl to enqueue an empty
42 To enqueue a buffer applications set the ``type`` field of a struct
46 Applications must also set the ``index`` field. Valid index numbers
54 or ``V4L2_BUF_TYPE_VBI_OUTPUT``) applications must also initialize the
56 for details. Applications must also set ``flags`` to 0. The
63 To enqueue a :ref:`memory mapped <mmap>` buffer applications set the
70 To enqueue a :ref:`user pointer <userp>` buffer applications set the
85 To enqueue a :ref:`DMABUF <dmabuf>` buffer applications set the
101 Applications call the ``VIDIOC_DQBUF`` ioctl to dequeue a filled
|
| 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-reqbufs.rst | 38 space. User buffers are allocated by applications themselves, and this
41 allocated by applications through a device driver, and this ioctl only
45 To allocate device buffers applications initialize all fields of the
61 Applications can call :ref:`VIDIOC_REQBUFS` again to change the number of
87 - Applications set this field to ``V4L2_MEMORY_MMAP``,
92 - A place holder for future extensions. Drivers and applications
|
| 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
85 video node applications must set this field to zero.
88 - Reserved for future extensions. Drivers and applications must set
|
| 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
109 *destructive Video Overlays* applications must provide a base
112 the driver must return a valid base address, so applications can
140 - For *destructive Video Overlays* applications must initialize this
156 - Drivers and applications shall ignore this field. If applicable,
169 For *destructive Video Overlays* both applications and drivers can
[all …]
|
| D | open.rst | 56 means applications cannot *reliable* scan for loaded or installed
73 'feature' was never used by applications and many drivers did not
105 application captures video and audio. In other words, panel applications
116 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl) and other applications are
123 descriptor. Applications can request additional access privileges using
130 V4L2 drivers should not support multiple applications reading or writing
139 To open and close V4L2 devices applications use the
158 not required, so applications cannot know if it really works.
|
| /kernel/linux/linux-4.19/Documentation/scsi/ |
| D | megaraid.txt | 8 user applications in a similar way. They understand the same firmware control
9 commands. Furthermore, the applications also can treat different classes of
11 interfaces with the applications on one side and all the low level drivers
20 iv. Applications have to interface with only module instead of
56 The applications interface with the common module via the character device
61 applications into uioc_t. After driver handles the uioc_t, the common module
62 will convert that back into the old format before returning to applications.
64 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-4.19/Documentation/fb/ |
| D | api.txt | 10 This document describes the frame buffer API used by applications to interact
16 the recommended API implementation, but applications should be prepared to
45 Pixels are stored in memory in hardware-dependent formats. Applications need
147 Screen information are queried by applications using the FBIOGET_FSCREENINFO
153 be directly modified by applications, but can be changed by the driver when an
221 To modify variable information, applications call the FBIOPUT_VSCREENINFO
226 applications should call the FBIOGET_VSCREENINFO ioctl and modify only the
239 for applications when using RGB and grayscale formats, as well as legacy
242 To select a format, applications set the fb_var_screeninfo bits_per_pixel field
246 - For grayscale formats, applications set the grayscale field to one. The red,
[all …]
|
| /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-4.19/Documentation/rapidio/ |
| D | mport_cdev.txt | 17 devices directly to applications, in a manner that allows the numerous and
21 for user-space applications. Most of RapidIO operations are supported through
28 Using available set of ioctl commands user-space applications can perform
41 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
43 - Enable/Disable reporting of RIO port-write events to user-space applications
62 as user-space applications while using remaining functionality provided by
98 V. User-space Applications and API
100 API library and applications that use this device driver are available from
|
| D | rio_cm.txt | 19 to applications, in a manner that allows the numerous and varied RapidIO
22 This driver (RIO_CM) provides to user-space applications shared access to
29 have reduced number of messaging mailboxes. RapidIO aware applications must
34 operations using a single messaging mailbox. This allows applications to
42 Following ioctl commands are available to user-space applications:
79 user-space applications are defined in 'include/uapi/linux/rio_cm_cdev.h'.
112 V. User-space Applications and API Library
114 Messaging API library and applications that use this device driver are available
|
| /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
|
12345678910>>...79