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

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