Home
last modified time | relevance | path

Searched +full:dma +full:- +full:capable (Results 1 – 25 of 356) sorted by relevance

12345678910>>...15

/linux/arch/s390/include/asm/
H A Ddma-types.h1 /* SPDX-License-Identifier: GPL-2.0 */
11 * Contains a 31 bit absolute address to a DMA capable piece of storage.
13 * For CIO, DMA addresses are always absolute addresses. These addresses tend
24 * Contains a 64 bit absolute address to a DMA capable piece of storage.
26 * For CIO, DMA addresses are always absolute addresses. These addresses tend
34 * Although DMA addresses should be obtained using the DMA API, in cases when
36 * DMA-able 31 bit addressable storage, then this function can be safely used.
69 * Although DMA addresses should be obtained using the DMA API, in cases when
71 * DMA-able storage, then this function can be safely used.
/linux/drivers/ata/
H A Dpata_ali.c2 * pata_ali.c - ALI 15x3 PATA for new ATA layer
8 * Copyright (C) 1998-2000 Michel Aubry, Maintainer
9 * Copyright (C) 1998-2000 Andrzej Krzysztofowicz, Maintainer
10 * Copyright (C) 1999-2000 CJ, cjtsai@ali.com.tw, Maintainer
12 * Copyright (C) 1998-2000 Andre Hedrick (andre@linux-ide.org)
22 * otherwise should do atapi DMA (For now for old we do PIO only for
42 MODULE_PARM_DESC(atapi_dma, "Enable ATAPI DMA (0=disable, 1=enable)");
54 DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
55 DMI_MATCH(DMI_BOARD_VERSION, "OmniBook N32N-736"),
59 .ident = "Toshiba Satellite S1800-814",
[all …]
H A Dahci.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * ahci.h - Common AHCI SATA definitions and declarations
6 * Please ALWAYS copy linux-ide@vger.kernel.org
9 * Copyright 2004-2005 Red Hat, Inc.
12 * as Documentation/driver-api/libata.rst
80 HOST_RESET = BIT(0), /* reset controller; self-clear */
89 HOST_CAP_PART = BIT(13), /* Partial state capable */
90 HOST_CAP_SSC = BIT(14), /* Slumber state capable */
92 HOST_CAP_FBS = BIT(16), /* FIS-based switching support */
98 HOST_CAP_SSS = BIT(27), /* Staggered Spin-up */
[all …]
/linux/Documentation/devicetree/bindings/dma/
H A Dowl-dma.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/dma/owl-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Actions Semi Owl SoCs DMA controller
10 The OWL DMA is a general-purpose direct memory access controller capable of
11 supporting 10 independent DMA channels for the Actions Semi S700 SoC and 12
12 independent DMA channels for the S500 and S900 SoC variants.
15 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
18 - $ref: dma-controller.yaml#
[all …]
H A Dsocionext,uniphier-xdmac.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/socionext,uniphier-xdmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Socionext UniPhier external DMA controller
10 This describes the devicetree bindings for an external DMA engine to perform
11 memory-to-memory or peripheral-to-memory data transfer capable of supporting
15 - Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
18 - $ref: dma-controller.yaml#
22 const: socionext,uniphier-xdmac
[all …]
H A Dmarvell,xor-v2.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/dma/marvell,xor-v2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
15 - const: marvell,xor-v2
16 - items:
17 - enum:
18 - marvell,armada-7k-xor
19 - const: marvell,xor-v2
[all …]
H A Dst_fdma.txt3 The FDMA is a general-purpose direct memory access controller capable of
4 supporting 16 independent DMA channels. It accepts up to 32 DMA requests.
10 - compatible : Should be one of
11 - st,stih407-fdma-mpe31-11, "st,slim-rproc";
12 - st,stih407-fdma-mpe31-12, "st,slim-rproc";
13 - st,stih407-fdma-mpe31-13, "st,slim-rproc";
14 - reg : Should contain an entry for each name in reg-names
15 - reg-names : Must contain "slimcore", "dmem", "peripherals", "imem" entries
16 - interrupts : Should contain one interrupt shared by all channels
17 - dma-channels : Number of channels supported by the controller
[all …]
/linux/arch/xtensa/include/asm/
H A Ddma.h2 * include/asm-xtensa/dma.h
8 * Copyright (C) 2003 - 2005 Tensilica Inc.
17 * This is only to be defined if we have PC-like DMA.
28 * The maximum virtual address to which DMA transfers
31 * NOTE: This is board (platform) specific, not processor-specific!
33 * NOTE: This assumes DMA transfers can only be performed on
36 * means the maximum possible size of this DMA area is
40 * NOTE: When the entire KSEG area is DMA capable, we subtract
48 #define MAX_DMA_ADDRESS (PAGE_OFFSET + XCHAL_KIO_SIZE - 1)
51 /* Reserve and release a DMA channel */
/linux/Documentation/devicetree/bindings/pci/
H A Dbrcm,stb-pcie.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/brcm,stb-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jim Quinlan <james.quinlan@broadcom.com>
15 - enum:
16 - brcm,bcm2711-pcie # The Raspberry Pi 4
17 - brcm,bcm4908-pcie
18 - brcm,bcm7211-pcie # Broadcom STB version of RPi4
19 - brcm,bcm7216-pcie # Broadcom 7216 Arm
[all …]
/linux/drivers/acpi/arm64/
H A Ddma.c1 // SPDX-License-Identifier: GPL-2.0-only
5 #include <linux/dma-direct.h>
14 * If @dev is expected to be DMA-capable then the bus code that created in acpi_arch_dma_setup()
19 if (!dev->dma_mask) { in acpi_arch_dma_setup()
20 dev_warn(dev, "DMA mask not set\n"); in acpi_arch_dma_setup()
21 dev->dma_mask = &dev->coherent_dma_mask; in acpi_arch_dma_setup()
24 if (dev->coherent_dma_mask) in acpi_arch_dma_setup()
25 end = dev->coherent_dma_mask; in acpi_arch_dma_setup()
27 end = (1ULL << 32) - 1; in acpi_arch_dma_setup()
32 dev->dma_range_map = map; in acpi_arch_dma_setup()
[all …]
/linux/include/uapi/linux/
H A Drio_mport_cdev.h1 /* SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) */
3 * Copyright (c) 2015-2016, Integrated Device Technology Inc.
11 * License(GPL) Version 2, or the BSD-3 Clause license below:
57 * - memory mapped (MAPPED)
58 * - packet generation from memory (TRANSFER)
83 __u32 cap_sys_size; /* Capable system sizes */
84 __u32 cap_addr_size; /* Capable addressing sizes */
85 __u32 cap_transfer_mode; /* Capable transfer modes */
91 * - incoming port-writes
92 * - incoming doorbells
[all …]
/linux/Documentation/devicetree/bindings/net/
H A Dti,icssg-prueth.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/ti,icssg-prueth.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Md Danish Anwar <danishanwar@ti.com>
13 Ethernet based on the Programmable Real-Time Unit and Industrial
19 - ti,am642-icssg-prueth # for AM64x SoC family
20 - ti,am654-icssg-prueth # for AM65x SoC family
21 - ti,am654-sr1-icssg-prueth # for AM65x SoC family, SR1.0
32 dma-names:
[all …]
H A Dkeystone-netcp.txt6 switch sub-module to send and receive packets. NetCP also includes a packet
10 capable of performing IPSec operations on ingress/egress packets.
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
24 -----------------------------
26 -----------------------------
[all …]
/linux/Documentation/devicetree/bindings/dma/stm32/
H A Dst,stm32-dma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/stm32/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32 DMA Controller
10 The STM32 DMA is a general-purpose direct memory access controller capable of
11 supporting 8 independent DMA channels. Each channel can have up to 8 requests.
12 DMA clients connected to the STM32 DMA controller must use the format
13 described in the dma.txt file, using a four-cell specifier for each
14 channel: a phandle to the DMA controller plus the following four integer cells:
[all …]
H A Dst,stm32-mdma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/stm32/st,stm32-mdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 MDMA is a general-purpose direct memory access controller capable of
11 supporting 64 independent DMA channels with 256 HW requests.
12 DMA clients connected to the STM32 MDMA controller must use the format
13 described in the dma.txt file, using a five-cell specifier for each channel:
21 3. A 32bit mask specifying the DMA channel configuration
22 -bit 0-1: Source increment mode
[all …]
/linux/Documentation/i2c/
H A Ddma-considerations.rst2 Linux I2C and DMA
5 Given that I2C is a low-speed bus, over which the majority of messages
6 transferred are small, it is not considered a prime user of DMA access. At this
7 time of writing, only 10% of I2C bus master drivers have DMA support
9 DMA for it will likely add more overhead than a plain PIO transfer.
11 Therefore, it is *not* mandatory that the buffer of an I2C message is DMA safe.
13 rarely used. However, it is recommended to use a DMA-safe buffer if your
14 message size is likely applicable for DMA. Most drivers have this threshold
18 I2C bus master driver is using USB as a bridge, then you need to have DMA
22 -------
[all …]
/linux/Documentation/devicetree/bindings/sound/
H A Dnvidia,tegra210-admaif.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/nvidia,tegra210-admaif.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
17 - Jon Hunter <jonathanh@nvidia.com>
18 - Sameer Pujar <spujar@nvidia.com>
22 pattern: "^admaif@[0-9a-f]*$"
26 - enum:
27 - nvidia,tegra210-admaif
28 - nvidia,tegra186-admaif
[all …]
/linux/Documentation/devicetree/bindings/spi/
H A Datmel,at91rm9200-spi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/spi/atmel,at91rm9200-spi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Tudor Ambarus <tudor.ambarus@linaro.org>
14 - $ref: spi-controller.yaml#
19 - const: atmel,at91rm9200-spi
20 - items:
21 - enum:
22 - microchip,sam9x60-spi
[all …]
/linux/drivers/video/fbdev/omap/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
28 Say Y here, if your user-space applications are capable of
34 bool "MIPI DBI-C/DCS compatible LCD support"
38 the Mobile Industry Processor Interface DBI-C/DCS
42 bool "Set DMA SDRAM access priority high"
46 (SDRAM) this will speed up graphics DMA operations.
/linux/drivers/rapidio/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
38 bool "DMA Engine support for RapidIO"
43 Say Y here if you want to use DMA Engine frameork for RapidIO data
46 memory and memory on remote target device. You need a DMA controller
47 capable to perform data transfers to/from RapidIO.
74 provides socket-like interface to allow sharing of single RapidIO
75 messaging mailbox between multiple user-space applications.
76 See "Documentation/driver-api/rapidio/rio_cm.rst" for driver description.
83 allows to user space applications to perform RapidIO-specific
/linux/drivers/xen/
H A Dgntdev-common.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (c) 2006-2007, D G Murray.
30 /* Device for which DMA memory is allocated. */
67 * If dmabuf_vaddr is not NULL then this mapping is backed by DMA
68 * capable memory.
72 /* Flags used to create this DMA buffer: GNTDEV_DMA_FLAG_XXX. */
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
32 2) control domain: xl mem-max <target-domain> <maxmem>
35 3) control domain: xl mem-set <target-domain> <memory>
51 …SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /…
145 bool "Add support for dma-buf grant access device driver extension"
150 dma-buf implementation. With this extension grant references to
151 the pages of an imported dma-buf can be exported for other domain
153 converted into a local dma-buf for local export.
156 tristate "User-space grant reference allocator driver"
162 or as part of an inter-domain shared memory channel.
[all …]
/linux/drivers/vfio/
H A Dvfio_iommu_type1.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * VFIO: IOMMU DMA mapping support for Type1 IOMMU
13 * It could be called the x86 IOMMU as it's designed for AMD-Vi & Intel
14 * VT-d, but that makes it harder to re-use as theoretically anyone
61 "Maximum number of user DMA mappings per container (65535).");
83 bool fgsp : 1; /* Fine-grained super pages */
94 bool lock_cap; /* capable(CAP_IPC_LOCK) */
97 struct rb_root pfn_list; /* Ex-user pinned pfn list */
124 * Guest RAM pinning working set or DMA target
144 * further casts to signed integer for unaligned multi-bit operation,
[all …]
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "VFIO Non-Privileged userspace driver framework"
12 See Documentation/driver-api/vfio.rst for more details.
25 to set up secure DMA context for device access. This interface does
64 bool "VFIO No-IOMMU support"
68 Only with an IOMMU can userspace access to DMA capable devices be
69 considered secure. VFIO No-IOMMU mode enables IOMMU groups for
70 devices without IOMMU backing for the purpose of re-using the VFIO
71 infrastructure in a non-secure mode. Use of this mode will result
74 this mode since there is no IOMMU to provide DMA translation.
[all …]
/linux/Documentation/devicetree/bindings/i2c/
H A Datmel,at91sam-i2c.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/i2c/atmel,at91sam-i2c.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Alexandre Belloni <alexandre.belloni@bootlin.com>
16 - items:
17 - enum:
18 - atmel,at91rm9200-i2c
19 - atmel,at91sam9261-i2c
20 - atmel,at91sam9260-i2c
[all …]

12345678910>>...15