| /linux-4.1.27/drivers/net/ethernet/mellanox/mlx4/ |
| D | icm.c | 78 void mlx4_free_icm(struct mlx4_dev *dev, struct mlx4_icm *icm, int coherent) in mlx4_free_icm() argument
86 if (coherent) in mlx4_free_icm()
128 gfp_t gfp_mask, int coherent) in mlx4_alloc_icm() argument
136 BUG_ON(coherent && (gfp_mask & __GFP_HIGHMEM)); in mlx4_alloc_icm()
176 if (coherent) in mlx4_alloc_icm()
194 if (coherent) in mlx4_alloc_icm()
211 if (!coherent && chunk) { in mlx4_alloc_icm()
223 mlx4_free_icm(dev, icm, coherent); in mlx4_alloc_icm()
265 __GFP_NOWARN, table->coherent); in mlx4_table_get()
273 mlx4_free_icm(dev, table->icm[i], table->coherent); in mlx4_table_get()
[all …]
|
| D | icm.h | 71 gfp_t gfp_mask, int coherent);
72 void mlx4_free_icm(struct mlx4_dev *dev, struct mlx4_icm *icm, int coherent);
|
| D | mlx4.h | 264 int coherent; member
|
| /linux-4.1.27/drivers/infiniband/hw/mthca/ |
| D | mthca_memfree.c | 88 void mthca_free_icm(struct mthca_dev *dev, struct mthca_icm *icm, int coherent) in mthca_free_icm() argument
96 if (coherent) in mthca_free_icm()
138 gfp_t gfp_mask, int coherent) in mthca_alloc_icm() argument
146 BUG_ON(coherent && (gfp_mask & __GFP_HIGHMEM)); in mthca_alloc_icm()
173 if (coherent) in mthca_alloc_icm()
184 if (coherent) in mthca_alloc_icm()
206 if (!coherent && chunk) { in mthca_alloc_icm()
218 mthca_free_icm(dev, icm, coherent); in mthca_alloc_icm()
236 __GFP_NOWARN, table->coherent); in mthca_table_get()
244 mthca_free_icm(dev, table->icm[i], table->coherent); in mthca_table_get()
[all …]
|
| D | mthca_memfree.h | 69 int coherent; member
83 gfp_t gfp_mask, int coherent);
84 void mthca_free_icm(struct mthca_dev *dev, struct mthca_icm *icm, int coherent);
|
| /linux-4.1.27/Documentation/devicetree/bindings/ata/ |
| D | apm-xgene.txt | 27 - dma-coherent : Present if dma operations are coherent
59 dma-coherent;
74 dma-coherent;
|
| D | sata_highbank.txt | 14 - dma-coherent : Present if dma operations are coherent
36 dma-coherent;
|
| D | ahci-platform.txt | 28 - dma-coherent : Present if dma operations are coherent
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | apm-xgene-dma.txt | 21 - dma-coherent : Present if dma operations are coherent
45 dma-coherent;
|
| D | arm-pl330.txt | 13 - dma-coherent : Present if dma operations are coherent
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | calxeda-xgmac.txt | 10 - dma-coherent : Present if dma operations are coherent
|
| D | amd-xgbe.txt | 28 - dma-coherent: Present if dma operations are coherent
|
| D | keystone-netcp.txt | 58 - dma-coherent: Present if dma operations are coherent
152 dma-coherent;
|
| /linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
| D | amd-ccp.txt | 11 - dma-coherent: Present if dma operations are coherent
|
| /linux-4.1.27/Documentation/devicetree/bindings/xillybus/ |
| D | xillybus.txt | 11 - dma-coherent: Present if DMA operations are coherent
|
| /linux-4.1.27/drivers/of/ |
| D | device.c | 88 bool coherent; in of_dma_configure() local
141 coherent = of_dma_is_coherent(np); in of_dma_configure()
143 coherent ? " " : " not "); in of_dma_configure()
149 arch_setup_dma_ops(dev, dma_addr, size, iommu, coherent); in of_dma_configure()
|
| /linux-4.1.27/drivers/crypto/ccp/ |
| D | ccp-platform.c | 33 int coherent; member
118 ccp_platform->coherent = !!cca; in ccp_acpi_support()
134 ccp_platform->coherent = of_dma_is_coherent(ccp->dev->of_node); in ccp_of_support()
192 if (ccp_platform->coherent) in ccp_platform_probe()
|
| /linux-4.1.27/Documentation/devicetree/bindings/pci/ |
| D | xgene-pci.txt | 24 - dma-coherent: Present if dma operations are coherent
49 dma-coherent;
|
| /linux-4.1.27/arch/arm64/boot/dts/apm/ |
| D | apm-storm.dtsi | 396 dma-coherent;
419 dma-coherent;
442 dma-coherent;
465 dma-coherent;
488 dma-coherent;
574 dma-coherent;
589 dma-coherent;
603 dma-coherent;
626 dma-coherent;
653 dma-coherent;
[all …]
|
| /linux-4.1.27/arch/arm64/mm/ |
| D | dma-mapping.c | 35 bool coherent) in __get_dma_pgprot() argument
37 if (!coherent || dma_get_attr(DMA_ATTR_WRITE_COMBINE, attrs)) in __get_dma_pgprot()
146 bool coherent = is_device_dma_coherent(dev); in __dma_alloc() local
150 if (!coherent && !(flags & __GFP_WAIT)) { in __dma_alloc()
165 if (coherent) in __dma_alloc()
|
| /linux-4.1.27/arch/arm64/boot/dts/amd/ |
| D | amd-seattle-soc.dtsi | 68 dma-coherent;
141 dma-coherent;
161 dma-coherent;
|
| /linux-4.1.27/arch/c6x/mm/ |
| D | Makefile | 5 obj-y := init.o dma-coherent.o
|
| /linux-4.1.27/arch/arm64/include/asm/ |
| D | dma-mapping.h | 49 struct iommu_ops *iommu, bool coherent) in arch_setup_dma_ops() argument
51 dev->archdata.dma_coherent = coherent; in arch_setup_dma_ops()
|
| /linux-4.1.27/arch/avr32/mm/ |
| D | Makefile | 5 obj-y += init.o clear_page.o copy_page.o dma-coherent.o
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | ecx-common.dtsi | 40 dma-coherent;
217 dma-coherent;
224 dma-coherent;
|
| D | k2e.dtsi | 70 dma-coherent;
|
| D | keystone.dtsi | 188 dma-coherent;
|
| /linux-4.1.27/drivers/staging/goldfish/ |
| D | README | 9 - Use dma coherent memory not kmalloc/__pa for the memory (this is just
|
| /linux-4.1.27/Documentation/usb/ |
| D | dma.txt | 53 to use this type of memory ("dma-coherent"), and memory returned from
56 The memory buffer returned is "dma-coherent"; sometimes you might need to
60 Documentation/DMA-API-HOWTO.txt for definitions of "coherent" and
67 semantics of dma-coherent memory require either bypassing CPU caches
|
| /linux-4.1.27/drivers/base/ |
| D | Makefile | 12 obj-$(CONFIG_HAVE_GENERIC_DMA_COHERENT) += dma-coherent.o
|
| /linux-4.1.27/drivers/net/ethernet/amd/xgbe/ |
| D | xgbe-main.c | 214 pdata->coherent = !!cca; in xgbe_acpi_support()
247 pdata->coherent = of_dma_is_coherent(dev->of_node); in xgbe_of_support()
367 if (pdata->coherent) { in xgbe_probe()
|
| D | xgbe.h | 680 unsigned int coherent; member
|
| /linux-4.1.27/drivers/bus/ |
| D | Kconfig | 21 Support for PMU events monitoring on the ARM CCI cache coherent
31 Low level power management driver for CCI400 cache coherent
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 2 ARM CCI cache coherent interconnect binding description
6 cache coherent interconnect (CCI) that is capable of monitoring bus
23 Description: Describes a CCI cache coherent Interconnect component
|
| D | l2cc.txt | 47 - arm,io-coherent : indicates that the system is operating in an hardware
48 I/O coherent mode. Valid only when the arm,pl310-cache compatible
|
| /linux-4.1.27/arch/arc/plat-arcfpga/ |
| D | Kconfig | 31 It doesn't provide coherent Caches and/or Atomic Ops (LLOCK/SCOND)
|
| /linux-4.1.27/sound/parisc/ |
| D | harmony.h | 13 int coherent; member
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 39 The mechanism presented in this document describes a coherent memory
63 DOWN: The CPU or cluster is not coherent, and is either powered off or
70 UP: The CPU or cluster is active and coherent at the hardware
153 cluster is set up and coherent. If the cluster is not ready,
173 CPU is coherent yet, but it does mean that it is safe to resume
424 executing Linux and hence coherent. Therefore, ordinary spinlocks can
426 non-coherent.
|
| D | vlocks.txt | 9 which are otherwise non-coherent, in situations where the hardware
174 memory unless all CPUs contending the lock are cache-coherent, due
176 CPUs. (Though if all the CPUs are cache-coherent, you should be
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 95 - dma-coherent : Present if DMA operations are coherent.
111 dma-coherent;
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | ccf.txt | 6 that enables the implementation of coherent, multicore systems.
|
| /linux-4.1.27/arch/arm/mm/ |
| D | dma-mapping.c | 2058 static struct dma_map_ops *arm_get_iommu_dma_map_ops(bool coherent) in arm_get_iommu_dma_map_ops() argument
2060 return coherent ? &iommu_coherent_ops : &iommu_ops; in arm_get_iommu_dma_map_ops()
2113 static struct dma_map_ops *arm_get_dma_map_ops(bool coherent) in arm_get_dma_map_ops() argument
2115 return coherent ? &arm_coherent_dma_ops : &arm_dma_ops; in arm_get_dma_map_ops()
2119 struct iommu_ops *iommu, bool coherent) in arch_setup_dma_ops() argument
2123 dev->archdata.dma_coherent = coherent; in arch_setup_dma_ops()
2125 dma_ops = arm_get_iommu_dma_map_ops(coherent); in arch_setup_dma_ops()
2127 dma_ops = arm_get_dma_map_ops(coherent); in arch_setup_dma_ops()
|
| D | proc-xsc3.S | 404 orrne r2, r2, #PTE_EXT_COHERENT @ interlock: mask in coherent bit
|
| D | Kconfig | 952 to suboptimal I/O performance for drivers using coherent DMA.
994 provide DMA coherent memory. With the advent of ARMv7, mapping
|
| /linux-4.1.27/Documentation/xtensa/ |
| D | atomctl.txt | 21 For systems without an coherent cache controller, non-MX, we always
|
| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 7 POHMELFS first began as a network filesystem with coherent local data and
11 * Locally coherent cache for data and metadata with (potentially) byte-range locks.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | hptiop.txt | 90 allocate a free request in host DMA coherent memory.
133 - Allocate a free request in host DMA coherent memory.
|
| D | ChangeLog.lpfc | 10 * Removed pci dma sync calls to coherent/consistent pci memory.
528 pci_dma_sync_* on coherent memory. pci_dma_sync_* is need and
530 coherent mappings. Note: There are more consistent mappings
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-log.txt | 52 provide a cluster-coherent log for shared-storage. Device-mapper mirroring
|
| D | cache.txt | 86 to be coherent with the origin device, then all reads are served from
|
| /linux-4.1.27/drivers/staging/lustre/ |
| D | README.txt | 48 Enable cluster-global posix file locking coherent across all
|
| /linux-4.1.27/arch/arm/include/asm/ |
| D | dma-mapping.h | 126 struct iommu_ops *iommu, bool coherent);
|
| /linux-4.1.27/Documentation/ |
| D | DMA-API.txt | 26 Part Ia - Using large DMA-coherent buffers
78 Part Ib - Using small DMA-coherent buffers
83 Many drivers need lots of small DMA-coherent memory regions for DMA
86 much like a struct kmem_cache, except that they use the DMA-coherent allocator,
95 dma_pool_create() initializes a pool of DMA-coherent buffers
154 streaming and coherent DMA mask parameters if it is.
505 it's asked for coherent memory for this device.
|
| D | volatile-considered-harmful.txt | 89 - Pointers to data structures in coherent memory which might be modified
|
| D | DMA-API-HOWTO.txt | 173 which will query the mask for both streaming and coherent APIs together.
257 The coherent mask will always be able to set the same or a smaller mask as
321 Think of "consistent" as "synchronous" or "coherent".
376 Also, systems with caches that aren't DMA-coherent will work better
938 isn't fully DMA-coherent (i.e. hardware doesn't ensure that data in
|
| D | dma-buf-sharing.txt | 266 coherent for the given range and access direction. The range and access
389 Because existing importing subsystems might presume coherent mappings for
390 userspace, the exporter needs to set up a coherent mapping. If that's not
|
| D | local_ops.txt | 27 coherent counters in NMI handlers. It is especially useful for tracing purposes
|
| D | cachetlb.txt | 353 implementation is a nop (and should remain so for all coherent
364 implementation is a nop and should remain so on all coherent
|
| D | CodingStyle | 597 Locking is used to keep data structures coherent, while reference
|
| D | memory-barriers.txt | 1733 cache coherent memory writes have completed before attempting a write to
2700 caches are expected to be coherent, there's no guarantee that that coherency
|
| D | kernel-parameters.txt | 676 Sets the size of memory pool for coherent, atomic dma
|
| /linux-4.1.27/Documentation/spi/ |
| D | pxa2xx | 216 mode supports both coherent and stream based DMA mappings.
229 use coherent DMA mode
|
| /linux-4.1.27/arch/metag/mm/ |
| D | Kconfig | 78 kernel takes the appropriate actions to keep the cache coherent.
|
| /linux-4.1.27/Documentation/cpuidle/ |
| D | sysfs.txt | 89 example, it is not coherent, i.e. if one is disabling a light state,
|
| /linux-4.1.27/Documentation/DocBook/ |
| D | .device-drivers.xml.cmd | 2 …vers/dma-buf/reservation.c include/linux/reservation.h drivers/base/dma-coherent.c drivers/base/dm…
|
| /linux-4.1.27/include/linux/ |
| D | dma-mapping.h | 139 bool coherent) { } in arch_setup_dma_ops() argument
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | cxl.txt | 7 The coherent accelerator interface is designed to allow the
8 coherent connection of accelerators (FPGAs and other devices) to a
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | sysv-fs.txt | 14 -t coherent
|
| D | path-lookup.txt | 184 dentry seqlock (d_seq) is used to take a "coherent snapshot" of what the dentry
186 the next part of the path walk. When loading the coherent snapshot under d_seq,
|
| /linux-4.1.27/arch/mips/include/asm/pci/ |
| D | bridge.h | 812 u64 coherent:1; member
|
| /linux-4.1.27/drivers/parisc/ |
| D | Kconfig | 25 generation of PA-RISC cache-coherent machines. Programs the
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | devres.txt | 56 drivers using devres. For example, coherent DMA memory is acquired
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 47 Set the DMA mask size (for both coherent and streaming DMA)
59 Release DMA buffers (both streaming and coherent)
243 Set the DMA mask size (for both coherent and streaming DMA)
|
| /linux-4.1.27/arch/frv/ |
| D | Kconfig | 333 bool "Reserve DMA coherent memory"
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig | 340 to a coherent interconnect.
362 present when it is connected to a coherent interconnect.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 1379 coherent DMA operations. The "dma-coherent" property is intended to be used
1380 for identifying devices supported coherent DMA operations in DT.
1398 - dma-coherent: Present if dma operations are coherent
1412 dma-coherent;
|
| /linux-4.1.27/Documentation/arm64/ |
| D | booting.txt | 147 coherent masters with caches enabled, this will typically require
|