| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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).
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A 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.
|
| H A D | lirc-get-rec-mode.rst | 63 - Device does not support receiving.
|
| H A 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.
|
| /openbmc/linux/drivers/virt/ |
| H A D | Kconfig | 40 receiving the shutdown doorbell from a manager partition.
42 4) A kernel interface for receiving callbacks when a managed
|
| /openbmc/linux/drivers/staging/pi433/Documentation/ |
| H A 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
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-networking/cyrus-sasl/cyrus-sasl/ |
| H A D | 0001-sample-Rename-dprintf-to-cyrus_dprintf.patch | 24 - dprintf(0, "receiving capability list... ");
25 + cyrus_dprintf(0, "receiving capability list... ");
|
| /openbmc/linux/Documentation/virt/kvm/ |
| H A 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
|
| /openbmc/linux/drivers/net/wireguard/ |
| H A 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()
|
| /openbmc/linux/drivers/hwtracing/stm/ |
| H A 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
|
| /openbmc/u-boot/doc/ |
| H A D | README.VLAN | 4 You control the sending/receiving of VLAN tagged packets with the
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/ |
| H A D | phosphor-ipmi-blobs_git.bb | 2 …es of OEM IPMI commands that implement the BLOB protocol for sending and receiving data over IPMI."
|
| H A D | phosphor-ipmi-ethstats_git.bb | 2 DESCRIPTION = "This package handles receiving OEM IPMI commands to provide ethernet device statisti…
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Barr | 1 … commercial software package is also permitted, but I would appreciate receiving a free copy for…
|
| H A D | IBM-pibs | 1 This source code has been made available to you by IBM on an AS-IS basis. Anyone receiving this so…
|
| /openbmc/linux/Documentation/scsi/ |
| H A 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
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| H A 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
|
| /openbmc/u-boot/Licenses/ |
| H A D | ibm-pibs.txt | 2 basis. Anyone receiving this source is licensed under IBM
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | imx-audio-spdif.txt | 21 - spdif-in : This is a boolean property. If present, the receiving
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
| /openbmc/linux/Documentation/bpf/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | intel,ixp4xx-gpio.txt | 12 The remaining 4 GPIO lines can not be used for receiving
|
| /openbmc/linux/Documentation/devicetree/bindings/firmware/ |
| H A D | nvidia,tegra210-bpmp.txt | 19 - interrupts: specifies the interrupt number for receiving messages ("rx")
|
| /openbmc/phosphor-pid-control/ |
| H A D | README.md | 92 We'll be receiving sensor updates with such regularly, however, at present it
121 - `ipmi` - Manual control for any zone is handled by receiving an IPMI message.
122 This holds the ipmid provider for receiving those messages and sending them
|