Searched full:sent (Results 1 – 25 of 416) sorted by relevance
12345678910>>...17
| /Documentation/input/ |
| D | notifier.rst | 15 - KBD_KEYCODE events are always sent before other events, value is the keycode.
16 - KBD_UNBOUND_KEYCODE events are sent if the keycode is not bound to a keysym.
18 - KBD_UNICODE events are sent if the keycode -> keysym translation produced a
20 - KBD_KEYSYM events are sent if the keycode -> keysym translation produced a
22 - 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/ABI/testing/ |
| D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured
12 and sent while the replies are read back one message at time
22 in little-endian binary format to have it sent to the configured
30 and sent while the replies are read back one message at time
74 in little-endian binary format to have it sent to the configured
81 and sent while the replies are read back one message at time
98 in little-endian binary format to have it sent to the configured
108 and sent while the replies are read back one message at time
|
| D | sysfs-bus-iio-chemical-sgp40 | 6 Set the temperature. This value is sent to the sensor for
15 Set the relative humidity. This value is sent to the sensor for
|
| D | sysfs-timecard | 36 PPS1 signal is sent to the PPS1 selector
37 PPS2 signal is sent to the PPS2 selector
38 TS1 signal is sent to timestamper 1
39 TS2 signal is sent to timestamper 2
40 TS3 signal is sent to timestamper 3
41 TS4 signal is sent to timestamper 4
42 IRIG signal is sent to the IRIG-B module
43 DCF signal is sent to the DCF module
44 FREQ1 signal is sent to frequency counter 1
45 FREQ2 signal is sent to frequency counter 2
[all …]
|
| /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 | 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
104 not sent via intr, except if high throughput is required.
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
[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
45 devices, the reports read using read() are the reports sent from the device
59 the device has an INTERRUPT OUT endpoint, the report will be sent on that
60 endpoint. If it does not, the report will be sent over the control endpoint,
115 specification, feature reports are always sent using the control endpoint.
|
| /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/networking/ |
| D | ipsec.rst | 21 payload, the IP datagram MUST be sent in the original non-compressed
22 form. To clarify: If an IP datagram is sent non-compressed, no
31 where IP datagrams of size smaller than the threshold are sent in the
|
| D | rds.rst | 118 a congestion update is sent to all peers.
209 RETRANSMITTED packet has previously been sent
234 Sending an ack immediately would allow the sender to free the sent
236 traffic to be used for acks. RDS piggybacks acks on sent data
263 bitmap changes it is sent through all the connections which
295 be sent and sets header fields as needed, based on the socket API.
296 This is then queued for the individual connection and sent by the
332 partially-sent datagrams to be retransmitted when the connection is
410 socket will be sent over the attached path using TCP to segment/reassemble
439 get sent from some reserved port, RDS_FLAG_PROBE_PORT (in <linux/rds.h>)
[all …]
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 46 Reserved bits must be zero when sent and ignored when received.
51 Multiplexer ID is to indicate the PDN on which data has to be sent.
72 Reserved bits must be zero when sent and ignored when received.
77 Multiplexer ID is to indicate the PDN on which data has to be sent.
93 Reserved bits must be zero when sent and ignored when received.
131 Multiplexer ID is to indicate the PDN on which data has to be sent.
155 Reserved bits must be zero when sent and ignored when received.
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-set-voltage.rst | 13 FE_SET_VOLTAGE - Allow setting the DC level sent to the antenna subsystem.
34 This ioctl allows to set the DC voltage level sent through the antenna
42 control the voltage level, provided that either 13V or 18V is sent to
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 22 events. Commands are sent to the EC and may have a different implications in
23 different contexts. Events are sent by the EC upon some internal state
114 (``SDTX_EVENT_LATCH_STATUS``) will be sent once the latch has been opened
117 sent with the cancel reason indicating the specific failure.
140 point when a detachment operation is in progress (i.e. after the EC has sent
143 process is canceled on the EC-level and an identical event is being sent.
191 Unknown status or error codes sent by the EC are assigned to the ``UNKNOWN``
328 Sent when a detachment process is started or, if in progress, aborted by the
330 (``SDTX_IOCTL_LATCH_REQUEST``) being sent from user-space.
337 Sent when a detachment process is canceled by the EC due to unfulfilled
[all …]
|
| D | san.rst | 14 relating to the discrete GPU (dGPU) of the Surface Book 2 can be sent from
16 only currently known event sent via this interface is a dGPU power-on
|
| /Documentation/i2c/ |
| D | i2c-protocol.rst | 20 [..] Data sent by I2C device, as opposed to data sent by the
47 condition P a start condition S is sent and the transaction continues.
63 message is sent.
|
| D | slave-interface.rst | 77 Another I2C master wants to write data to us. This event should be sent once
87 'val': backend returns first byte to be sent
91 Another I2C master wants to read data from us. This event should be sent once
101 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret'
107 'val': backend returns next byte to be sent
111 The bus driver requests the next byte to be sent to another I2C master in
117 needs to be sent again on the next I2C_SLAVE_READ_REQUEST, depending a bit on
|
| /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/block/ |
| D | ublk.rst | 103 WRT IO command communication. Basic device info is sent together with this
106 for which the info is negotiated with the driver and sent back to the server.
114 sent before sending ``UBLK_CMD_START_DEV``.
119 pthread & io_uring for handling ublk IO), this command is sent to the
168 ``UBLK_CMD_GET_DEV_INFO`` is always sent to kernel, and the feature of
181 ``UBLK_CMD_GET_DEV_INFO`` is always sent to kernel, and the feature of
221 Once the flag is set, all control commands can be sent by unprivileged
252 Sent from the server IO pthread for fetching future incoming IO requests
253 destined to ``/dev/ublkb*``. This command is sent only once from the server
|
| D | blk-mq.rst | 54 sent to the software queue.
60 queue, to be sent in the future, when the hardware is able.
66 (represented by struct blk_mq_ctx) in case that they weren't sent
95 eligible to be sent to the hardware. One of the possible schedulers to be
116 requests that were ready to be sent first. The number of hardware queues
135 driver, the tag is sent back to the block layer to notify it of the finalization.
|
| /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/surface_aggregator/ |
| D | ssh.rst | 117 - Sent on error in previously received message.
121 - Sent to acknowledge receival of |DATA| frame.
125 - Sent to transfer data. Sequenced.
196 Commands are sent as payload inside a data frame. Currently, this is the
248 We differentiate between requests (sent by the host), responses (sent by the
249 EC in response to a request), and events (sent by the EC without a preceding
271 separated, e.g. by an event being sent after the request but before the
283 events sent from the respective source. Note that an event should still be
323 possibly also commands) should be re-sent by the host if a certain timeout
334 the EC is sent again, e.g. due to the host not receiving an |ACK|, the EC
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subscribe-event.rst | 85 - When this event is subscribed an initial event will be sent
91 - If set, then events directly caused by an ioctl will also be sent
94 a V4L2_EVENT_CTRL to be sent back to that same filehandle.
|
| /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/process/ |
| D | maintainer-soc.rst | 58 All typical platform related patches should be sent via SoC submaintainers
73 3. Introducing a completely new SoC platform. Such new SoC work should be sent
75 community review. After positive community review, work should be sent to
83 thus work sent to this address should be already considered as acceptable by
182 Small sets of patches can also be sent as separate emails to soc@kernel.org,
202 Pull requests for bugfixes for the current release can be sent at any time, but
|
12345678910>>...17