| /openbmc/linux/Documentation/hid/ |
| H A D | amd-sfh-hid.rst | 71 1. Command transfer via the C2P mailbox registers.
72 2. Data transfer via DRAM.
|
| H A D | intel-ish-hid.rst | 184 3.3.3 Peer to Peer data transfer
187 Peer to Peer data transfer can happen with or without using DMA. Depending on
191 Each side (host and FW) manages its DMA transfer memory independently. When an
193 whether to send over IPC or over DMA; for each transfer the decision is
206 it's request to do host->ISH DMA transfer; when FW sends DMA_XFER, it means
|
| /openbmc/qemu/hw/i3c/ |
| H A D | trace-events | 18 aspeed_i3c_device_transfer_ccc(uint32_t deviceid, uint8_t ccc) "I3C Dev[%u] transfer CCC 0x%" PRIx8
29 i3c_end_transfer(void) "I3C transfer done"
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A D | spi-peripheral-props.yaml | 72 Delay, in microseconds, after a read transfer.
89 Delay, in microseconds, after a write transfer.
|
| H A D | icpdas-lp8841-spi-rtc.txt | 6 The device uses the standard MicroWire half-duplex transfer timing.
|
| /openbmc/linux/drivers/scsi/aic7xxx/ |
| H A D | aic7xxx.seq | 731 * Do we need any more segments for this transfer?
804 * If the transfer is less than a cachline,
935 * The transfer has terminated either due to a phase
958 * in this transfer.
961 * to fetch additional segments for this transfer,
1009 * transfer messages prior to doing this, but this
1108 /* Start DMA data transfer. */
1757 * any message transfer.
2252 * transfer, we must empty the fifo of all
2254 * continue the transfer. This does not
[all …]
|
| /openbmc/docs/designs/ |
| H A D | binarystore-via-blobs.md | 52 1. The host should only store binary data that is suitable using this transfer
214 **_Security_**: As mentioned, the binary store transfer mechanism doesn't offer
216 either not to transfer security-critical data, or supply their own security
223 then the host would need a handler that understands the blob transfer semantics
|
| /openbmc/linux/arch/alpha/ |
| H A D | Kconfig.debug | 19 ELF headers to determine where to transfer control. Unfortunately,
|
| /openbmc/linux/drivers/ntb/ |
| H A D | Kconfig | 10 transfer data from one system to the other.
|
| /openbmc/u-boot/doc/device-tree-bindings/spi/ |
| H A D | spi-cadence.txt | 31 n_ss_out low and first bit transfer
|
| /openbmc/linux/Documentation/devicetree/bindings/display/ |
| H A D | brcm,bcm2835-hdmi.yaml | 49 transfer audio data.
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | isl29003.rst | 38 transfer.
|
| /openbmc/openbmc/poky/meta/recipes-bsp/lrzsz/ |
| H A D | lrzsz_0.12.20.bb | 1 SUMMARY = "Tools for zmodem/xmodem/ymodem file transfer"
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/ |
| H A D | arm,pl330.yaml | 54 description: quirk for performing burst transfer only
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | README.md | 101 If you're using an LPC data transfer mechanism, you'll need two additional
103 you've reserved memory to be used for the transfer window.
105 If you're using a net data transfer mechanism, you'll also need two additional
163 transfer the data. By default, the data-in-IPMI mechanism is enabled.
|
| /openbmc/linux/Documentation/usb/ |
| H A D | ohci.rst | 27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
|
| /openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
| H A D | ti,secure-proxy.yaml | 30 Contains the secure proxy thread ID used for the specific transfer path.
|
| /openbmc/linux/drivers/video/fbdev/mmp/hw/ |
| H A D | mmp_spi.c | 155 master->transfer = lcd_spi_one_transfer; in lcd_spi_register()
|
| /openbmc/openbmc/poky/meta/recipes-core/glibc/ |
| H A D | glibc.inc | 32 # glibc uses PARALLELMFLAGS variable to pass parallel build info so transfer
|
| /openbmc/sdbusplus/include/sdbusplus/async/stdexec/__detail/ |
| H A D | __execution_fwd.hpp | 191 extern const transfer_t transfer;
|
| /openbmc/linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 337 (for control transfer).
403 This driver supports both control transfer and bulk transfer modes.
404 This driver dose not support interrupt transfer or isochronous
405 transfer modes.
476 This host controller driver emulates USB, looping all data transfer
|
| /openbmc/qemu/hw/scsi/ |
| H A D | trace-events | 69 megasas_scsi_read_start(int cmd, int len) "scmd %d: transfer %d bytes of data"
70 megasas_scsi_write_start(int cmd, int len) "scmd %d: transfer %d bytes of data"
141 pvscsi_process_req_descr_invalid_dir(void) "command with invalid transfer direction rejected"
180 esp_transfer_data(uint32_t dma_left, int32_t ti_size) "transfer %d/%d"
202 esp_pci_error_invalid_dma_direction(void) "invalid DMA transfer direction"
229 spapr_vscsi_srp_transfer_data(uint32_t len) "no data desc transfer, skipping 0x%"PRIx32" bytes"
296 lsi_execute_script_tc_illegal(void) "Illegal transfer control"
318 scsi_disk_read_data_invalid(void) "Data transfer direction invalid"
320 scsi_disk_write_data_invalid(void) "Data transfer direction invalid"
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | ethernet.txt | 10 - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than
|
| /openbmc/u-boot/drivers/sysreset/ |
| H A D | sysreset_mpc83xx.c | 118 "Transfer Type", ttype, transfer[ttype]); in print_83xx_arb_event()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/ckermit/ |
| H A D | ckermit_302.bb | 4 sessions, file transfer, character-set translation, and automation \
|