Home
last modified time | relevance | path

Searched refs:coherent (Results 1 – 97 of 97) sorted by relevance

/linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/
Dicm.c78 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 …]
Dicm.h71 gfp_t gfp_mask, int coherent);
72 void mlx4_free_icm(struct mlx4_dev *dev, struct mlx4_icm *icm, int coherent);
Dmlx4.h266 int coherent; member
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dahci-fsl-qoriq.txt11 - dma-coherent: Enable AHCI coherent DMA operation.
20 dma-coherent;
Dapm-xgene.txt27 - dma-coherent : Present if dma operations are coherent
59 dma-coherent;
74 dma-coherent;
Dsata_highbank.txt14 - dma-coherent : Present if dma operations are coherent
36 dma-coherent;
Dahci-platform.txt28 - dma-coherent : Present if dma operations are coherent
/linux-4.4.14/drivers/infiniband/hw/mthca/
Dmthca_memfree.c88 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 …]
Dmthca_memfree.h69 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.4.14/arch/arm64/mm/
Ddma-mapping.c33 bool coherent) in __get_dma_pgprot() argument
35 if (!coherent || dma_get_attr(DMA_ATTR_WRITE_COMBINE, attrs)) in __get_dma_pgprot()
144 bool coherent = is_device_dma_coherent(dev); in __dma_alloc() local
149 if (!coherent && !gfpflags_allow_blocking(flags)) { in __dma_alloc()
164 if (coherent) in __dma_alloc()
545 bool coherent = is_device_dma_coherent(dev); in __iommu_alloc_attrs() local
546 int ioprot = dma_direction_to_prot(DMA_BIDIRECTIONAL, coherent); in __iommu_alloc_attrs()
563 pgprot_t prot = __get_dma_pgprot(attrs, PAGE_KERNEL, coherent); in __iommu_alloc_attrs()
581 if (coherent) { in __iommu_alloc_attrs()
592 if (coherent) in __iommu_alloc_attrs()
[all …]
/linux-4.4.14/arch/arm64/boot/dts/hisilicon/
Dhip05_hns.dtsi125 dma-coherent;
134 dma-coherent;
141 dma-coherent;
149 dma-coherent;
157 dma-coherent;
165 dma-coherent;
173 dma-coherent;
181 dma-coherent;
189 dma-coherent;
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dhisilicon-pcie.txt21 - dma-coherent: Present if DMA operations are coherent.
33 dma-coherent;
Darm,juno-r1-pcie.txt9 - dma-coherent: The host controller bridges the AXI transactions into PCIe bus
10 in a manner that makes the DMA operations to appear coherent to the CPUs.
Dxgene-pci.txt24 - dma-coherent: Present if dma operations are coherent
49 dma-coherent;
Dxgene-pci-msi.txt65 dma-coherent;
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dapm-xgene-dma.txt21 - dma-coherent : Present if dma operations are coherent
45 dma-coherent;
Darm-pl330.txt13 - dma-coherent : Present if dma operations are coherent
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dcalxeda-xgmac.txt10 - dma-coherent : Present if dma operations are coherent
Dsnps,dwc-qos-ethernet.txt16 - dma-coherent: Present if dma operations are coherent
64 dma-coherent;
Damd-xgbe.txt31 - dma-coherent: Present if dma operations are coherent
Dkeystone-netcp.txt58 - dma-coherent: Present if dma operations are coherent
156 dma-coherent;
Dhisilicon-hns-dsaf.txt48 dma-coherent;
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Damd-ccp.txt11 - dma-coherent: Present if dma operations are coherent
/linux-4.4.14/Documentation/devicetree/bindings/xillybus/
Dxillybus.txt11 - dma-coherent: Present if DMA operations are coherent
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Darm,smmu-v3.txt32 - dma-coherent : Present if DMA operations made by the SMMU (page
34 coherent with the CPU.
56 dma-coherent;
Darm,smmu.txt46 - dma-coherent : Present if page table walks made by the SMMU are
47 cache coherent with the CPU.
/linux-4.4.14/drivers/of/
Ddevice.c89 bool coherent; in of_dma_configure() local
142 coherent = of_dma_is_coherent(np); in of_dma_configure()
144 coherent ? " " : " not "); in of_dma_configure()
150 arch_setup_dma_ops(dev, dma_addr, size, iommu, coherent); in of_dma_configure()
/linux-4.4.14/drivers/crypto/ccp/
Dccp-platform.c32 int coherent; member
128 ccp_platform->coherent = (attr == DEV_DMA_COHERENT); in ccp_platform_probe()
129 if (ccp_platform->coherent) in ccp_platform_probe()
/linux-4.4.14/arch/arm64/boot/dts/apm/
Dapm-shadowcat.dtsi204 dma-coherent;
214 dma-coherent;
224 dma-coherent;
250 dma-coherent;
265 dma-coherent;
Dapm-storm.dtsi540 dma-coherent;
565 dma-coherent;
590 dma-coherent;
615 dma-coherent;
640 dma-coherent;
727 dma-coherent;
742 dma-coherent;
756 dma-coherent;
792 dma-coherent;
819 dma-coherent;
[all …]
/linux-4.4.14/arch/arm64/boot/dts/amd/
Damd-seattle-soc.dtsi68 dma-coherent;
141 dma-coherent;
161 dma-coherent;
/linux-4.4.14/arch/c6x/mm/
DMakefile5 obj-y := init.o dma-coherent.o
/linux-4.4.14/arch/avr32/mm/
DMakefile5 obj-y += init.o clear_page.o copy_page.o dma-coherent.o
/linux-4.4.14/arch/arm/boot/dts/
Decx-common.dtsi40 dma-coherent;
217 dma-coherent;
224 dma-coherent;
Dk2l-netcp.dtsi13 dma-coherent;
141 dma-coherent;
Dk2e-netcp.dtsi13 dma-coherent;
142 dma-coherent;
Dk2hk-netcp.dtsi13 dma-coherent;
159 dma-coherent;
Dk2e.dtsi73 dma-coherent;
Dls1021a.dtsi448 dma-coherent;
477 dma-coherent;
506 dma-coherent;
Dkeystone.dtsi189 dma-coherent;
/linux-4.4.14/drivers/bus/
DKconfig25 Support for PMU events monitoring on the ARM CCI-400 (cache coherent
34 Low level power management driver for CCI400 cache coherent
43 Support for PMU events monitoring on the ARM CCI-500 cache coherent
/linux-4.4.14/drivers/staging/goldfish/
DREADME9 - Use dma coherent memory not kmalloc/__pa for the memory (this is just
/linux-4.4.14/Documentation/usb/
Ddma.txt53 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.4.14/arch/arm64/include/asm/
Ddma-mapping.h51 struct iommu_ops *iommu, bool coherent);
/linux-4.4.14/drivers/base/
DMakefile12 obj-$(CONFIG_HAVE_GENERIC_DMA_COHERENT) += dma-coherent.o
/linux-4.4.14/include/linux/
Ddma-iommu.h35 int dma_direction_to_prot(enum dma_data_direction dir, bool coherent);
Ddma-mapping.h140 bool coherent) { } in arch_setup_dma_ops() argument
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcci.txt2 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
Dl2cc.txt47 - 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.4.14/sound/parisc/
Dharmony.h13 int coherent; member
/linux-4.4.14/Documentation/arm/
Dcluster-pm-race-avoidance.txt39 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.
Dvlocks.txt9 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.4.14/Documentation/DocBook/
Dusb.xml.db97 API-usb-alloc-coherent
98 API-usb-free-coherent
Ddevice-drivers.xml.db436 API-dma-alloc-from-coherent
437 API-dma-release-from-coherent
438 API-dma-mmap-from-coherent
439 API-dmam-alloc-coherent
440 API-dmam-free-coherent
443 API-dmam-declare-coherent-memory
D.device-drivers.xml.cmd2 …vers/dma-buf/reservation.c include/linux/reservation.h drivers/base/dma-coherent.c drivers/base/dm…
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt95 - dma-coherent : Present if DMA operations are coherent.
111 dma-coherent;
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dccf.txt6 that enables the implementation of coherent, multicore systems.
/linux-4.4.14/arch/arm/mm/
Ddma-mapping.c2070 static struct dma_map_ops *arm_get_iommu_dma_map_ops(bool coherent) in arm_get_iommu_dma_map_ops() argument
2072 return coherent ? &iommu_coherent_ops : &iommu_ops; in arm_get_iommu_dma_map_ops()
2125 static struct dma_map_ops *arm_get_dma_map_ops(bool coherent) in arm_get_dma_map_ops() argument
2127 return coherent ? &arm_coherent_dma_ops : &arm_dma_ops; in arm_get_dma_map_ops()
2131 struct iommu_ops *iommu, bool coherent) in arch_setup_dma_ops() argument
2135 dev->archdata.dma_coherent = coherent; in arch_setup_dma_ops()
2137 dma_ops = arm_get_iommu_dma_map_ops(coherent); in arch_setup_dma_ops()
2139 dma_ops = arm_get_dma_map_ops(coherent); in arch_setup_dma_ops()
Dproc-xsc3.S404 orrne r2, r2, #PTE_EXT_COHERENT @ interlock: mask in coherent bit
DKconfig961 to suboptimal I/O performance for drivers using coherent DMA.
1013 provide DMA coherent memory. With the advent of ARMv7, mapping
/linux-4.4.14/Documentation/xtensa/
Datomctl.txt21 For systems without an coherent cache controller, non-MX, we always
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt7 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.4.14/drivers/iommu/
Ddma-iommu.c138 int dma_direction_to_prot(enum dma_data_direction dir, bool coherent) in dma_direction_to_prot() argument
140 int prot = coherent ? IOMMU_CACHE : 0; in dma_direction_to_prot()
Darm-smmu-v3.c2471 bool coherent; in arm_smmu_device_probe() local
2527 coherent = of_dma_is_coherent(smmu->dev->of_node); in arm_smmu_device_probe()
2528 if (coherent) in arm_smmu_device_probe()
2531 if (!!(reg & IDR0_COHACC) != coherent) in arm_smmu_device_probe()
2533 coherent ? "true" : "false"); in arm_smmu_device_probe()
/linux-4.4.14/arch/arm/include/asm/
Ddma-mapping.h128 struct iommu_ops *iommu, bool coherent);
/linux-4.4.14/Documentation/scsi/
Dhptiop.txt90 allocate a free request in host DMA coherent memory.
133 - Allocate a free request in host DMA coherent memory.
DChangeLog.lpfc10 * 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.4.14/arch/arm64/boot/dts/arm/
Djuno-r1.dts156 dma-coherent;
/linux-4.4.14/drivers/staging/lustre/
DREADME.txt46 Enable cluster-global posix file locking coherent across all
/linux-4.4.14/Documentation/device-mapper/
Ddm-log.txt52 provide a cluster-coherent log for shared-storage. Device-mapper mirroring
Dcache.txt86 to be coherent with the origin device, then all reads are served from
/linux-4.4.14/Documentation/
DDMA-API.txt26 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
148 streaming and coherent DMA mask parameters if it is.
499 it's asked for coherent memory for this device.
Dvolatile-considered-harmful.txt89 - Pointers to data structures in coherent memory which might be modified
DDMA-API-HOWTO.txt173 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
943 isn't fully DMA-coherent (i.e. hardware doesn't ensure that data in
Ddma-buf-sharing.txt266 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
Dlocal_ops.txt27 coherent counters in NMI handlers. It is especially useful for tracing purposes
Dcachetlb.txt353 implementation is a nop (and should remain so for all coherent
364 implementation is a nop and should remain so on all coherent
DCodingStyle597 Locking is used to keep data structures coherent, while reference
Dmemory-barriers.txt1752 cache coherent memory writes have completed before attempting a write to
2655 caches are expected to be coherent, there's no guarantee that that coherency
Dkernel-parameters.txt683 Sets the size of memory pool for coherent, atomic dma
/linux-4.4.14/drivers/net/ethernet/amd/xgbe/
Dxgbe-main.c618 pdata->coherent = (attr == DEV_DMA_COHERENT); in xgbe_probe()
619 if (pdata->coherent) { in xgbe_probe()
Dxgbe.h793 unsigned int coherent; member
/linux-4.4.14/Documentation/spi/
Dpxa2xx210 mode supports both coherent and stream based DMA mappings.
223 use coherent DMA mode
/linux-4.4.14/arch/metag/mm/
DKconfig78 kernel takes the appropriate actions to keep the cache coherent.
/linux-4.4.14/Documentation/cpuidle/
Dsysfs.txt89 example, it is not coherent, i.e. if one is disabling a light state,
/linux-4.4.14/Documentation/powerpc/
Dcxl.txt7 The coherent accelerator interface is designed to allow the
8 coherent connection of accelerators (FPGAs and other devices) to a
/linux-4.4.14/Documentation/filesystems/
Dsysv-fs.txt14 -t coherent
Dpath-lookup.txt184 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.4.14/drivers/parisc/
DKconfig25 generation of PA-RISC cache-coherent machines. Programs the
/linux-4.4.14/arch/mips/include/asm/pci/
Dbridge.h812 u64 coherent:1; member
/linux-4.4.14/Documentation/dmaengine/
Dpxa_dma.txt54 Transfers a single u32 to a well known dma coherent memory to leave
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt56 drivers using devres. For example, coherent DMA memory is acquired
/linux-4.4.14/Documentation/PCI/
Dpci.txt47 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.4.14/arch/frv/
DKconfig333 bool "Reserve DMA coherent memory"
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt1383 coherent DMA operations. The "dma-coherent" property is intended to be used
1384 for identifying devices supported coherent DMA operations in DT.
1402 - dma-coherent: Present if dma operations are coherent
1416 dma-coherent;
/linux-4.4.14/arch/arm64/
DKconfig264 to a coherent interconnect.
286 present when it is connected to a coherent interconnect.
/linux-4.4.14/Documentation/arm64/
Dbooting.txt157 coherent masters with caches enabled, this will typically require