Lines Matching refs:I915_MEMORY_CLASS_DEVICE

1087  *	  contain I915_MEMORY_CLASS_DEVICE then the object will be allocated and
1268 	 * alignment restrictions with I915_MEMORY_CLASS_DEVICE, on devices with
1664  *       contain I915_MEMORY_CLASS_DEVICE then the object will be allocated and
3432 	/** @I915_MEMORY_CLASS_DEVICE: Device local-memory */
3433 	I915_MEMORY_CLASS_DEVICE,
3478 	 * for I915_MEMORY_CLASS_DEVICE regions (for other types the value here
3500 			 * I915_MEMORY_CLASS_DEVICE regions (for other types the
3520 			 * I915_MEMORY_CLASS_DEVICE regions (for other types the
3527 			 * currently tracked for I915_MEMORY_CLASS_DEVICE
3637 	 * pages for I915_MEMORY_CLASS_DEVICE. The kernel also requires a
3673 	 * Only valid when placing objects in I915_MEMORY_CLASS_DEVICE, and only
3685 	 * I915_MEMORY_CLASS_DEVICE.
3688 	 * that can *only* be placed in I915_MEMORY_CLASS_DEVICE, we therefore
3693 	 * I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the
3703 	 * entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as
3752  *              .memory_class = I915_MEMORY_CLASS_DEVICE,
3779  * in I915_MEMORY_CLASS_DEVICE. When such objects (compressed) have other
3781  * constraints) to the non I915_MEMORY_CLASS_DEVICE region, then i915 needs to
3786  * I915_MEMORY_CLASS_DEVICE regions.