Searched full:application (Results 1 – 25 of 616) sorted by relevance
12345678910>>...25
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 34 This call is used by the application to access the enumeration
74 application.
78 Filled in by the application.
115 - The driver allows the application to try to change the default colorspace
116 encoding. The application can ask to configure the colorspace of the
122 - The driver allows the application to try to change the default transform function.
123 The application can ask to configure the transform function of
129 - The driver allows the application to try to change the default Y'CbCr
130 encoding. The application can ask to configure the Y'CbCr encoding of the
136 - The driver allows the application to try to change the default HSV
[all …]
|
| D | pixfmt-v4l2.rst | 47 - The pixel format or type of compression, set by the application.
69 the value requested by the application, returning ``width`` times
111 by the driver for capture streams and by the application for
112 output streams, see :ref:`colorspaces`. If the application sets the
113 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
148 - Flags set by the application or driver, see :ref:`format-flags`.
155 the driver for capture streams and by the application for output
156 streams, see :ref:`colorspaces`. If the application sets the
157 flag ``V4L2_PIX_FMT_FLAG_SET_CSC`` then the application can set
169 the driver for capture streams and by the application for output
[all …]
|
| D | vidioc-enum-fmt.rst | 87 - Number of the format in the enumeration, set by the application.
91 - Type of the data stream, set by the application. Only these types
131 application. Only applicable to drivers that advertise the
197 - The driver allows the application to try to change the default
199 The application can ask to configure the colorspace of the capture device
204 - The driver allows the application to try to change the default
206 The application can ask to configure the transfer function of the capture
211 - The driver allows the application to try to change the default
213 The application can ask to configure the Y'CbCr encoding of the capture device
218 - The driver allows the application to try to change the default
[all …]
|
| D | userp.rst | 19 methods. Buffers (planes) are allocated by the application itself, and
55 area of memory. This happens transparently to the application in the
69 the application's free list and subsequently reused for other purposes,
74 application waits until a filled buffer can be dequeued, and re-enqueues
77 started. In the write loop, when the application runs out of free
79 Two methods exist to suspend execution of the application until one or
97 application needs to synchronize with another event it should examine
117 because an application may share them with other processes.
|
| D | app-pri.rst | 6 Application Priority
11 of thought, a video recording application could for example block other
30 after another application obtained higher priority.
|
| D | vidioc-enum-frameintervals.rst | 47 (zero-based) is valid. The application should increase the index by
66 When the application calls the function with index zero, it must check
79 without any interaction from the application itself. This means that the
80 enumeration data is consistent if the application does not perform any
97 the application, *OUT* denotes values that the driver fills in. The
98 application should zero out all members except for the *IN* fields.
|
| D | vidioc-enum-framesizes.rst | 48 (zero-based) is valid. The application should increase the index by
67 When the application calls the function with index zero, it must check
79 without any interaction from the application itself. This means that the
80 enumeration data is consistent if the application does not perform any
87 the application, *OUT* denotes values that the driver fills in. The
88 application should zero out all members except for the *IN* fields.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fc | 5 This interface allows an admin to set an FC application
8 an application or logical entity such as a virtual
9 machine or container group. The application or logical
13 entities can utilize the application id and FC traffic
25 If an admin wants to remove an FC application identifier
|
| D | sysfs-platform-chipidea-usb-otg | 7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
15 Reading: returns 1 if the application running on the A-device
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
40 bus as host, and is 0 when the application no longer wants to
45 Reading: returns if the application running on the B device
|
| D | sysfs-driver-w1_therm | 13 Users: any user space application which wants to communicate with
29 Users: any user space application which wants to communicate with
43 Users: any user space application which wants to communicate with
65 Users: any user space application which wants to communicate with
86 Users: any user space application which wants to communicate with
107 Users: any user space application which wants to communicate with
135 Users: any user space application which wants to communicate with
163 Users: An application using the w1_term device
190 Users: An application using the w1_term device
|
| /Documentation/networking/device_drivers/wwan/ |
| D | iosm.rst | 13 MBIM protocol [1]. Any front end application ( eg: Modem Manager) could easily
21 application to detect port enumeration and enable MBIM functionality.
23 Examples of few such userspace application are:
34 Management application development
46 /dev/wwan0mbim0 character device. Application shall use this interface for
51 The userspace application is responsible for all control message fragmentation
56 The MBIM control messages from the management application must not exceed the
61 The management application must accept control messages of up the negotiated
74 The userspace management application is responsible for creating new IP link
|
| D | t7xx.rst | 13 application (e.g. Modem Manager) could easily manage the MBIM interface to enable
22 application to detect port enumeration and enable MBIM & AT functionalities.
70 Management application development
82 /dev/wwan0mbim0 character device. Application shall use this interface for
87 The userspace application is responsible for all control message fragmentation
92 The MBIM control messages from the management application must not exceed the
97 The management application must accept control messages of up the negotiated
109 The userspace management application is responsible for creating new IP link
126 device. Application shall use this interface to issue AT commands.
135 /dev/wwan0fastboot0 character device. Application shall use this interface for
|
| /Documentation/arch/arm/ |
| D | marvell.rst | 308 Dove family (application processor)
315 …https://web.archive.org/web/20111102020643/http://www.marvell.com/application-processors/armada-50…
318 …https://web.archive.org/web/20160428160231/http://www.marvell.com/application-processors/armada-50…
321 …https://web.archive.org/web/20120130172443/http://www.marvell.com/application-processors/armada-50…
324 …https://web.archive.org/web/20160822232651/http://www.marvell.com/application-processors/armada-50…
338 - Application processor only
341 … : https://web.archive.org/web/20150927135510/http://www.marvell.com/application-processors/pxa-…
342 … : https://web.archive.org/web/20120111181937/http://www.marvell.com/application-processors/pxa-…
343 … : https://web.archive.org/web/20150927164805/http://www.marvell.com/application-processors/pxa-…
344 … : https://web.archive.org/web/20140211221535/http://www.marvell.com/application-processors/pxa-…
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_prio.rst | 9 Nominally, an application would set the priority of its traffic via the
12 1) The application may not have been coded to set this value
13 2) The priority of application traffic is often a site-specific administrative
14 decision rather than an application defined one.
52 One usage for the net_prio cgroup is with mqprio qdisc allowing application
|
| /Documentation/networking/devlink/ |
| D | sfc.rst | 40 - SmartNIC application co-processor (APU) first stage boot loader version.
43 - SmartNIC application co-processor (APU) co-operating system loader version.
46 - SmartNIC application co-processor (APU) main operating system version.
49 - SmartNIC application co-processor (APU) recovery operating system version.
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 35 Management Application
38 In the management partition, a management application exists which enables
41 State Transfer Application (REST API's).
43 The management application runs on a Linux logical partition on a
47 application using a combination of HMC to hypervisor interfaces and
51 application component are passed to the hypervisor over a VMC interface,
68 for communicating between the management application and the hypervisor. It
107 This section provides an example for the management application
122 which will be used for management application session initialization.
146 connection can be established. The application layer performs an open() to
[all …]
|
| /Documentation/networking/ |
| D | kcm.rst | 8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
73 Messages are sent over a TCP stream with some application protocol message
75 of a received message can be deduced from the application protocol header
93 using the socket. When the application gets the error notification for a
195 if an application thread knows that it will be doing a lot of
223 KCM accelerates application layer protocols. Specifically, it allows
228 application layer messages a unit of work in the kernel for the purposes of
238 parallelized). In an application, a KCM socket can be opened for each
255 On transmit, there are three ways an application can batch (pipeline)
[all …]
|
| D | tcp-thin.rst | 9 that the application sends data with such a low rate that the
15 dependency on the arrival of new data from the application to trigger
25 In order to reduce application-layer latency when packets are lost,
40 they must be specifically activated by the application using the
|
| D | cdc_mbim.rst | 46 userspace MBIM management application always is required to enable a
55 management application:
62 Management application development
79 application. It is therefore up to this application to ensure that it
96 limits the maximum control message size. The management application is
101 The userspace application can access the CDC MBIM functional
110 The userspace application is responsible for all control message
116 The MBIM control messages from the management application *must not*
122 The management application *must* accept control messages of up the
183 The userspace management application is responsible for adding new
[all …]
|
| /Documentation/iio/ |
| D | iio_tools.rst | 13 * lsiio: example application that provides a list of IIO devices and triggers
14 * iio_event_monitor: example application that reads events from an IIO device
16 * iio_generic_buffer: example application that reads data from buffer
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,pru-consumer.yaml | 13 A PRU application/consumer/user node typically uses one or more PRU device
14 nodes to implement a PRU application/functionality. Each application/client
20 The application nodes shall define their own bindings like regular platform
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 35 application's behavior, but never try to search for sysfs. Never try
60 is a bug in the application
82 bug in the application
89 like the "device"-link, is a bug in the application
130 the application.
137 a bug in the application.
147 a device in ``/sys/devices/`` is a bug in the application.
148 Accessing ``/sys/class/net/eth0/device`` is a bug in the application.
158 the application.
170 access the chain of parents is a bug in the application.
|
| D | syscall-user-dispatch.rst | 19 address back to userspace. The application is in control of a flip
21 multiple-personality application can then flip the switch without
31 personality, and the application simply modifies that variable to
85 application, while not impacting the Linux native regions of the
88 malicious application to subvert the mechanism by jumping to an allowed
|
| /Documentation/devicetree/bindings/ata/ |
| D | snps,dwc-ahci-common.yaml | 30 Basic DWC AHCI SATA clock sources like application AXI/AHB BIU clock,
41 - description: Application APB/AHB/AXI BIU clock
60 At least basic application and reference clock domains resets are
70 - description: Application AHB/AXI BIU clock domain reset control
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr.yaml | 14 communication between Application processor and QDSP. APR/GPR is mainly
36 5 = Application processor Domain
38 7 = Application Processor2 Domain
51 5 = Application processor Domain
53 7 = Application Processor2 Domain
57 3 = Application Processor Domain
|
12345678910>>...25