| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | renesas,rzv2m.yaml | 27 - description: Data transmission/reception interrupt
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A D | nvidia,tegra20-sflash.yaml | 38 - description: DMA channel used for transmission
|
| H A D | nvidia,tegra20-slink.yaml | 40 - description: DMA channel used for transmission
|
| H A D | cdns,xspi.yaml | 15 single, dual, quad or octal wire transmission modes for
|
| H A D | nvidia,tegra114-spi.yaml | 48 - description: DMA channel for the transmission FIFO
|
| H A D | qcom,spi-qcom-qspi.yaml | 13 dual, or quad wire transmission modes for read/write access to slaves such
|
| /openbmc/linux/Documentation/networking/ |
| H A D | packet_mmap.rst | 37 transmission, multiple packets can be sent through one system call to get the
42 transmission process, but it isn't everything. At least, if you are capturing
46 enabled. For transmission, check the MTU (Maximum Transmission Unit) used and
95 for capture and transmission. This can be done by mapping the
103 How to use mmap() directly to improve transmission process
107 [setup] socket() -------> creation of the transmission socket
110 bind() ---------> bind transmission socket with a network interface
114 [transmission] poll() ---------> wait for free packets (optional)
120 [shutdown] close() --------> destruction of the transmission socket and
418 To use one socket for capture and transmission, the mapping of both the
[all …]
|
| H A D | bareudp.rst | 56 sending packet buffer to the bareudp device for transmission. On reception the
|
| /openbmc/linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | tc358743.txt | 23 is half of the bps per lane due to DDR transmission.
|
| /openbmc/linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 34 bool "Enable support for SCMI Raw transmission mode"
38 Enable support for SCMI Raw transmission mode.
52 Allow SCMI Raw transmission mode to coexist with normal SCMI stack.
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | rc-core.rst | 31 The infrared transmission is done by blinking a infrared emitter using a
36 In other words, a typical IR transmission can be viewed as a sequence of
|
| /openbmc/linux/Documentation/w1/slaves/ |
| H A D | w1_ds2413.rst | 51 The chip has some kind of basic protection against transmission errors.
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-type-t.rst | 8 modulation used in transmission. The fontend types are given by
|
| /openbmc/linux/Documentation/devicetree/bindings/serial/ |
| H A D | renesas,scifb.yaml | 62 transmission, and one for reception.
|
| H A D | renesas,scifa.yaml | 62 transmission, and one for reception.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | libata.rst | 654 transmission errors sometimes cause this kind of errors.
784 ATA bus error means that data corruption occurred during transmission
791 indicating transmission error.
794 mechanism to determine that the timeout is due to transmission error.
798 As described above, transmission errors can cause wide variety of
801 transmission error or not; therefore, it's necessary to employ some kind
807 lowering ATA bus transmission speed is one of actions which may
837 Timeouts can also be caused by transmission errors. Refer to
956 cables or controllers and it's quite common to see high transmission
957 error rate. This can be mitigated by lowering transmission speed.
[all …]
|
| /openbmc/openbmc-test-automation/openpower/pel/ |
| H A D | test_bmc_pel.robot | 725 [Documentation] Verify host transmission state of offloaded PEL logs.
736 [Documentation] Verify host transmission state of not offloaded PEL logs.
939 [Documentation] Inject PEL log of given type and verify its host transmission state.
945 # expected_transmission_state Expected host transmission state of PEL log.
968 # Check host transmission state for the cases where PEL is
974 # Adding delay before checking host transmission for the cases where PEL is
982 [Documentation] Check if PEL's host transmission state is matching expected state.
986 # expected_transmission_state Expected transmission state of PEL log.
988 # Check the transmission details in the error log.
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-read.rst | 56 used for transmission, and ``scancode`` to the decoded scancode,
|
| /openbmc/linux/drivers/net/arcnet/ |
| H A D | Kconfig | 63 transmission:
66 2=transmission accepted by the receiver hardware
|
| /openbmc/linux/Documentation/driver-api/serial/ |
| H A D | serial-iso7816.rst | 72 /* Set transmission factors: */
|
| /openbmc/linux/Documentation/devicetree/bindings/display/bridge/ |
| H A D | ps8640.yaml | 16 plus clock, at a transmission rate up to 1.5Gbit/sec per lane. The
|
| /openbmc/linux/Documentation/devicetree/bindings/display/mediatek/ |
| H A D | mediatek,dsc.yaml | 18 real-time compression, transmission, decompression and Display.
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/ |
| H A D | internal.rst | 106 Packets are the fundamental transmission unit of the SSH protocol. They are
181 packet transmission. In each iteration, it (waits for and) checks if the
183 from the queue and increments its counter for the number of transmission
223 packets, started when the respective packet begins (re-)transmission (i.e.
224 this timeout is armed once per transmission attempt on the transmitter
239 timeout for the packet will be disabled until the next transmission attempt
242 Note that due to transmission and packet acknowledgment timeouts, the packet
383 transmission. It checks if the next request on the request queue can be
433 Note that this timeout, in combination with packet transmission and
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | renesas,mmcif.yaml | 53 transmission, and one for reception.
|
| /openbmc/linux/tools/testing/vsock/ |
| H A D | README | 43 starts data transmission to the receiver. After data processing is done,
|