| /openbmc/linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-ib62x0.dts | 35 pmx_led_usb_transfer: pmx-led-usb-transfer {
|
| /openbmc/linux/drivers/video/fbdev/ |
| H A D | pxa168fb.h | 183 #define CFG_KEEPXFER(transfer) ((transfer) << 6) argument
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | oem-extension-numbering.md | 109 for example, there is no way to insert a stop command within a transfer.
165 - In the unlikely event a transfer specifies multiple read steps, all bytes read
|
| /openbmc/linux/Documentation/devicetree/bindings/display/hisilicon/ |
| H A D | hisi-ade.txt | 5 timing stream and transfer to DSI.
|
| /openbmc/linux/Documentation/driver-api/pldmfw/ |
| H A D | driver-ops.rst | 38 and wait for a response. The provided transfer flag indicates whether this
|
| /openbmc/linux/drivers/net/wireless/microchip/wilc1000/ |
| H A D | Kconfig | 19 the 1-bit/4-bit SD transfer mode at the clock range of 0-50 MHz.
|
| /openbmc/linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | ovti,ov5675.yaml | 70 # Supports max data transfer of 900 Mbps per lane
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | crypto_engine.rst | 63 When your driver receives a crypto_request, you must to transfer it to
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rsync/ |
| H A D | rsync_3.3.0.bb | 3 DESCRIPTION = "rsync is an open source utility that provides fast incremental file transfer."
|
| /openbmc/qemu/hw/ssi/ |
| H A D | ssi.c | 92 return ssc->transfer(dev, val); in ssi_transfer_raw_default()
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 132 - Make sure no data transfer will happen for Scsi_Cmnd requests
138 - Test against expected data transfer direction from SCRIPTS.
143 - Get data transfer direction from the scsi command structure
148 - Test against expected data transfer direction from SCRIPTS.
174 - Get data transfer direction from the scsi command structure
272 - Calculate the data transfer residual as the 2's complement
283 async transfer for the target.
318 in DATA IN phase with WIDE transfer when the byte count gets odd).
324 transfer, whatever a SWIDE is present (OVERRUN in DATA IN phase)
|
| H A D | ChangeLog.sym53c8xx_2 | 13 * Add the target number to the display of transfer parameters.
76 - Add DT/ST (double/simple transition) in the transfer
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | dma-api-howto.rst | 93 transfer.
198 1) Use some non-DMA mode for data transfer, if possible.
326 transfer, unmapped right after it (unless you use dma_sync_* below)
456 transfer.
461 If you absolutely cannot know the direction of the DMA transfer,
530 from the interrupt which told you that the DMA transfer is done.
564 from the interrupt which told you that the DMA transfer is done.
613 transfer call either::
642 After the last DMA transfer call one of the DMA unmap routines
683 * the DMA transfer with the CPU first
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NGPL | 36 …te or transfer NetHack except as expressly provided under this License Agreement. Any attempt othe…
|
| H A D | IPA | 22 7. "Reproduction and Other Exploitation" shall mean reproduction, transfer, distribution, l…
30 …hall be held by the Licensor. In no sense is this Agreement intended to transfer any right relatin…
44 6. The Recipient may reproduce the Licensed Program as is without modification and transfer…
|
| H A D | Imlib2 | 5 …a method to get this software via some reasonable mechanism (electronic transfer via a network or …
|
| /openbmc/linux/Documentation/driver-api/virtio/ |
| H A D | writing_virtio_drivers.rst | 141 of the direction of the data transfer.
143 To configure a buffer transfer from the driver to the device, first you
|
| /openbmc/linux/Documentation/power/ |
| H A D | userland-swsusp.rst | 51 has been created the read() operation can be used to transfer
56 uploaded snapshot image; before calling it you should transfer
118 The device's read() operation can be used to transfer the snapshot image from
|
| /openbmc/libmctp/docs/bindings/ |
| H A D | vendor-ibm-astlpc.md | 5 This design provides an efficient method to transfer MCTP packets between the
98 The basic components used for the transfer are:
104 In order to transfer a packet, either side of the channel (BMC or host) will:
460 The KCS hardware (used as the full transfer channel) can be used to transfer
466 We could use the VUART hardware to transfer the MCTP packets according to the
|
| /openbmc/linux/sound/core/oss/ |
| H A D | linear.c | 177 plugin->transfer = linear_transfer; in snd_pcm_plugin_build_linear()
|
| H A D | pcm_plugin.h | 52 snd_pcm_sframes_t (*transfer)(struct snd_pcm_plugin *plugin, member
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A D | rsirq.c | 225 {ACPI_RSC_2BITFLAG, ACPI_RS_OFFSET(data.dma.transfer),
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/afe/ |
| H A D | temperature-sense-rtd.yaml | 21 The general transfer function here is (using SI units)
|
| /openbmc/linux/drivers/scsi/arm/ |
| H A D | fas216.h | 303 … (*pseudo)(struct Scsi_Host *host, struct scsi_pointer *SCp, fasdmadir_t direction, int transfer);
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | rockchip-i2s.yaml | 11 audio data transfer between devices in the system.
|