Searched full:applications (Results 1 – 25 of 465) sorted by relevance
12345678910>>...19
| /Documentation/userspace-api/media/v4l/ |
| 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-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 | 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-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 | 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 | io.rst | 10 a device. All drivers exchanging data with applications must support at
19 with memory mapped or user buffers applications call the
29 each file descriptor. The only exceptions are applications not
30 exchanging data with a driver ("panel applications", see :ref:`open`)
|
| D | dv-timings.rst | 26 device applications use the
29 DV timings for the device applications use the
33 the DV timings as seen by the video receiver applications use the
36 Applications can make use of the :ref:`input-capabilities` and
|
| D | rw.rst | 31 To read from the device applications use the :c:func:`read()`
33 must implement one I/O method if they exchange data with applications,
39 It would be desirable if applications could depend on drivers
42 require this interface, which is most useful for simple applications
|
| D | streaming-par.rst | 11 as well as I/O. Presently applications can request a high quality
16 applications can request frame skipping or duplicating on the driver
26 To get and set the streaming parameters applications call the
|
| 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-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
123 Applications call the ``VIDIOC_DQBUF`` ioctl to dequeue a filled
|
| D | vidioc-subdev-g-fmt.rst | 41 To retrieve the current format applications set the ``pad`` field of a
48 To change the current format applications set both the ``pad`` and
56 Applications can query the device capabilities by setting the ``which``
59 and stored in the sub-device file handle. Two applications querying the
63 applications would first set the try format at the sub-device input with
106 - Reserved for future extensions. Applications and drivers must set
|
| D | vidioc-subdev-g-crop.rst | 44 To retrieve the current crop rectangle applications set the ``pad``
53 To change the current crop rectangle applications set both the ``pad``
62 Applications can query the device capabilities by setting the ``which``
66 applications querying the same sub-device would thus not interact with
100 - Reserved for future extensions. Applications and drivers 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 …]
|
| D | vidioc-g-input.rst | 38 To query the current video input applications call the
44 To select a video input applications store the number of the desired
49 applications must select an input before querying or negotiating any
|
| /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
|
| /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
|
| /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 …]
|
| /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
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | mlx90632.txt | 5 There are various applications for the Infra Red contactless temperature sensor
6 and MLX90632 is most suitable for consumer applications where measured object
9 industrial applications. Since it can operate and measure ambient temperature
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 40 space. User buffers are allocated by applications themselves, and this
43 allocated by applications through a device driver, and this ioctl only
47 To allocate device buffers applications initialize all fields of the
62 Applications can call :ref:`DMX_REQBUFS` again to change the number of
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 31 Applications manage PCM substream to maintain data transmission for PCM frames.
32 Before starting the data transmission, applications need to configure PCM
34 interaction between applications and ALSA PCM core. Once decided, runtime of
38 structure includes several types of parameters. Applications set preferable
75 SNDRV_PCM_IOCTL_HW_REFINE only. Applications can select which
85 with SNDRV_PCM_INFO_XXX. Typically, applications execute ioctl(2) with
114 applications execute ioctl(2) with SNDRV_PCM_HW_REFINE or SNDRV_PCM_HW_PARAMS.
|
| /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 …]
|
12345678910>>...19