Home
last modified time | relevance | path

Searched refs:receiving (Results 1 – 25 of 134) sorted by relevance

123456

/linux/Documentation/ABI/testing/
H A Ddebugfs-scmi-raw13 (receiving an EOF at each message boundary).
31 (receiving an EOF at each message boundary).
47 (receiving an EOF at each message boundary).
67 (receiving an EOF at each message boundary).
77 Each read gives back one message at time (receiving an EOF at
88 Each read gives back one message at time (receiving an EOF at
118 (receiving an EOF at each message boundary).
145 (receiving an EOF at each message boundary).
171 (receiving an EOF at each message boundary).
200 (receiving an EOF at each message boundary).
H A Dsysfs-class-led-trigger-tty49 DTE is receiving a carrier from the DCE.
/linux/drivers/virt/
H A DKconfig39 receiving the shutdown doorbell from a manager partition.
41 4) A kernel interface for receiving callbacks when a managed
/linux/Documentation/userspace-api/media/rc/
H A Dlirc-get-features.rst58 This is raw IR driver for receiving. This means that
74 This is a scancode driver for receiving. This means that
161 :ref:`LIRC_MODE_MODE2 <lirc-mode-mode2>` can only be used for receiving.
H A Dlirc-get-rec-mode.rst63 - Device does not support receiving.
H A Dlirc-dev-intro.rst49 LIRC supports some modes of receiving and sending IR codes, as shown
58 This mode is for both sending and receiving IR.
65 For receiving, you read struct lirc_scancode from the LIRC device.
/linux/Documentation/virt/kvm/
H A Dvcpu-requests.rst171 Requesters that want the receiving VCPU to handle new state need to ensure
172 the newly written state is observable to the receiving VCPU thread's CPU
175 request bit. Additionally, on the receiving VCPU thread's side, a
188 When making requests to VCPUs, we want to avoid the receiving VCPU
206 the requesting thread and the receiving VCPU. With the memory barriers we
208 !kvm_request_pending() on its last check and then not receiving an IPI for
260 receiving VCPU, as the final kvm_request_pending() check does for
/linux/drivers/net/wireguard/
H A Dreceive.c252 if (unlikely(!READ_ONCE(keypair->receiving.is_valid) || in decrypt_packet()
253 wg_birthdate_has_expired(keypair->receiving.birthdate, REJECT_AFTER_TIME) || in decrypt_packet()
255 WRITE_ONCE(keypair->receiving.is_valid, false); in decrypt_packet()
280 keypair->receiving.key)) in decrypt_packet()
H A Dnoise.h34 struct noise_symmetric_key receiving; member
/linux/Documentation/scsi/
H A Dcxgb3i.rst20 On receiving, Chelsio S3 h/w computes and verifies the Header and
38 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-rf-tuner.rst45 to receiving party needs. Driver configures filters to fulfill
89 Is synthesizer PLL locked? RF tuner is receiving given frequency
H A Dvidioc-g-tuner.rst127 - receiving mono audio
131 - receiving stereo audio and a secondary audio program
135 - receiving mono or stereo audio, the hardware cannot distinguish
139 - receiving bilingual audio
143 - receiving mono, stereo or bilingual audio
H A Ddev-mem2mem.rst19 and capture (receiving the processed frames from the hardware into
/linux/tools/testing/selftests/net/packetdrill/
H A Dtcp_ooo-before-and-after-accept.pkt9 // its initial sk_rcvbuf (tcp_rmem[1]) when receiving ooo packets.
/linux/Documentation/bpf/
H A Dprog_sk_lookup.rst23 1. receiving connections on a range of IP addresses, e.g. 192.0.2.0/24, when
26 2. receiving connections on all or a wide range of ports, i.e. an L7 proxy use
/linux/Documentation/devicetree/bindings/media/
H A Dst-rc.txt11 protocol used for receiving remote control signals. rx-mode should
/linux/Documentation/networking/
H A Dgtp.rst110 GTP-U uses UDP for transporting PDUs. The receiving UDP port is 2151
162 GTP-U uses UDP for transporting PDU's. The receiving UDP port is 2152
179 * when receiving the local entity is defined by the local
199 Therefore, the receiving side identifies tunnels exclusively based on
H A Dkcm.rst80 BPF program must be specified. The program is called at the start of receiving
192 A setsockopt is used to disable or enable receiving on a KCM socket.
224 applications to use a message based interface for sending and receiving
280 may have occurred in the middle of receiving a message).
H A Dtuntap.rst23 instead of receiving packets from physical media, receives them from
133 file descriptors (queues) to parallelize packets sending or receiving. The
232 Ethernet device, which instead of receiving packets from a physical
H A Dj1939.rst88 receiving side.
145 TP transfers. ETP cannot be broadcast and always needs a receiving client.
345 receiving broadcast packets use the socket option ``SO_BROADCAST``:
454 - **Parameter Group Number (PGN)**: Focus on receiving messages with specific
554 The ``SO_BROADCAST`` option enables the sending and receiving of broadcast
694 When receiving extended error messages from the error queue, the error
713 - For ETP transfers, it is sent after receiving a CTS (Clear to Send)
732 session has been acknowledged, typically after receiving the End of
804 - After receiving this message, the receiver discards the partially received
828 - ``J1939_NLA_DEST_ADDR``: 8-bit destination address of the receiving ECU.
[all …]
/linux/Documentation/devicetree/bindings/firmware/
H A Dnvidia,tegra210-bpmp.txt19 - interrupts: specifies the interrupt number for receiving messages ("rx")
/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dsan.rst26 receiving dGPU events does not miss any events due to the SAN interface not
/linux/security/smack/
H A DKconfig51 receiving process. If this option is selected, the delivery
/linux/drivers/media/radio/si470x/
H A DKconfig28 if you don't want to use the device solely for RDS receiving,
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmpic-msgr.txt19 for receiving interrupts. Interrupt-specifier consists of two cells: first

123456