| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 | 106 unsigned int application; member
153 struct mt_application *application; member
227 static int cypress_compute_slot(struct mt_application *application, in cypress_compute_slot() argument
230 if (*slot->contactid != 0 || application->num_received == 0) in cypress_compute_slot()
385 struct mt_application *application; in mt_set_quirks() local
394 list_for_each_entry(application, &td->applications, list) { in mt_set_quirks()
395 application->quirks = val; in mt_set_quirks()
396 if (!application->have_contact_count) in mt_set_quirks()
397 application->quirks &= ~MT_QUIRK_CONTACT_CNT_ACCURATE; in mt_set_quirks()
494 struct mt_application *application) in mt_allocate_usage() argument
[all …]
|
| D | hid-plantronics.c | 36 #define PLT_ALLOW_CONSUMER (field->application == HID_CP_CONSUMERCONTROL && \
49 if (field->application == HID_GD_JOYSTICK) in plantronics_input_mapping()
74 else if (!((field->application ^ plt_type) & HID_USAGE_PAGE)) { in plantronics_input_mapping()
98 usage->hid, field->application); in plantronics_input_mapping()
104 usage->hid, field->application, mapped_key); in plantronics_input_mapping()
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/networking/ |
| D | kcm.txt | 5 interface over TCP for generic application protocols. With KCM an application
6 can efficiently send and receive application protocol messages over TCP using
70 Messages are sent over a TCP stream with some application protocol message
72 of a received message can be deduced from the application protocol header
90 using the socket. When the application gets the error notification for a
191 if an application thread knows that it will be doing a lot of
219 KCM accelerates application layer protocols. Specifically, it allows
224 application layer messages a unit of work in the kernel for the purposes of
234 parallelized). In an application, a KCM socket can be opened for each
251 On transmit, there are three ways an application can batch (pipeline)
[all …]
|
| D | cdc_mbim.txt | 43 userspace MBIM management application always is required to enable a
51 management application:
57 Management application development
74 application. It is therefore up to this application to ensure that it
91 limits the maximum control message size. The managament application is
96 The userspace application can access the CDC MBIM functional
105 The userspace application is responsible for all control message
111 The MBIM control messages from the management application *must not*
117 The management application *must* accept control messages of up the
176 The userspace management application is responsible for adding new
[all …]
|
| D | af_xdp.rst | 21 application.
43 fill ring is used by the application to send down addr for the kernel
72 user-space application can place an XSK at an arbitrary place in this
118 user-space application.
125 application need explicit synchronization of multiple
156 The user application produces UMEM addrs to this ring. Note that, if
157 running the application with aligned chunk mode, the kernel will mask
160 to the same chunk. If the user application is run in the unaligned
174 The user application consumes UMEM addrs from this ring.
187 The user application consumes struct xdp_desc descriptors from this
[all …]
|
| D | tcp-thin.txt | 5 that the application sends data with such a low rate that the
11 dependency on the arrival of new data from the application to trigger
21 In order to reduce application-layer latency when packets are lost,
36 they must be specifically activated by the application using the
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | userp.rst | 25 methods. Buffers (planes) are allocated by the application itself, and
61 area of memory. This happens transparently to the application in the
75 the application's free list and subsequently reused for other purposes,
80 application waits until a filled buffer can be dequeued, and re-enqueues
83 started. In the write loop, when the application runs out of free
85 Two methods exist to suspend execution of the application until one or
103 application needs to synchronize with another event it should examine
123 because an application may share them with other processes.
|
| D | open.rst | 23 helper functions and a common application interface specified in this
64 drivers. The user must enter a device name, or the application can try
110 by the driver, users can for example start a "panel" application to
112 application captures video and audio. In other words, panel applications
113 are comparable to an ALSA audio mixer application. Just opening a V4L2
116 Once an application has allocated the memory buffers needed for
120 :ref:`write() <func-write>` functions) that application (filehandle)
139 or similar means. This is better handled by a proxy application in user
|
| D | vidioc-enum-frameintervals.rst | 55 (zero-based) is valid. The application should increase the index by
74 When the application calls the function with index zero, it must check
87 without any interaction from the application itself. This means that the
88 enumeration data is consistent if the application does not perform any
106 the application, *OUT* denotes values that the driver fills in. The
107 application should zero out all members except for the *IN* fields.
|
| D | vidioc-enum-framesizes.rst | 56 (zero-based) is valid. The application should increase the index by
75 When the application calls the function with index zero, it must check
87 without any interaction from the application itself. This means that the
88 enumeration data is consistent if the application does not perform any
96 the application, *OUT* denotes values that the driver fills in. The
97 application should zero out all members except for the *IN* fields.
|
| D | pixfmt-v4l2.rst | 49 - The pixel format or type of compression, set by the application.
71 the value requested by the application, returning ``width`` times
113 by the driver for capture streams and by the application for
143 - Flags set by the application or driver, see :ref:`format-flags`.
151 the driver for capture streams and by the application for output
157 the driver for capture streams and by the application for output
166 the driver for capture streams and by the application for output
172 the driver for capture streams and by the application for output
|
| D | pixfmt-v4l2-mplane.rst | 102 - Flags set by the application or driver, see :ref:`format-flags`.
108 the driver for capture streams and by the application for output
114 the driver for capture streams and by the application for output
121 the driver for capture streams and by the application for output
127 the driver for capture streams and by the application for output
|
| /Linux-v5.4/Documentation/core-api/ |
| D | protection-keys.rst | 17 when an application changes protection domains. It works by
43 pkey_alloc(). An application calls the WRPKRU instruction
53 ... application runs here
55 Now, if the application needs to update the data at 'ptr', it can
92 or when the kernel does the access on the application's behalf like
|
| /Linux-v5.4/Documentation/crypto/ |
| D | async-tx-api.txt | 18 4.2 "My application needs exclusive control of hardware channels"
79 operations complete. When an application needs to submit a chain of
82 acknowledged by the application before the offload engine driver is allowed to
95 automatically issues pending operations. An application can force this
97 channels since the application has no knowledge of channel to operation
101 There are two methods for an application to learn about the completion
108 called in application context if the operation is carried out
110 async_<operation>, or when the application needs to submit a chain of
177 4.2 "My application needs exclusive control of hardware channels"
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | dnotify.txt | 8 The basic mechanism involves the application registering for notification
12 The application decides which "events" it wants to be notified about.
23 Usually, the application must reregister after each notification, but
33 Preferably the application will choose one of the real time signals
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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.
|
