Searched refs:receiving (Results 1 – 25 of 183) sorted by relevance
12345678
| /linux-5.19.10/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra194-tcu.yaml | 17 for transmitting and one for receiving, that is used to communicate
39 List of phandles to mailbox channels used for receiving and
42 - description: mailbox for receiving data from hardware UART
|
| /linux-5.19.10/Documentation/devicetree/bindings/media/ |
| D | qcom,sm8250-camss.yaml | 117 Input port for receiving CSI data.
140 Input port for receiving CSI data.
163 Input port for receiving CSI data.
186 Input port for receiving CSI data.
209 Input port for receiving CSI data.
232 Input port for receiving CSI data.
|
| D | qcom,sdm845-camss.yaml | 100 Input port for receiving CSI data.
119 Input port for receiving CSI data.
138 Input port for receiving CSI data.
157 Input port for receiving CSI data.
|
| D | qcom,sdm660-camss.yaml | 106 Input port for receiving CSI data.
125 Input port for receiving CSI data.
144 Input port for receiving CSI data.
163 Input port for receiving CSI data.
|
| D | qcom,msm8996-camss.yaml | 100 Input port for receiving CSI data.
126 Input port for receiving CSI data.
145 Input port for receiving CSI data.
164 Input port for receiving CSI data.
|
| D | qcom,msm8916-camss.yaml | 78 Input port for receiving CSI data.
104 Input port for receiving CSI data.
|
| D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
| /linux-5.19.10/drivers/virt/ |
| D | Kconfig | 40 receiving the shutdown doorbell from a manager partition.
42 4) A kernel interface for receiving callbacks when a managed
|
| /linux-5.19.10/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-5.19.10/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 182 Requesters that want the receiving VCPU to handle new state need to ensure
183 the newly written state is observable to the receiving VCPU thread's CPU
186 request bit. Additionally, on the receiving VCPU thread's side, a
199 When making requests to VCPUs, we want to avoid the receiving VCPU
217 the requesting thread and the receiving VCPU. With the memory barriers we
219 !kvm_request_pending() on its last check and then not receiving an IPI for
271 receiving VCPU, as the final kvm_request_pending() check does for
303 Generally it only makes sense for the receiving VCPU thread to clear a
305 thread and the receiving VCPU thread are executed serially, such as when
309 receiving VCPU thread to handle the request in VCPU RUN. The only current
|
| /linux-5.19.10/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 44 As soon as an application sets a request for receiving a telegram, the reception
45 configuration set is written to the rf module and it gets set into receiving mode.
49 As soon as the predefined RSSI level is met, a receiving cycle starts. Similar
69 PI433_IOC_RD_RX_CFG - get the receiving parameters from the driver
70 PI433_IOC_WR_RX_CFG - set the receiving parameters
164 The rx configuration is transferred via struct pi433_rx_cfg, the parameterset for receiving. It is …
261 off and the rf chip is used in raw receiving mode. This may be
|
| /linux-5.19.10/drivers/hwtracing/stm/ |
| D | Kconfig | 24 The receiving side only needs to be able to decode the MIPI
39 The receiving side must be able to decode this protocol in
|
| /linux-5.19.10/drivers/net/wireguard/ |
| D | receive.c | 259 if (unlikely(!READ_ONCE(keypair->receiving.is_valid) || in decrypt_packet()
260 wg_birthdate_has_expired(keypair->receiving.birthdate, REJECT_AFTER_TIME) || in decrypt_packet()
262 WRITE_ONCE(keypair->receiving.is_valid, false); in decrypt_packet()
287 keypair->receiving.key)) in decrypt_packet()
|
| D | noise.h | 34 struct noise_symmetric_key receiving; member
|
| /linux-5.19.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | loongson,htvec.yaml | 14 receiving vectorized interrupts from PCH's interrupt controller.
|
| /linux-5.19.10/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-5.19.10/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
|
| /linux-5.19.10/Documentation/devicetree/bindings/sound/ |
| D | imx-audio-spdif.txt | 21 - spdif-in : This is a boolean property. If present, the receiving
|
| /linux-5.19.10/Documentation/devicetree/bindings/phy/ |
| D | allwinner,sun6i-a31-mipi-dphy.yaml | 44 - "rx" for receiving (e.g. when used with MIPI CSI-2);
|
| /linux-5.19.10/Documentation/devicetree/bindings/gpio/ |
| D | intel,ixp4xx-gpio.txt | 12 The remaining 4 GPIO lines can not be used for receiving
|
| /linux-5.19.10/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-5.19.10/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 19 - interrupts: specifies the interrupt number for receiving messages ("rx")
|
12345678