Searched refs:applications (Results 1 – 25 of 502) sorted by relevance
12345678910>>...21
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| 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 | 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 | 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
|
| 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-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`.
119 period. To reset manually applications can just set this field to
127 applications and drivers must set this field to zero. Applications
140 - Reserved for future extensions. Drivers and applications must set
159 - Set by drivers and applications, see :ref:`parm-flags`.
176 period. To reset manually applications can just set this field to
184 applications and drivers must set this field to zero. Applications
197 - Reserved for future extensions. Drivers and applications must set
[all …]
|
| D | io.rst | 9 a device. All drivers exchanging data with applications must support at
18 with memory mapped or user buffers applications call the
28 each file descriptor. The only exceptions are applications not
29 exchanging data with a driver ("panel applications", see :ref:`open`)
|
| D | rw.rst | 31 To read from the device applications use the :ref:`read() <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 | vidioc-g-jpegcomp.rst | 38 These ioctls are **deprecated**. New drivers and applications should use
54 encoded. If you omit them, applications assume you've used standard
71 control is exposed by a driver applications should use it instead
92 control is exposed by a driver applications should use it instead
|
| D | streaming-par.rst | 10 as well as I/O. Presently applications can request a high quality
15 applications can request frame skipping or duplicating on the driver
25 To get and set the streaming parameters applications call the
|
| 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
|
| D | vidioc-g-audioout.rst | 38 To query the current audio output applications zero out the ``reserved``
46 current audio output applications can initialize the ``index`` field and
83 - Audio mode, none defined yet. Drivers and applications (on
87 - Reserved for future extensions. Drivers and applications must set
|
| D | vidioc-g-output.rst | 38 To query the current video output applications call the
45 To select a video output applications store the number of the desired
50 effects applications must select an output before querying or
|
| 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
|
| D | vidioc-g-fbuf.rst | 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
173 hardware. That implies applications can just set this field to
[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
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.
|
| D | vidioc-g-audio.rst | 38 To query the current audio input applications zero out the ``reserved``
45 current audio input *and* change the audio mode, applications initialize
75 - Audio mode flags set by drivers and applications (on
79 - Reserved for future extensions. Drivers and applications must set
|
| /Linux-v4.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
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
|
| /Linux-v4.19/Documentation/media/uapi/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
|
| /Linux-v4.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
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'.
114 Messaging API library and applications that use this device driver are available
|
| /Linux-v4.19/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
|
| /Linux-v4.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
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,
247 blue, green and transp fields must be set to 0 by applications and ignored by
[all …]
|
| /Linux-v4.19/arch/arm/mach-sti/ |
| D | Kconfig | 34 and other digital audio/video applications using Flattned Device
43 and other digital audio/video applications using Flattened Device
53 and other digital audio/video applications using Flattened Device
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,nsp.txt | 5 and management applications as well as residential router/gateway
6 applications. The SoC features dual core Cortex A9 ARM CPUs, integrating
|
| /Linux-v4.19/Documentation/ |
| D | SAK.txt | 11 masquerading as login applications. Users need to be taught to enter
46 2. On the PC keyboard, SAK kills all applications which have
50 actually want killed. This is because these applications are
90 applications to malfunction - test everything well.
|
12345678910>>...21
