Searched refs:applications (Results 1 – 25 of 610) sorted by relevance
12345678910>>...25
| /Linux-v6.6/Documentation/userspace-api/media/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
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 | 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 | 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
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
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 :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 | vidioc-g-parm.rst | 53 To get and set the streaming parameters applications call the
104 - Set by drivers and applications, see :ref:`parm-flags`.
124 period. To reset manually applications can just set this field to
132 applications and drivers must set this field to zero. Applications
145 - Reserved for future extensions. Drivers and applications must set
163 - Set by drivers and applications, see :ref:`parm-flags`.
184 period. To reset manually applications can just set this field to
192 applications and drivers must set this field to zero. Applications
205 - Reserved for future extensions. Drivers and applications must set
236 imaging applications. The idea is to get the best possible image
|
| 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
70 control is exposed by a driver applications should use it instead
91 control is exposed by a driver applications should use it instead
|
| 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 | 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
82 - Audio mode, none defined yet. Drivers and applications (on
86 - Reserved for future extensions. Drivers and applications must set
|
| 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-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-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
74 - Audio mode flags set by drivers and applications (on
78 - Reserved for future extensions. Drivers and applications must set
|
| D | vidioc-dv-timings-cap.rst | 38 To query the capabilities of the DV receiver/transmitter applications
52 receivers) or outputs (for DV transmitters), applications must specify
115 video node applications must set this field to zero.
120 Drivers and applications must set the array to zero.
|
| /Linux-v6.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
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
|
| /Linux-v6.6/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
|
| D | media-ioc-enum-links.rst | 34 To enumerate pads and/or links for a given entity, applications set the
80 - Reserved for future extensions. Drivers and applications must set
106 - Reserved for future extensions. Drivers and applications must set
133 - Reserved for future extensions. Drivers and applications must set
|
| /Linux-v6.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
|
| /Linux-v6.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
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-v6.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
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-v6.6/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-v6.6/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.
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | xstate.rst | 1 Using XSTATE features in user space applications
25 size of 2KB with existing applications is too small for new CPU features
27 enabling, the kernel can enforce userspace applications to have
30 Using dynamically enabled XSTATE features in user space applications
33 The kernel provides an arch_prctl(2) based mechanism for applications to
86 Below is the example of how userspace applications enable
|
12345678910>>...25
