Searched full:send (Results 1 – 25 of 483) sorted by relevance
12345678910>>...20
| /Documentation/devicetree/bindings/mailbox/ |
| D | apple,mailbox.yaml | 17 One of the two FIFOs is used to send data to a co-processor while the other
52 - description: send fifo is empty interrupt
53 - description: send fifo is not empty interrupt
59 - const: send-empty
60 - const: send-not-empty
85 interrupt-names = "send-empty", "send-not-empty",
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 6 source send operations to destination receives. The following parameters must
14 The ordering rules require that when more than one pair of send and receive
15 message envelopes may match, the pair that includes the earliest posted-send
31 1. The Eager protocol- the complete message is sent when the send is
32 processed by the sender. A completion send is received in the send_cq
46 to the MPI receive routines in the posted receive list and posts send messages
47 using the MPI send routines. The head of the posted receive list may be
50 When send is initiated and arrives at the receive side, if there is no
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 62 send()/write() system call family. The result of the cipher operation is
79 particular cipher instance. When invoking send/write or recv/read
80 system calls to send data to the kernel or obtain data from the
88 the input buffer used for the send/write system call and the output
120 Using the send() system call, the application provides the data that
121 should be processed with the message digest. The send system call allows
124 - MSG_MORE: If this flag is set, the send system call acts like a
126 calculated. If the flag is not set, the send system call calculates
154 Before data can be sent to the kernel using the write/send system call
165 send/recv system call family. That cmsghdr data structure holds the
[all …]
|
| /Documentation/networking/ |
| D | rds.rst | 55 Sockets must be bound before you can send or receive data.
79 setsockopt(SOL_SOCKET): send and receive buffer size
80 RDS honors the send and receive buffer size socket options.
90 mark the port as "congested" and send a congestion update to
104 An attempt to send a message that exceeds SO_SNDSIZE will
107 An attempt to send a message that would take the total number
111 An attempt to send a message to a destination that is marked
135 POLLOUT is a little harder. Since you can essentially send
137 there's room on the send queue (ie the number of bytes queued
152 it detects a timeout. For instance, if it tried to send a message,
[all …]
|
| D | tls.rst | 69 For example, we can send an encrypted hello world record as follows:
74 send(sock, msg, strlen(msg));
76 send() data is directly encrypted from the userspace buffer provided
77 to the encrypted kernel send buffer if possible.
79 The sendfile system call will send the file's data over TLS records of maximum
88 TLS records are created and sent after each send() call, unless
93 This buffer is allocated at the time send() is called, such that
94 either the entire send() call will return -ENOMEM (or block waiting
95 for memory), or the encryption will always succeed. If send() returns
123 Send TLS control messages
[all …]
|
| D | msg_zerocopy.rst | 9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
20 underlying copy avoidance mechanism to common socket send calls.
67 send system call. By default it simply ignores these. To avoid enabling
79 The change to send (or sendto, sendmsg, sendmmsg) itself is trivial.
84 ret = send(fd, buf, sizeof(buf), MSG_ZEROCOPY);
108 maintains an internal unsigned 32-bit counter. Each send call with
119 send syscall is followed by a poll and recvmsg on the error queue.
141 every couple of send calls.
146 a zero error code, however, to not block send and recv calls.
216 scatter-gather I/O cannot send packets made up of kernel generated
|
| D | mac80211-injection.rst | 49 IEEE80211_RADIOTAP_MCS_BW_40 send in HT40 mode
66 * 1: send using 40MHz channel width
67 * 4: send using 80MHz channel width
68 * 11: send using 160MHz channel width
93 After composing the packet contents, it is sent by send()-ing it to a logical
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-func.rst | 15 lirc-get-send-mode
18 lirc-set-send-duty-cycle
23 lirc-set-send-carrier
|
| D | lirc-get-features.rst | 77 .. _LIRC-CAN-SET-SEND-CARRIER:
84 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
140 .. _LIRC-CAN-SEND-RAW:
146 .. _LIRC-CAN-SEND-PULSE:
156 .. _LIRC-CAN-SEND-MODE2:
163 .. _LIRC-CAN-SEND-LIRCCODE:
|
| D | lirc-set-send-carrier.rst | 13 LIRC_SET_SEND_CARRIER - Set send carrier used to modulate IR TX.
34 Set send carrier used to modulate IR PWM pulses and spaces.
|
| /Documentation/hid/ |
| D | uhid.rst | 48 The first thing you should do is send a UHID_CREATE2 event. This will
62 If you want to send data on the interrupt channel to the HID subsystem, you send
63 a HID_INPUT2 event with your raw data payload. If the kernel wants to send data
74 If your device disconnects, you should send a UHID_DESTROY event. This will
75 unregister the device. You can now send UHID_CREATE2 again to register a new
91 This creates the internal HID device. No I/O is possible until you send this
103 You must send UHID_CREATE2 before sending input to the kernel! This event
159 send UHID_INPUT2 events to the kernel.
166 This is sent if the HID device driver wants to send raw data to the I/O
180 GET_REPORT (or if it fails), you must send a UHID_GET_REPORT_REPLY to the
[all …]
|
| D | hidraw.rst | 16 which send and receive data in a way that is inconsistent with their report
112 Send a Feature Report
114 This ioctl will send a feature report to the device. Per the HID
133 Send an Input Report
135 This ioctl will send an input report to the device, using the control endpoint.
153 Send an Output Report
155 This ioctl will send an output report to the device, using the control endpoint.
|
| D | intel-ish-hid.rst | 129 internal queues to sequence messages and send them in order to the firmware.
149 The transport layer uses them to send and receive messages.
177 Once connection is established, peers send each other flow control bus messages
178 independently. Every peer may send a message only if it has received a
179 flow-control credit before. Once it has sent a message, it may not send another one
181 Either side can send disconnect request bus message to end communication. Also
192 ISHTP client from either host or FW side wants to send something, it decides
193 whether to send over IPC or over DMA; for each transfer the decision is
202 if the host doesn't support DMA, then it won't send DMA allocation, so FW can't
203 send DMA; if FW doesn't support DMA then it won't respond with
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | max98373.txt | 13 - maxim,vmon-slot-no : slot number used to send voltage information
18 - maxim,imon-slot-no : slot number used to send current information
21 - maxim,spkfb-slot-no : slot number used to send speaker feedback information
|
| /Documentation/devicetree/bindings/mtd/ |
| D | mxic-nand.txt | 10 - clock-names: should contain "ps", "send" and "send_dly"
11 - clocks: should contain 3 phandles for the "ps", "send" and
29 clock-names = "send", "send_dly", "ps";
|
| /Documentation/driver-api/pldmfw/ |
| D | driver-ops.rst | 25 The ``.send_package_data`` operation is used to send the device-specific
29 length. The device driver should send this data to firmware.
37 device driver should send the component information to the device firmware,
48 flash a given component. The driver must perform any steps necessary to send
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pca954x.yaml | 17 attached to the parent bus by using the SMBus "Send Byte"
80 maxim,send-flush-out-sequence:
82 description: Send a flush-out sequence to stuck auxiliary buses
87 description: Send a STOP condition to the auxiliary buses when the switch
125 maxim,send-flush-out-sequence: false
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy-p_sys-t | 30 the default and stands for "never send the timestamp".
36 Time interval in milliseconds. Send a CLOCKSYNC packet if
39 stands for "never send the CLOCKSYNC". It makes sense to
|
| /Documentation/input/ |
| D | uinput.rst | 11 this virtual device is created, the process can send events through it,
28 create uinput devices and send events. libevdev is less error-prone than
41 send a key event. All default imports and error handlers were removed for
90 * to send. This pause is only needed in our example code!
94 /* Key press, report the event, send key release, and report again */
153 * to send. This pause is only needed in our example code!
224 * to send. This pause is only needed in our example code!
228 /* Key press, report the event, send key release, and report again */
|
| /Documentation/input/devices/ |
| D | sentelic.rst | 455 FSP will send out enable/disable packet when FSP receive PS/2 enable/disable
529 1. send 0xf3 PS/2 command to FSP;
531 2. send 0x66 PS/2 command to FSP;
533 3. send 0x88 PS/2 command to FSP;
535 4. send 0xf3 PS/2 command to FSP;
541 a. send 0x68 PS/2 command to FSP;
543 b. send the inverted register address to FSP and goto step 8;
549 a. send 0xcc PS/2 command to FSP;
551 b. send the swapped register address to FSP and goto step 8;
553 7. send 0x66 PS/2 command to FSP;
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend_fcalls.rst | 18 fe-diseqc-send-master-cmd
20 fe-diseqc-send-burst
|
| /Documentation/process/ |
| D | email-clients.rst | 9 These days most developers use ``git send-email`` instead of regular
13 If you are new to ``git`` then send your first patch to yourself. Save it
15 then review the changelog with ``git log``. When that works then send
33 Email clients that are used for Linux kernel patches should send the
37 Don't send patches with ``format=flowed``. This can cause unexpected
45 If you configure your email client to send emails with UTF-8 encoding,
60 It's a good idea to send a patch to yourself, save the received message,
85 - :menuselection:`Do Not Send Flowed Text` must be ``enabled``
156 If you absolutely must send patches as attachments instead of inlining
204 to send them::
[all …]
|
| /Documentation/arch/powerpc/ |
| D | vas-api.rst | 30 kernel to setup channel / window which can be used to send compression
41 establish connection to the engine. It means send window is opened on GZIP
49 established connection or send window by closing the file descriptor
52 Note that applications can send several requests with the same window or
81 node is opened, Kernel opens send window on a suitable instance of NX
201 Applications should use the copy and paste instructions to send CRB to NX.
216 Applications send requests to NX and wait for the status by polling on
237 to the process who opened the send window on which the original request was
245 In the case of multi-thread applications, NX send windows can be shared
246 across all threads. For example, a child thread can open a send window,
[all …]
|
| /Documentation/virt/gunyah/ |
| D | message-queue.rst | 19 involves 2 message queues. Message queue 1 allows VM_A to send messages to VM_B.
20 Message queue 2 allows VM_B to send messages to VM_A.
44 Clear-to-Send.
46 For VM_B to send a message to VM_A, the process is identical, except that
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 67 Any ufs bug report you can send to daniel.pirkl@email.cz or
68 to dushistov@mail.ru (do not send partition tables bug reports).
|
12345678910>>...20