Searched full:sent (Results 1 – 25 of 296) sorted by relevance
12345678910>>...12
| /Documentation/input/ |
| D | notifier.rst | 14 - KBD_KEYCODE events are always sent before other events, value is the keycode.
15 - KBD_UNBOUND_KEYCODE events are sent if the keycode is not bound to a keysym.
17 - KBD_UNICODE events are sent if the keycode -> keysym translation produced a
19 - KBD_KEYSYM events are sent if the keycode -> keysym translation produced a
21 - KBD_POST_KEYSYM events are sent after the treatment of non-unicode keysyms.
|
| D | userio.rst | 27 /dev/userio character device in their applications. Commands are sent to the
43 ``type`` describes the type of command that is being sent. This can be any one
47 Each command should be sent by writing the struct directly to the character
50 to the kernel log. Only one command can be sent at a time, any additional data
76 ``data`` is the interrupt data being sent.
|
| /Documentation/hid/ |
| D | uhid.rst | 39 payloads are sent. You must not split a single event across multiple read()'s or
40 multiple write()'s. A single event must always be sent as a whole. Furthermore,
41 only a single event can be sent per read() or write(). Pending data is ignored.
98 UHID_INPUT events can be sent to the kernel.
125 This is sent when the HID device is started. Consider this as an answer to
126 UHID_CREATE2. This is always the first event that is sent. Note that this
140 For messages sent by user-space to the kernel, you must adjust the
144 This is sent when the HID device is stopped. Consider this as an answer to
155 This is sent when the HID device is opened. That is, the data that the HID
162 This is sent when there are no more processes which read the HID data. It is
[all …]
|
| D | hidraw.rst | 6 Interface Devices (HIDs). It differs from hiddev in that reports sent and
7 received are not parsed by the HID parser, but are sent to and received from
17 descriptors. Because hiddev parses reports which are sent and received
44 devices, the reports read using read() are the reports sent from the device
58 the device has an INTERRUPT OUT endpoint, the report will be sent on that
59 endpoint. If it does not, the report will be sent over the control endpoint,
114 specification, feature reports are always sent using the control endpoint.
|
| D | hid-transport.rst | 100 reports. No management commands or data acknowledgements are sent on this
101 channel. Any unrequested incoming or outgoing data report must be sent on
106 device management. Unrequested data input events must not be sent on this
111 Outgoing reports are usually sent on the ctrl channel via synchronous
119 data is generated by the device and sent to the host with or without
122 - OUTPUT Report: Output reports change device states. They are sent from host
124 reports are never sent from device to host, but a host can retrieve their
131 Feature reports are never sent without requests. A host must explicitly set
132 or retrieve a feature report. This also means, feature reports are never sent
135 INPUT and OUTPUT reports can be sent as pure data reports on the intr channel.
[all …]
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 32 socket and a poll notification will be sent to the appropriate
42 the netlink event socket and a poll notification will be sent to the
47 There are a few other ACPI notifications that can be sent by the firmware. In
49 well as sent as a poll notification to a sysfs file. The events are as
|
| /Documentation/isdn/ |
| D | avmb1.rst | 133 capi messages sent without DATA_B3_REQ
135 capi DATA_B3_REQ sent
154 capi messages sent without DATA_B3_REQ
156 capi DATA_B3_REQ sent
169 capi messages sent without DATA_B3_REQ
171 capi DATA_B3_REQ sent
192 capi messages sent without DATA_B3_REQ
194 capi DATA_B3_REQ sent
|
| /Documentation/networking/ |
| D | ipsec.txt | 13 payload, the IP datagram MUST be sent in the original non-compressed
14 form. To clarify: If an IP datagram is sent non-compressed, no
23 where IP datagrams of size smaller than the threshold are sent in the
|
| D | rds.txt | 110 a congestion update is sent to all peers.
197 RETRANSMITTED - packet has previously been sent
220 Sending an ack immediately would allow the sender to free the sent
222 traffic to be used for acks. RDS piggybacks acks on sent data
249 bitmap changes it is sent through all the connections which
281 be sent and sets header fields as needed, based on the socket API.
282 This is then queued for the individual connection and sent by the
312 partially-sent datagrams to be retransmitted when the connection is
385 socket will be sent over the attached path using TCP to segment/reassemble
414 get sent from some reserved port, RDS_FLAG_PROBE_PORT (in <linux/rds.h>)
[all …]
|
| D | snmp_counter.rst | 43 The number of packets sent via IP layer, for both single cast and
274 The number of packets sent by the TCP layer. As mentioned in RFC1213,
286 It means the TCP layer sends a SYN, and come into the SYN-SENT
384 the 'segments sent containing the RST flag', but in linux kernel, this
393 is not lost in the network, but the packet is not sent yet, the TCP
404 This counter indicates many keepalive packets were sent. The keepalive
432 - Data is sent in both directions. The fast path only supports pure senders
441 used, because when using "Delayed ack", the data is sent in both
632 packet again. (2) Assume packet 1,2,3,4,5 are sent by the sender, and
779 Packets are dropped by PAWS in Syn-Sent status.
[all …]
|
| D | mac80211-injection.txt | 28 IEEE80211_RADIOTAP_F_TX_NOACK: frame should be sent without waiting for
84 After composing the packet contents, it is sent by send()-ing it to a logical
|
| /Documentation/media/uapi/dvb/ |
| D | fe-set-voltage.rst | 19 FE_SET_VOLTAGE - Allow setting the DC level sent to the antenna subsystem.
42 This ioctl allows to set the DC voltage level sent through the antenna
50 control the voltage level, provided that either 13V or 18V is sent to
|
| /Documentation/infiniband/ |
| D | user_mad.rst | 89 MADs are sent using write(). The agent ID for sending should be
92 RMPP so arbitrary length MAD can be sent. For example::
113 field in network byte order) in MADs being sent to match
115 the kernel and will be overwritten before a MAD is sent.
121 MADs that are sent and did not provide a way for obtaining the P_Key
|
| /Documentation/i2c/ |
| D | slave-interface.rst | 77 Another I2C master wants to write data to us. This event should be sent once
84 'val': backend returns first byte to be sent
88 Another I2C master wants to read data from us. This event should be sent once
98 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret'
104 'val': backend returns next byte to be sent
108 The bus driver requests the next byte to be sent to another I2C master in
114 needs to be sent again on the next I2C_SLAVE_READ_REQUEST, depending a bit on
|
| D | i2c-protocol.rst | 23 [..]: Data sent by I2C device, as opposed to data sent by the
50 a start bit S is sent and the transaction continues. An example of
66 message is sent.
|
| /Documentation/devicetree/bindings/serial/ |
| D | rs485.txt | 10 * a is the delay between rts signal and beginning of data sent in milliseconds.
12 * b is the delay between end of data sent and rts signal in milliseconds
|
| /Documentation/accounting/ |
| D | taskstats.rst | 37 one of the cpus in the cpumask, its per-pid statistics are sent to the
43 an additional record containing the per-tgid stats is also sent to userspace.
78 1. Commands: Sent from user to kernel. Commands to get data on
93 2. Response for a command: sent from the kernel in response to a userspace
105 3. New message sent by kernel whenever a task exits. The payload consists of a
128 gets sent to userspace (along with the per-task data).
|
| /Documentation/driver-api/ |
| D | sync_file.rst | 17 The sync_file then can be sent to the consumer (DRM driver for example), that
32 Sync files can go either to or from userspace. When a sync_file is sent from
63 The sync_file fd now can be sent to userspace.
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | aspeed-wdt.txt | 38 - aspeed,external-signal: If property is present then signal is sent to
40 specified no external signal is sent.
|
| /Documentation/filesystems/ |
| D | fuse-io.txt | 23 In write-through mode each write is immediately sent to userspace as one or more
25 uncached, but fully written pages). No READ requests are ever sent for writes,
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-subscribe-event.rst | 94 - When this event is subscribed an initial event will be sent
100 - If set, then events directly caused by an ioctl will also be sent
103 a V4L2_EVENT_CTRL to be sent back to that same filehandle.
|
| /Documentation/ |
| D | rpmsg.txt | 75 and its length (in bytes). The message will be sent on the specified
98 The message will then be sent to the remote processor to which the
122 The message will then be sent to the remote processor to which the
141 and its length (in bytes). The message will be sent on the specified
162 The message will then be sent to the remote processor to which the
183 The message will then be sent to the remote processor to which the
|
| /Documentation/admin-guide/ |
| D | binderfs.rst | 42 sent through the ``binder-control`` device node. A request is sent in the form
|
| /Documentation/ABI/testing/ |
| D | sysfs-c2port | 22 to the C2 port from the system. No commands can be sent
38 No commands can be sent till this entry is set to 0.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | ltc2952-poweroff.txt | 4 been sent, the chip's watchdog has to be reset to gracefully shut down.
|
12345678910>>...12