Searched refs:receiving (Results 1 – 25 of 138) sorted by relevance
123456
| /Linux-v5.4/drivers/virt/ |
| D | Kconfig | 29 receiving the shutdown doorbell from a manager partition.
31 4) A kernel interface for receiving callbacks when a managed
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra194-tcu.txt | 6 for transmitting and one for receiving, that is used to communicate
16 "rx" - Mailbox for receiving data from hardware UART
|
| D | rs485.txt | 18 - rs485-rx-during-tx: empty property that enables the receiving of data even
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 169 Requesters that want the receiving VCPU to handle new state need to ensure
170 the newly written state is observable to the receiving VCPU thread's CPU
173 request bit. Additionally, on the receiving VCPU thread's side, a
186 When making requests to VCPUs, we want to avoid the receiving VCPU
204 the requesting thread and the receiving VCPU. With the memory barriers we
206 !kvm_request_pending() on its last check and then not receiving an IPI for
258 receiving VCPU, as the final kvm_request_pending() check does for
290 Generally it only makes sense for the receiving VCPU thread to clear a
292 thread and the receiving VCPU thread are executed serially, such as when
296 receiving VCPU thread to handle the request in VCPU RUN. The only current
|
| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | lirc-get-features.rst | 65 This is raw IR driver for receiving. This means that
81 This is a scancode driver for receiving. This means that
186 :ref:`LIRC_MODE_MODE2 <lirc-mode-mode2>` can only be used for receiving.
|
| D | lirc-dev-intro.rst | 56 LIRC supports some modes of receiving and sending IR codes, as shown
65 This mode is for both sending and receiving IR.
72 For receiving, you read ``struct lirc_scancode`` from the LIRC device.
|
| D | lirc-get-rec-mode.rst | 68 - Device does not support receiving.
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/scsi/ |
| D | cxgb3i.txt | 16 On receiving, Chelsio S3 h/w computes and verifies the Header and
34 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | imx-audio-spdif.txt | 21 - spdif-in : This is a boolean property. If present, the receiving
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | intel,ixp4xx-gpio.txt | 12 The remaining 4 GPIO lines can not be used for receiving
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | ext-ctrls-rf-tuner.rst | 51 to receiving party needs. Driver configures filters to fulfill
95 Is synthesizer PLL locked? RF tuner is receiving given frequency
|
| D | vidioc-g-tuner.rst | 135 - receiving mono audio
139 - receiving stereo audio and a secondary audio program
143 - receiving mono or stereo audio, the hardware cannot distinguish
147 - receiving bilingual audio
151 - receiving mono, stereo or bilingual audio
|
| D | dev-mem2mem.rst | 25 and capture (receiving the processed frames from the hardware into
|
| /Linux-v5.4/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 19 - interrupts: specifies the interrupt number for receiving messages ("rx")
|
| /Linux-v5.4/Documentation/devicetree/bindings/display/msm/ |
| D | edp.txt | 23 to HPD receiving chip
|
| /Linux-v5.4/Documentation/networking/ |
| D | kcm.txt | 77 BPF program must be specified. The program is called at the start of receiving
188 A setsockopt is used to disable or enable receiving on a KCM socket.
220 applications to use a message based interface for sending and receiving
275 may have occurred in the middle of receiving a message).
|
| D | gtp.txt | 100 GTP-U uses UDP for transporting PDUs. The receiving UDP port is 2151
146 GTP-U uses UDP for transporting PDU's. The receiving UDP port is 2152
163 * when receiving the local entity is defined by the local
183 Therefore, the receiving side identifies tunnels exclusively based on
|
| D | tuntap.txt | 15 instead of receiving packets from physical media, receives them from
111 file descriptors (queues) to parallelize packets sending or receiving. The
203 Ethernet device, which instead of receiving packets from a physical
|
| /Linux-v5.4/drivers/net/hippi/ |
| D | Kconfig | 36 transmitting and receiving. This memory cannot be used by any other
|
| /Linux-v5.4/security/smack/ |
| D | Kconfig | 51 receiving process. If this option is selected, the delivery
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | imx.rst | 157 These are the CSI entities. They have a single sink pad receiving from
180 IDMAC channel. For example, if the CSI sink pad is receiving in UYVY
182 in YUYV order. Also, if the CSI sink pad is receiving a packed YUV
342 in low and medium modes, because these modes require receiving
360 can be activated at the same time if the sink pad is receiving from
362 can be activated if the sink pad is receiving from ipuX_vdic (frames
392 receiving from ipuX_vdic.
396 ipuX_vdic is included in the pipeline (ipuX_ic_prp is receiving from
|
| /Linux-v5.4/drivers/media/radio/si470x/ |
| D | Kconfig | 28 if you don't want to use the device solely for RDS receiving,
|
123456
