| /linux-3.3/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()
189 struct cmtp_application *application; in cmtp_recv_interopmsg() local
207 application = cmtp_application_get(session, CMTP_MSGNUM, msgnum); in cmtp_recv_interopmsg()
208 if (application) { in cmtp_recv_interopmsg()
209 application->state = BT_CONNECTED; in cmtp_recv_interopmsg()
210 application->msgnum = 0; in cmtp_recv_interopmsg()
211 application->mapping = CAPIMSG_APPID(skb->data); in cmtp_recv_interopmsg()
220 application = cmtp_application_get(session, CMTP_MAPPING, appl); in cmtp_recv_interopmsg()
221 if (application) { in cmtp_recv_interopmsg()
[all …]
|
| /linux-3.3/net/netlabel/ |
| D | netlabel_mgmt.h | 41 * Sent by an application to add a domain mapping to the NetLabel system.
65 * Sent by an application to remove a domain mapping from the NetLabel
73 * This message can be sent either from an application or by the kernel in
74 * response to an application generated LISTALL message. When sent by an
75 * application there is no payload and the NLM_F_DUMP flag should be set.
101 * Sent by an application to set the default domain mapping for the NetLabel
115 * Sent by an application to remove the default domain mapping from the
119 * This message can be sent either from an application or by the kernel in
120 * response to an application generated LISTDEF message. When sent by an
121 * application there is no payload. On success the kernel should send a
[all …]
|
| D | netlabel_unlabeled.h | 40 * This message is sent from an application to add a new static label for
59 * This message is sent from an application to remove an existing static
77 * This message can be sent either from an application or by the kernel in
78 * response to an application generated STATICLIST message. When sent by an
79 * application there is no payload and the NLM_F_DUMP flag should be set.
98 * This message is sent from an application to set the default static
116 * This message is sent from an application to remove the existing default
130 * This message can be sent either from an application or by the kernel in
131 * response to an application generated STATICLISTDEF message. When sent by
132 * an application there is no payload and the NLM_F_DUMP flag should be set.
[all …]
|
| D | netlabel_cipso_v4.h | 40 * Sent by an application to add a new DOI mapping table.
57 * Sent by an application to remove a specific DOI mapping table from the
65 * Sent by an application to list the details of a DOI definition. On
89 * This message is sent by an application to list the valid DOIs on the
90 * system. When sent by an application there is no payload and the
|
| /linux-3.3/arch/arm/mach-pxa/include/mach/ |
| D | pxa3xx-regs.h | 43 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
44 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
45 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
46 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
47 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
48 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
49 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
50 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
51 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
52 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
|
| /linux-3.3/Documentation/ |
| D | sysfs-rules.txt | 34 application's behavior, but never try to search for sysfs. Never try
57 is a bug in the application
76 bug in the application
82 like the "device"-link, is a bug in the application
123 the application.
130 a bug in the application.
140 a device in /sys/devices/ is a bug in the application.
141 Accessing /sys/class/net/eth0/device is a bug in the application.
151 the application.
163 access the chain of parents is a bug in the application.
|
| /linux-3.3/Documentation/cgroups/ |
| 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-3.3/drivers/staging/mei/ |
| D | mei.txt | 15 communication channel between a host application and the Intel ME feature.
42 HTTP/S that are received from a remote management console application.
52 An application maintains communication with an Intel ME feature while
64 and host application.
70 A code snippet for an application communicating with
134 local application using the same network interface as a remote application
137 When a local application sends a message addressed to the local Intel AMT host
151 single application.
|
| /linux-3.3/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-3.3/drivers/net/wireless/iwlwifi/ |
| D | iwl-testmode.h | 75 * commands from user application to the uCode,
99 * to user application
102 * to user application
105 * to user application
108 * commands from user application to own change the ownership of the uCode
109 * if application has the ownership, the only host command from
188 * application command
194 * application
200 * application
|
| /linux-3.3/Documentation/block/ |
| D | data-integrity.txt | 8 application tried to write is most likely lost.
11 application meant it to. Recent additions to both the SCSI family
64 generated by Linux or the application at very low cost (comparable to
86 they enable us to protect the entire path from application to storage
94 transport protocols completely transparent to the application.
99 It is completely unreasonable for an application to be aware whether
103 from the application. As far as the application (and to some extent
156 the protection data, as well as getting and setting application tags.
163 will require extra work due to the application tag.
191 attached. It can also use the application tag space if this is
[all …]
|
| /linux-3.3/drivers/scsi/mpt2sas/ |
| D | mpt2sas_ctl.h | 283 * To obtain a bus/id the application sets
286 * To obtain the device handle the application sets
303 /* application flags for mpt2_diag_register, mpt2_diag_query */
314 * struct mpt2_diag_register - application register with driver
322 * @unique_id - tag specified by application that is used to signal ownership
340 * struct mpt2_diag_unregister - application unregister with driver
364 * The application will send only buffer_type and unique_id. Driver will
386 * allowing an application to read the buffer without fear that firmware is
401 * reading data at into the specified application buffer
403 * application buffer starting at starting_offset.
|
| /linux-3.3/security/selinux/ss/ |
| D | status.c | 27 * application should reference the status page according to the seqlock
30 * Typically, application checks status->sequence at the head of access
33 * number, it means something happen, so application will reset userspace
35 * In most cases, application shall confirm the kernel status is not
66 * So, application can know it was updated. in selinux_kernel_status_page()
|
| /linux-3.3/Documentation/isdn/ |
| D | INTERFACE.CAPI | 7 COMMON-ISDN-API (CAPI) is an application programming interface standard used
16 application registration to an available device, forwarding it to the
18 directions between the application and the hardware driver.
52 3. Application Registration and Communication
56 register_appl() callback function. A unique Application ID (ApplID, u16) is
58 parameter structure provided by the application. This is analogous to the
62 application may be passed to the driver for the device via calls to the
65 Kernel CAPI for forwarding to an application, specifying its ApplID.
70 messages for that application may be passed to or from the device anymore.
269 for forwarding to the specified application
[all …]
|
| 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-3.3/drivers/hid/ |
| D | hid-uclogic.c | 31 * Usage (Pen), ; Pen (02h, application collection)
32 * Collection (Application),
75 * Usage (Mouse), ; Mouse (02h, application collection)
76 * Collection (Application),
103 * Usage (Mouse), ; Mouse (02h, application collection)
104 * Collection (Application),
159 0xA1, 0x01, /* Collection (Application), */
201 0xA1, 0x01, /* Collection (Application), */
239 0xA1, 0x01, /* Collection (Application), */
275 0xA1, 0x01, /* Collection (Application), */
[all …]
|
| D | hid-waltop.c | 59 * Usage (Mouse), ; Mouse (02h, application collection)
60 * Collection (Application),
87 * Usage (Pen), ; Pen (02h, application collection)
88 * Collection (Application),
182 0xA1, 0x01, /* Collection (Application), */
234 * Usage (Mouse), ; Mouse (02h, application collection)
235 * Collection (Application),
262 * Usage (Pen), ; Pen (02h, application collection)
263 * Collection (Application),
344 * Usage (Keyboard), ; Keyboard (06h, application collection)
[all …]
|
| /linux-3.3/Documentation/networking/ |
| 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-3.3/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-3.3/arch/mips/include/asm/octeon/ |
| D | cvmx-bootmem.h | 30 * application start time.
54 * application init code converts addresses to 64 bit addresses before the
55 * application starts.
136 * to the application by the bootloader.
148 * passed to the application by the bootloader at a specific
164 * passed to the application by the bootloader within a specified
190 * to the application by the bootloader, and assign it a name in the
207 * to the application by the bootloader, and assign it a name in the
226 * that was passed to the application by the bootloader, and assign it
|
| D | cvmx-sysinfo.h | 37 * Structure describing application specific information.
56 /* Application image specific variables */
65 /* coremask defining cores running application */
91 * addresses, and it is up to the application to use the
100 * application to use the proper addressing mode (XKPHYS,
|
| /linux-3.3/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-3.3/mm/ |
| D | madvise.c | 149 * Application no longer needs these pages. If the pages are dirty,
162 * the swap area if the application is discarding it.
187 * Application wants to free up the pages and associated backing store.
310 * kernel without affecting the correct operation of the application.
321 * MADV_WILLNEED - the application is notifying the system to read
323 * MADV_DONTNEED - the application is finished with the given range,
325 * MADV_REMOVE - the application wants to free up the given range of
330 * MADV_MERGEABLE - the application recommends that KSM try to merge pages in
337 * "behavior" is not a valid value, or application
|
| /linux-3.3/Documentation/dvb/ |
| D | ci.txt | 16 (2) one requires a userspace application, ca_zap. This small userland
17 application is in charge of sending the descrambling related information
20 This application requires the following to function properly as of now.
72 the application programmer it would be as simple as sending/receiving an
108 Application layer only and no session management is taken care of by the
109 application. The driver/hardware will take care of all that.
113 exist in this case in the application to driver communication. It is
|
| /linux-3.3/drivers/staging/tidspbridge/Documentation/ |
| D | README | 26 A GPP application communicates with its associated DSP task running on the
28 application can use the API to pass messages to a DSP task that is managing
40 some level of interoperability of application code using DSP/BIOS Bridge
66 device independent I/O streams, performing application-specific processing
|