| /Linux-v5.10/net/bluetooth/cmtp/ |
| D | capi.c | 77 BT_DBG("session %p application %p appl %d", session, app, appl); in cmtp_application_add()
92 BT_DBG("session %p application %p", session, app); in cmtp_application_del()
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()
[all …]
|
| /Linux-v5.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/
292 - Application processor only
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_…
[all …]
|
| /Linux-v5.10/net/netlabel/ |
| D | netlabel_mgmt.h | 26 * Sent by an application to add a domain mapping to the NetLabel system.
53 * Sent by an application to remove a domain mapping from the NetLabel
61 * This message can be sent either from an application or by the kernel in
62 * response to an application generated LISTALL message. When sent by an
63 * application there is no payload and the NLM_F_DUMP flag should be set.
90 * Sent by an application to set the default domain mapping for the NetLabel
107 * Sent by an application to remove the default domain mapping from the
111 * This message can be sent either from an application or by the kernel in
112 * response to an application generated LISTDEF message. When sent by an
113 * application there may be an optional payload.
[all …]
|
| D | netlabel_unlabeled.h | 25 * This message is sent from an application to add a new static label for
44 * This message is sent from an application to remove an existing static
62 * This message can be sent either from an application or by the kernel in
63 * response to an application generated STATICLIST message. When sent by an
64 * application there is no payload and the NLM_F_DUMP flag should be set.
83 * This message is sent from an application to set the default static
101 * This message is sent from an application to remove the existing default
115 * This message can be sent either from an application or by the kernel in
116 * response to an application generated STATICLISTDEF message. When sent by
117 * an application there is no payload and the NLM_F_DUMP flag should be set.
[all …]
|
| /Linux-v5.10/arch/arm/mach-pxa/include/mach/ |
| D | pxa3xx-regs.h | 40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
41 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
42 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
43 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
44 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
45 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
46 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
47 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
48 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
49 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| 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-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 | 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.
|
| /Linux-v5.10/drivers/iio/accel/ |
| D | mma9551_core.c | 33 /* GPIO Application */
37 /* Sleep/Wake application */
43 /* AFE application */
48 /* Reset/Suspend/Clear application */
202 * @app_id: Application ID
203 * @reg: Application register
227 * @app_id: Application ID
228 * @reg: Application register
252 * @app_id: Application ID
253 * @reg: Application register
[all …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.10/net/ipv4/netfilter/ |
| D | nf_nat_snmp_basic.asn1 | 22 application-wide
60 [APPLICATION 0]
64 [APPLICATION 1]
68 [APPLICATION 2]
74 [APPLICATION 3]
78 [APPLICATION 4]
82 [APPLICATION 6]
|
| /Linux-v5.10/drivers/staging/octeon-usb/ |
| D | octeon-hcd.h | 110 * The application must program this register as part of the O2P USB core
142 * The application uses this bit to mask or unmask the interrupt
145 * * 1'b0: Mask the interrupt assertion to the application.
146 * * 1'b1: Unmask the interrupt assertion to the application.
195 * The application uses this bit to indicate the O2P USB core's
236 * application. When an interrupt bit is masked, the interrupt associated with
324 * This register interrupts the application for system-level events in the
329 * type R_SS_WC, the application must write 1'b1 into the bit. The FIFO status
368 * application must read the Host All Channels Interrupt (HAINT)
372 * cause of the interrupt. The application must clear the
[all …]
|
| /Linux-v5.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
|
| /Linux-v5.10/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 …]
|
| /Linux-v5.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 | 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
123 user-space application.
130 application need explicit synchronization of multiple
161 The user application produces UMEM addrs to this ring. Note that, if
162 running the application with aligned chunk mode, the kernel will mask
165 to the same chunk. If the user application is run in the unaligned
179 The user application consumes UMEM addrs from this ring.
192 The user application consumes struct xdp_desc descriptors from this
[all …]
|
| /Linux-v5.10/drivers/crypto/caam/ |
| D | qi.h | 23 * This is the request structure the driver application should fill while
29 * caam_qi_cbk - application's callback function invoked by the driver when the
73 * caam_drv_req - The request structure the driver application should fill while
78 * @app_ctx: arbitrary context attached with request by the application
80 * The fields mentioned below should not be used by application.
98 * the application. This handle must be submitted along with each enqueue
99 * request to the driver by the application.
101 * @cpu: CPU where the application prefers to the driver to receive CAAM
|
| /Linux-v5.10/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.
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/block/ |
| D | data-integrity.rst | 12 application tried to write is most likely lost.
15 application meant it to. Recent additions to both the SCSI family
68 generated by Linux or the application at very low cost (comparable to
90 they enable us to protect the entire path from application to storage
98 transport protocols completely transparent to the application.
103 It is completely unreasonable for an application to be aware whether
107 from the application. As far as the application (and to some extent
162 the protection data, as well as getting and setting application tags.
169 will require extra work due to the application tag.
199 attached. It can also use the application tag space if this is
|
| /Linux-v5.10/security/selinux/ |
| D | status.c | 24 * application should reference the status page according to the seqlock
27 * Typically, application checks status->sequence at the head of access
30 * number, it means something happen, so application will reset userspace
32 * In most cases, application shall confirm the kernel status is not
61 * So, application can know it was updated. in selinux_kernel_status_page()
|
