Searched refs:receiving (Results 1 – 25 of 128) sorted by relevance
123456
| /Linux-v4.19/drivers/virt/ |
| D | Kconfig | 28 receiving the shutdown doorbell from a manager partition.
30 4) A kernel interface for receiving callbacks when a managed
|
| /Linux-v4.19/Documentation/virtual/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-v4.19/Documentation/media/uapi/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
179 :ref:`LIRC_MODE_MODE2 <lirc-mode-mode2>` can only be used for receiving.
|
| D | lirc-dev-intro.rst | 36 LIRC supports some modes of receiving and sending IR codes, as shown
45 This mode is for both sending and receiving IR.
52 For receiving, you read ``struct lirc_scancode`` from the lirc device,
|
| D | lirc-get-rec-mode.rst | 61 - Device does not support receiving.
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/devicetree/bindings/sound/ |
| D | imx-audio-spdif.txt | 21 - spdif-in : This is a boolean property. If present, the receiving
|
| /Linux-v4.19/Documentation/devicetree/bindings/media/ |
| D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-g-tuner.rst | 128 - receiving mono audio
132 - receiving stereo audio and a secondary audio program
136 - receiving mono or stereo audio, the hardware cannot distinguish
140 - receiving bilingual audio
144 - receiving mono, stereo or bilingual audio
|
| D | dev-teletext.rst | 9 This interface was aimed at devices receiving and demodulating Teletext
|
| D | dev-codec.rst | 16 and capture (receiving the processed frames from the codec hardware into
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/msm/ |
| D | edp.txt | 23 to HPD receiving chip
|
| /Linux-v4.19/Documentation/devicetree/bindings/serial/ |
| D | rs485.txt | 18 - rs485-rx-during-tx: empty property that enables the receiving of data even
|
| D | atmel-usart.txt | 15 - atmel,use-dma-rx: use of PDC or DMA for receiving data
|
| /Linux-v4.19/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-v4.19/drivers/net/hippi/ |
| D | Kconfig | 35 transmitting and receiving. This memory cannot be used by any other
|
| /Linux-v4.19/security/smack/ |
| D | Kconfig | 50 receiving process. If this option is selected, the delivery
|
| /Linux-v4.19/drivers/media/radio/si470x/ |
| D | Kconfig | 27 if you don't want to use the device solely for RDS receiving,
|
| /Linux-v4.19/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-msgr.txt | 19 for receiving interrupts. Interrupt-specifier consists of two cells: first
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | imx.rst | 155 These are the CSI entities. They have a single sink pad receiving from
179 If the sink pad is receiving YUV, the output at the capture device can
334 in low and medium modes, because these modes require receiving
352 can be activated at the same time if the sink pad is receiving from
354 can be activated if the sink pad is receiving from ipuX_vdic (frames
384 receiving from ipuX_vdic.
388 included in the pipeline (ipuX_ic_prp is receiving from ipuX_vdic),
|
| /Linux-v4.19/drivers/block/drbd/ |
| D | Kconfig | 64 512 insert data corruption on receiving side
|
| /Linux-v4.19/Documentation/arm/ |
| D | uefi.txt | 22 The implementation depends on receiving information about the UEFI environment
|
123456
