| /kernel/linux/linux-5.10/net/bluetooth/cmtp/ |
| D | capi.c | 187 struct cmtp_application *application; in cmtp_recv_interopmsg() local
205 application = cmtp_application_get(session, CMTP_MSGNUM, msgnum); in cmtp_recv_interopmsg()
206 if (application) { in cmtp_recv_interopmsg()
207 application->state = BT_CONNECTED; in cmtp_recv_interopmsg()
208 application->msgnum = 0; in cmtp_recv_interopmsg()
209 application->mapping = CAPIMSG_APPID(skb->data); in cmtp_recv_interopmsg()
218 application = cmtp_application_get(session, CMTP_MAPPING, appl); in cmtp_recv_interopmsg()
219 if (application) { in cmtp_recv_interopmsg()
220 application->state = BT_CLOSED; in cmtp_recv_interopmsg()
221 application->msgnum = 0; in cmtp_recv_interopmsg()
[all …]
|
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | wacom_wac.h | 171 ((f)->application == HID_DG_PEN) || \
172 ((f)->application == HID_DG_DIGITIZER) || \
173 ((f)->application == WACOM_HID_WD_PEN) || \
174 ((f)->application == WACOM_HID_WD_DIGITIZER) || \
175 ((f)->application == WACOM_HID_G9_PEN) || \
176 ((f)->application == WACOM_HID_G11_PEN))
179 ((f)->application == HID_DG_TOUCHSCREEN) || \
180 ((f)->application == WACOM_HID_G9_TOUCHSCREEN) || \
181 ((f)->application == WACOM_HID_G11_TOUCHSCREEN) || \
182 ((f)->application == WACOM_HID_WT_TOUCHPAD) || \
[all …]
|
| D | hid-multitouch.c | 107 unsigned int application; member
154 struct mt_application *application; member
229 static int cypress_compute_slot(struct mt_application *application, in cypress_compute_slot() argument
232 if (*slot->contactid != 0 || application->num_received == 0) in cypress_compute_slot()
389 struct mt_application *application; in mt_set_quirks() local
398 list_for_each_entry(application, &td->applications, list) { in mt_set_quirks()
399 application->quirks = val; in mt_set_quirks()
400 if (!application->have_contact_count) in mt_set_quirks()
401 application->quirks &= ~MT_QUIRK_CONTACT_CNT_ACCURATE; in mt_set_quirks()
498 struct mt_application *application) in mt_allocate_usage() argument
[all …]
|
| D | hid-plantronics.c | 37 #define PLT_ALLOW_CONSUMER (field->application == HID_CP_CONSUMERCONTROL && \
61 if (field->application == HID_GD_JOYSTICK) in plantronics_input_mapping()
86 else if (!((field->application ^ plt_type) & HID_USAGE_PAGE)) { in plantronics_input_mapping()
110 usage->hid, field->application); in plantronics_input_mapping()
116 usage->hid, field->application, mapped_key); in plantronics_input_mapping()
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 63 - Number of the format in the enumeration, set by the application.
93 - The driver allows the application to try to change the default colorspace
94 encoding. The application can ask to configure the colorspace of the
100 - The driver allows the application to try to change the default transform function.
101 The application can ask to configure the transform function of
107 - The driver allows the application to try to change the default Y'CbCr
108 encoding. The application can ask to configure the Y'CbCr encoding of the
114 - The driver allows the application to try to change the default HSV
115 encoding. The application can ask to configure the HSV encoding of the
121 - The driver allows the application to try to change the default
[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 | 85 - Number of the format in the enumeration, set by the application.
89 - Type of the data stream, set by the application. Only these types
129 application. Only applicable to drivers that advertise the
193 - The driver allows the application to try to change the default
195 The application can ask to configure the colorspace of the capture device
200 - The driver allows the application to try to change the default
202 The application can ask to configure the transfer function of the capture
207 - The driver allows the application to try to change the default
209 The application can ask to configure the Y'CbCr encoding of the capture device
214 - 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 | 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.
|
| D | vidioc-g-fmt.rst | 43 format) exchanged between driver and application.
49 ``V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE``. When the application calls the
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
68 parameters acceptable for both the application and driver. On success
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | marvel.rst | 262 Dove family (application processor)
269 http://www.marvell.com/application-processors/armada-500/assets/Marvell_Armada510_SoC.pdf
272 http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Hardware-Spec.pdf
275 http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Functional-Spec.pdf
278 http://www.marvell.com/application-processors/armada-500/
295 …- Product Brief : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
296 …- Design guide : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
297 …- Developers manual : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
298 …- Specification : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
299 …- Specification update : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_…
[all …]
|
| /kernel/linux/linux-5.10/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 | 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 managament 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 …]
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| D | ibmvmc.rst | 38 In the management partition, a management application exists which enables
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
177 During normal runtime, the management application and the hypervisor
179 sending data to the hypervisor, the management application performs a
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | protection-keys.rst | 18 when an application changes protection domains. It works by
44 pkey_alloc(). An application calls the WRPKRU instruction
54 ... application runs here
56 Now, if the application needs to update the data at 'ptr', it can
93 or when the kernel does the access on the application's behalf like
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-driver-w1_ds28e04 | 6 Users: any user space application which wants to communicate with DS28E04-100
15 Users: any user space application which wants to communicate with DS28E04-100
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/bridge/analogix/ |
| D | Kconfig | 12 application processor to eDP or DisplayPort.
22 the HDMI output of an application processor to MyDP
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/drivers/ |
| D | meye-uapi.rst | 38 application). The argument to MEYEIOC_QBUF_CAPT is the
45 for the application to use. It returns the buffer size.
53 Look at the 'motioneye' application code for an actual example.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/mei/ |
| D | iamt.rst | 27 HTTP/S that are received from a remote management console application.
42 local application using the same network interface as a remote application
45 When a local application sends a message addressed to the local Intel AMT host
59 single application.
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | swsusp-and-swap-files.rst | 33 2) Use an application that will bmap the swap file with the help of the
44 application in 2) (of course, this step may be carried out automatically
45 by the same application that determines the swap file's header offset using the
50 Use a userland suspend application that will set the partition and offset
|