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

1 /* SPDX-License-Identifier: GPL-2.0-only */
88  * Posting") mandate non-posted configuration transactions. This default
92  * support non-posted accesses should implement ioremap_np() instead, which
118  * end up write-combining.  This facility should be used in conjunction
119  * with pgprot_writecombine, ioremap-wc, or set_memory_wc, since it has
120  * no effect if the per-page mechanisms are functional.
124  * to have no effect.
141 	return -1;  in arch_phys_wc_index()
150 	/* See memremap() kernel-doc for usage description... */
162  * On x86 PAT systems we have memory tracking that keeps track of
163  * the allowed mappings on memory ranges. This tracking works for
164  * all the in-kernel mapping APIs (ioremap*), but where the user
165  * wishes to map a range from a physical device into user memory
168  * and wants to make sure they are mapped WC and not UC.