Lines Matching +full:no +full:- +full:memory +full:- +full:wc

1 /* SPDX-License-Identifier: GPL-2.0-only */
83  * Posting") mandate non-posted configuration transactions. There is
84  * no ioremap API in the kernel that can guarantee non-posted write
87  * should override it if they have memory mapping implementations that
88  * guarantee non-posted writes semantics to make the memory mapping
113  * end up write-combining.  This facility should be used in conjunction
114  * with pgprot_writecombine, ioremap-wc, or set_memory_wc, since it has
115  * no effect if the per-page mechanisms are functional.
119  * to have no effect.
136 	return -1;  in arch_phys_wc_index()
143 	/* See memremap() kernel-doc for usage description... */
155  * On x86 PAT systems we have memory tracking that keeps track of
156  * the allowed mappings on memory ranges. This tracking works for
157  * all the in-kernel mapping APIs (ioremap*), but where the user
158  * wishes to map a range from a physical device into user memory
161  * and wants to make sure they are mapped WC and not UC.