| /Linux-v4.19/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-v4.19/drivers/hid/ |
| D | wacom_wac.h | 173 ((f)->application == HID_DG_PEN) || \
174 ((f)->application == HID_DG_DIGITIZER) || \
175 ((f)->application == WACOM_HID_WD_PEN) || \
176 ((f)->application == WACOM_HID_WD_DIGITIZER) || \
177 ((f)->application == WACOM_HID_G9_PEN) || \
178 ((f)->application == WACOM_HID_G11_PEN))
181 ((f)->application == HID_DG_TOUCHSCREEN) || \
182 ((f)->application == WACOM_HID_G9_TOUCHSCREEN) || \
183 ((f)->application == WACOM_HID_G11_TOUCHSCREEN) || \
184 ((f)->application == WACOM_HID_WT_TOUCHPAD) || \
[all …]
|
| D | hid-multitouch.c | 109 unsigned int application; member
155 struct mt_application *application; member
228 static int cypress_compute_slot(struct mt_application *application, in cypress_compute_slot() argument
231 if (*slot->contactid != 0 || application->num_received == 0) in cypress_compute_slot()
379 struct mt_application *application; in mt_set_quirks() local
388 list_for_each_entry(application, &td->applications, list) { in mt_set_quirks()
389 application->quirks = val; in mt_set_quirks()
390 if (!application->have_contact_count) in mt_set_quirks()
391 application->quirks &= ~MT_QUIRK_CONTACT_CNT_ACCURATE; in mt_set_quirks()
488 struct mt_application *application) in mt_allocate_usage() argument
[all …]
|
| D | hid-plantronics.c | 39 #define PLT_ALLOW_CONSUMER (field->application == HID_CP_CONSUMERCONTROL && \
52 if (field->application == HID_GD_JOYSTICK) in plantronics_input_mapping()
77 else if (!((field->application ^ plt_type) & HID_USAGE_PAGE)) { in plantronics_input_mapping()
101 usage->hid, field->application); in plantronics_input_mapping()
107 usage->hid, field->application, mapped_key); in plantronics_input_mapping()
|
| /Linux-v4.19/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-v4.19/Documentation/arm/Marvell/ |
| D | README | 184 Dove family (application processor)
189 …Product Brief : http://www.marvell.com/application-processors/armada-500/assets/Marvell_Armada51…
190 …Hardware Spec : http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Hardw…
191 …Functional Spec : http://www.marvell.com/application-processors/armada-500/assets/Armada-510-Funct…
192 Homepage: http://www.marvell.com/application-processors/armada-500/
206 …Product Brief : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_pb…
207 …Design guide : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_de…
208 …Developers manual : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_de…
209 …Specification : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_em…
210 …Specification update : http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_sp…
[all …]
|
| /Linux-v4.19/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 the
172 The user application consumes UMEM addrs from this ring.
185 The user application consumes struct xdp_desc descriptors from this
197 The user application produces struct xdp_desc descriptors to this
207 The user application inserts the socket into the map, via the bpf()
[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-v4.19/Documentation/misc-devices/ |
| D | ibmvmc.rst | 37 In the management partition, a management application exists which enables
42 The management application runs on a Linux logical partition on a
46 application using a combination of HMC to hypervisor interfaces and
50 application component are passed to the hypervisor over a VMC interface,
67 for communicating between the management application and the hypervisor. It
106 This section provides an example for the management application
121 which will be used for management application session initialization.
145 connection can be established. The application layer performs an open() to
176 During normal runtime, the management application and the hypervisor
178 sending data to the hypervisor, the management application performs a
[all …]
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | net_prio.txt | 8 Nominally, an application would set the priority of its traffic via the
11 1) The application may not have been coded to set this value
12 2) The priority of application traffic is often a site-specific administrative
13 decision rather than an application defined one.
50 One usage for the net_prio cgroup is with mqprio qdisc allowing application
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | pixfmt-v4l2-mplane.rst | 77 - Flags set by the application or driver, see :ref:`format-flags`.
85 the driver for capture streams and by the application for output
91 the driver for capture streams and by the application for output
100 the driver for capture streams and by the application for output
106 the driver for capture streams and by the application for output
|
| D | userp.rst | 18 methods. Buffers (planes) are allocated by the application itself, and
54 area of memory. This happens transparently to the application in the
68 the application's free list and subsequently reused for other purposes,
73 application waits until a filled buffer can be dequeued, and re-enqueues
76 started. In the write loop, when the application runs out of free
78 Two methods exist to suspend execution of the application until one or
96 application needs to synchronize with another event it should examine
116 because an application may share them with other processes.
|
| D | pixfmt-v4l2.rst | 37 - The pixel format or type of compression, set by the application.
59 the value requested by the application, returning ``width`` times
90 by the driver for capture streams and by the application for
120 - Flags set by the application or driver, see :ref:`format-flags`.
128 the driver for capture streams and by the application for output
134 the driver for capture streams and by the application for output
143 the driver for capture streams and by the application for output
149 the driver for capture streams and by the application for output
|
| D | open.rst | 16 helper functions and a common application interface specified in this
57 drivers. The user must enter a device name, or the application can try
103 by the driver, users can for example start a "panel" application to
105 application captures video and audio. In other words, panel applications
106 are comparable to an ALSA audio mixer application. Just opening a V4L2
109 Once an application has allocated the memory buffers needed for
113 :ref:`write() <func-write>` functions) that application (filehandle)
132 or similar means. This is better handled by a proxy application in user
|
| D | vidioc-enum-frameintervals.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
80 without any interaction from the application itself. This means that the
81 enumeration data is consistent if the application does not perform any
99 the application, *OUT* denotes values that the driver fills in. The
100 application should zero out all members except for the *IN* fields.
|
| D | vidioc-enum-framesizes.rst | 49 (zero-based) is valid. The application should increase the index by
68 When the application calls the function with index zero, it must check
80 without any interaction from the application itself. This means that the
81 enumeration data is consistent if the application does not perform any
89 the application, *OUT* denotes values that the driver fills in. The
90 application should zero out all members except for the *IN* fields.
|
| D | vidioc-g-fmt.rst | 41 format) exchanged between driver and application.
47 ``V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE``. When the application calls the
61 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
66 parameters acceptable for both the application and driver. On success
72 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
|
| /Linux-v4.19/Documentation/x86/ |
| D | protection-keys.txt | 11 when an application changes protection domains. It works by
36 pkey_alloc(). An application calls the WRPKRU instruction
45 ... application runs here
47 Now, if the application needs to update the data at 'ptr', it can
83 or when the kernel does the access on the application's behalf like
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/isdn/ |
| D | README.audio | 50 the application. See below for data format
83 received from the application via phone line.
87 On incoming calls, if the application responds to a RING
98 starts sending audio data to the application. There are several
129 CONNECT, and starts transferring data from application to the phone line.
|
| /Linux-v4.19/Documentation/power/ |
| D | swsusp-and-swap-files.txt | 30 2) Use an application that will bmap the swap file with the help of the
41 application in 2) (of course, this step may be carried out automatically
42 by the same application that determines the swap file's header offset using the
47 Use a userland suspend application that will set the partition and offset
|
| /Linux-v4.19/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
|
