Searched refs:receiving (Results 1 – 25 of 181) sorted by relevance
12345678
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 13 (receiving an EOF at each message boundary).
31 (receiving an EOF at each message boundary).
41 Each read gives back one message at time (receiving an EOF at
52 Each read gives back one message at time (receiving an EOF at
82 (receiving an EOF at each message boundary).
109 (receiving an EOF at each message boundary).
|
| /linux-6.12.1/drivers/virt/ |
| D | Kconfig | 39 receiving the shutdown doorbell from a manager partition.
41 4) A kernel interface for receiving callbacks when a managed
|
| /linux-6.12.1/Documentation/admin-guide/media/ |
| D | starfive_camss.rst | 42 - MIPI: The MIPI interface, receiving data from a MIPI CSI-2 camera sensor.
44 - Parallel: The parallel interface, receiving data from a parallel sensor.
|
| D | imx.rst | 186 These are the CSI entities. They have a single sink pad receiving from
209 IDMAC channel. For example, if the CSI sink pad is receiving in UYVY
211 in YUYV order. Also, if the CSI sink pad is receiving a packed YUV
287 in low and medium modes, because these modes require receiving
305 can be activated at the same time if the sink pad is receiving from
307 can be activated if the sink pad is receiving from ipuX_vdic (frames
337 receiving from ipuX_vdic.
341 ipuX_vdic is included in the pipeline (ipuX_ic_prp is receiving from
|
| /linux-6.12.1/Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 58 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.
|
| D | lirc-get-rec-mode.rst | 63 - Device does not support receiving.
|
| D | lirc-dev-intro.rst | 49 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-6.12.1/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 171 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-6.12.1/drivers/net/wireguard/ |
| D | receive.c | 252 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()
|
| D | noise.h | 34 struct noise_symmetric_key receiving; member
|
| /linux-6.12.1/drivers/hwtracing/stm/ |
| D | Kconfig | 23 The receiving side only needs to be able to decode the MIPI
38 The receiving side must be able to decode this protocol in
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-rf-tuner.rst | 44 to receiving party needs. Driver configures filters to fulfill
88 Is synthesizer PLL locked? RF tuner is receiving given frequency
|
| D | vidioc-g-tuner.rst | 127 - 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
|
| D | dev-mem2mem.rst | 18 and capture (receiving the processed frames from the hardware into
|
| /linux-6.12.1/Documentation/scsi/ |
| D | cxgb3i.rst | 20 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-6.12.1/Documentation/devicetree/bindings/media/ |
| D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
| /linux-6.12.1/Documentation/bpf/ |
| D | prog_sk_lookup.rst | 23 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-6.12.1/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 19 - interrupts: specifies the interrupt number for receiving messages ("rx")
|
| /linux-6.12.1/Documentation/networking/ |
| D | kcm.rst | 80 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).
|
| D | gtp.rst | 110 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
|
| D | tuntap.rst | 23 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
|
| /linux-6.12.1/drivers/net/hippi/ |
| D | Kconfig | 36 transmitting and receiving. This memory cannot be used by any other
|
| /linux-6.12.1/Documentation/driver-api/surface_aggregator/clients/ |
| D | san.rst | 26 receiving dGPU events does not miss any events due to the SAN interface not
|
| /linux-6.12.1/drivers/thunderbolt/ |
| D | Kconfig | 54 This allows sending and receiving DMA traffic through loopback
|
| /linux-6.12.1/security/smack/ |
| D | Kconfig | 51 receiving process. If this option is selected, the delivery
|
12345678