/openbmc/linux/drivers/dma/xilinx/ |
H A D | xilinx_dpdma.c | 1694 ddev->directions = BIT(DMA_MEM_TO_DEV); in xilinx_dpdma_probe()
|
/openbmc/linux/Documentation/filesystems/ |
H A D | ramfs-rootfs-initramfs.rst | 343 Future directions:
|
/openbmc/linux/drivers/dma/ |
H A D | sun6i-dma.c | 1357 sdc->slave.directions = BIT(DMA_DEV_TO_MEM) | in sun6i_dma_probe()
|
H A D | tegra20-apb-dma.c | 1544 tdma->dma_dev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in tegra_dma_probe()
|
H A D | ste_dma40.c | 2841 dev->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in d40_ops_init() 2846 dev->directions = BIT(DMA_MEM_TO_MEM); in d40_ops_init()
|
H A D | pxa_dma.c | 1405 pdev->slave.directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in pxad_probe()
|
H A D | at_hdmac.c | 2056 atdma->dma_device.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in at_dma_probe()
|
H A D | stm32-mdma.c | 1691 dd->directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV) | in stm32_mdma_probe()
|
H A D | imx-sdma.c | 2302 sdma->dma_device.directions = SDMA_DMA_DIRECTIONS; in sdma_probe()
|
H A D | at_xdmac.c | 2360 atxdmac->dma.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in at_xdmac_probe()
|
/openbmc/linux/drivers/dma/sh/ |
H A D | rcar-dmac.c | 1946 engine->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM); in rcar_dmac_probe()
|
/openbmc/phosphor-logging/ |
H A D | README.md | 178 - Following the [directions](#adding-application-specific-error-yaml) defined
|
/openbmc/linux/drivers/dma/lgm/ |
H A D | lgm-dma.c | 1692 dma_dev->directions = BIT(DMA_MEM_TO_DEV) | in intel_ldma_probe()
|
/openbmc/linux/Documentation/networking/ |
H A D | tls-offload.rst | 404 Note that each TCP connection requires a TLS session in both directions,
|
H A D | snmp_counter.rst | 432 - Data is sent in both directions. The fast path only supports pure senders 442 directions. When the TCP window scale option is not used, kernel will
|
/openbmc/linux/Documentation/userspace-api/netlink/ |
H A D | intro.rst | 32 in both directions (to and from the kernel). The operations are still
|
/openbmc/linux/drivers/dma/ti/ |
H A D | omap-dma.c | 1711 od->ddev.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in omap_dma_probe()
|
/openbmc/linux/Documentation/networking/device_drivers/can/ctu/ |
H A D | ctucanfd-driver.rst | 600 …mmunity about the project and invited us to events focused on CAN bus future development directions
|
/openbmc/linux/Documentation/process/ |
H A D | adding-syscalls.rst | 92 zero value gives the previous behaviour, then this allows both directions of
|
H A D | 2.Process.rst | 343 directions. The whole thing would not work anywhere near as well as it
|
/openbmc/linux/drivers/dma/qcom/ |
H A D | gpi.c | 2255 gpi_dev->dma_device.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); in gpi_probe()
|
/openbmc/linux/Documentation/sound/kernel-api/ |
H A D | writing-an-alsa-driver.rst | 1771 capture directions, because it uses two different codecs (SB- and 1772 AD-compatible) for different directions. 2432 capture directions. 3488 and capture directions. In the playback case, you copy the given amount
|
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
H A D | SSPL-1 | 212 equivalent copying facilities, provided you maintain clear directions
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | RPL-1.5 | 233 include a copy of this License or directions on how to obtain a copy with
|
H A D | SSPL-1.0 | 212 equivalent copying facilities, provided you maintain clear directions
|