Searched refs:applications (Results 1 – 25 of 527) sorted by relevance
12345678910>>...22
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-priority.rst | 45 To query the current access priority applications call the
49 To request an access priority applications store the desired priority in
68 - Lowest priority, usually applications running in background, for
70 in user space will be necessary if multiple applications want to
77 - Medium priority, usually applications started and interactively
79 or just "panel" applications to change the channel or video
86 applications which must not be interrupted, like video recording.
|
| D | format.rst | 20 Different devices exchange different kinds of data with applications,
25 applications should always negotiate a data format before engaging in
28 to satisfy the request. Of course applications can also just query the
42 initialization sequence. Prior to this point multiple panel applications
60 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
73 All drivers exchanging data with applications must support the
86 by all drivers exchanging image data with applications.
93 routine or library for integration into applications.
98 seems useless, but there are applications serving as proxy between
99 drivers and the actual video applications for which this is useful.
|
| D | app-pri.rst | 16 When multiple applications share a device it may be desirable to assign
19 applications from changing video controls or switching the current TV
20 channel. Another objective is to permit low priority applications
22 applications and automatically regain control of the device at a later
|
| D | vidioc-enum-dv-timings.rst | 47 applications can enumerate a list of known supported timings. Call
52 To query the available timings, applications initialize the ``index``
58 DV timings, applications shall begin at index zero, incrementing by one
69 or outputs (for DV transmitters), applications must specify the desired
92 video node applications must set this field to zero.
95 - Reserved for future extensions. Drivers and applications must set
|
| D | vidioc-g-parm.rst | 47 applications can request frame skipping or duplicating on the driver
59 To get and set the streaming parameters applications call the
116 - Set by drivers and applications, see :ref:`parm-flags`.
129 period. To reset manually applications can just set this field to
137 applications and drivers must set this field to zero. Applications
150 - Reserved for future extensions. Drivers and applications must set
169 - Set by drivers and applications, see :ref:`parm-flags`.
186 period. To reset manually applications can just set this field to
194 applications and drivers must set this field to zero. Applications
207 - Reserved for future extensions. Drivers and applications must set
[all …]
|
| D | io.rst | 16 a device. All drivers exchanging data with applications must support at
25 with memory mapped or user buffers applications call the
35 each file descriptor. The only exceptions are applications not
36 exchanging data with a driver ("panel applications", see :ref:`open`)
|
| D | rw.rst | 38 To read from the device applications use the :ref:`read() <func-read>`
40 must implement one I/O method if they exchange data with applications,
46 It would be desirable if applications could depend on drivers
49 require this interface, which is most useful for simple applications
|
| D | vidioc-g-jpegcomp.rst | 45 These ioctls are **deprecated**. New drivers and applications should use
61 encoded. If you omit them, applications assume you've used standard
78 control is exposed by a driver applications should use it instead
99 control is exposed by a driver applications should use it instead
|
| D | streaming-par.rst | 17 as well as I/O. Presently applications can request a high quality
22 applications can request frame skipping or duplicating on the driver
32 To get and set the streaming parameters applications call the
|
| D | vidioc-g-audioout.rst | 45 To query the current audio output applications zero out the ``reserved``
53 current audio output applications can initialize the ``index`` field and
90 - Audio mode, none defined yet. Drivers and applications (on
94 - Reserved for future extensions. Drivers and applications must set
|
| D | vidioc-g-input.rst | 45 To query the current video input applications call the
51 To select a video input applications store the number of the desired
56 applications must select an input before querying or negotiating any
|
| D | vidioc-g-output.rst | 45 To query the current video output applications call the
52 To select a video output applications store the number of the desired
57 effects applications must select an output before querying or
|
| D | vidioc-g-fbuf.rst | 59 To get the current parameters applications call the :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
64 To set the parameters for a *Video Output Overlay*, applications must
74 applications must initialize the ``flags`` field, the ``fmt``
79 For a *destructive Video Overlay* applications must additionally provide
116 *destructive Video Overlays* applications must provide a base
119 the driver must return a valid base address, so applications can
147 - For *destructive Video Overlays* applications must initialize this
163 - Drivers and applications shall ignore this field. If applicable,
176 For *destructive Video Overlays* both applications and drivers can
180 hardware. That implies applications can just set this field to
[all …]
|
| D | open.rst | 63 means applications cannot *reliably* scan for loaded or installed
80 'feature' was never used by applications and many drivers did not
112 application captures video and audio. In other words, panel applications
123 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl) and other applications are
137 V4L2 drivers should not support multiple applications reading or writing
146 To open and close V4L2 devices applications use the
165 not required, so applications cannot know if it really works.
|
| D | dv-timings.rst | 33 device applications use the
36 DV timings for the device applications use the
40 the DV timings as seen by the video receiver applications use the
|
| /Linux-v5.4/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-v5.4/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
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'.
129 Messaging API library and applications that use this device driver are available
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | media-controller-intro.rst | 22 presented to userspace applications as V4L2 and ALSA capture devices.
25 available directly to applications by the drivers, can usually be
35 applications to access hardware parameters. As newer hardware expose an
37 applications really require based on limited information, thereby
|
| D | media-ioc-enum-links.rst | 42 To enumerate pads and/or links for a given entity, applications set the
89 - Reserved for future extensions. Drivers and applications must set
116 - Reserved for future extensions. Drivers and applications must set
144 - Reserved for future extensions. Drivers and applications must set
|
| /Linux-v5.4/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-v5.4/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
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,
248 blue, green and transp fields must be set to 0 by applications and ignored by
[all …]
|
| /Linux-v5.4/arch/arm/mach-sti/ |
| D | Kconfig | 35 and other digital audio/video applications using Flattned Device
44 and other digital audio/video applications using Flattened Device
54 and other digital audio/video applications using Flattened Device
|
| /Linux-v5.4/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-v5.4/Documentation/security/ |
| D | sak.rst | 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>>...22
