Searched refs:coherent (Results 1 – 11 of 11) sorted by relevance
140 dma-coherent;152 dma-coherent;163 dma-coherent;186 dma-coherent;
66 dma-coherent;77 dma-coherent;
242 * The base address of the coherent memory section must be page-aligned (4K)243 * to guarantee that the coherent data are stored on their own pages and245 * memory attributes for the coherent data page tables.250 * Bakery locks are stored in coherent memory
151 sc_bool_t grant, sc_bool_t coherent);
7 T194 has eight NVIDIA Carmel CPU cores in a coherent multi-processor23 in a coherent multiprocessor configuration. The Denver 2 and Cortex-A57 cores
33 sc_bool_t grant, sc_bool_t coherent) in sc_rm_partition_alloc() argument45 RPC_U8(&msg, 4U) = (uint8_t)coherent; in sc_rm_partition_alloc()
1593 - The coherent memory section (if enabled) must be zero-initialised as well.2009 Use of coherent memory in TF-A2020 is the smallest possible size of the coherent memory region.2023 mismatched attributes from various CPUs are allocated in a coherent memory2024 region (refer to section 2.1 of :ref:`Porting Guide`). The coherent memory2036 Disabling the use of coherent memory in TF-A2039 It might be desirable to avoid the cost of allocating coherent memory on2040 platforms which are memory constrained. TF-A enables inclusion of coherent2088 them from coherent memory involves only doing a clean and invalidate of the2209 Non Functional Impact of removing coherent memory[all …]
86 This flag determines whether to include the coherent memory region in the
1628 - ti: k3: drivers: ti_sci: Put sequence number in coherent memory and1908 - ti/k3: common: Add support for J721E, Use coherent memory for shared data, Trap all3784 - The bakery lock structure for coherent memory has been optimised.3949 memory as coherent. The build flag ``USE_COHERENT_MEM`` can be used to3954 coherent memory has been added.3956 - Memory which was previously marked as coherent is now kept coherent4111 - Removed coherent stacks from the codebase. Stacks allocated in normal4277 - Updated BL1 and BL2 to use a single coherent stack each, rather than one
585 sections of BL31 (.bss, stacks, page tables, and coherent memory) to be674 - ``USE_COHERENT_MEM``: This flag determines whether to include the coherent
68 page boundary (4K) for each BL stage. All sections which allocate coherent506 the platform decides not to use the coherent memory section by undefining the
Completed in 29 milliseconds