Searched refs:mappable (Results 1 – 9 of 9) sorted by relevance
| /linux-2.6.39/drivers/gpu/drm/i915/ |
| D | i915_trace.h | 37 TP_PROTO(struct drm_i915_gem_object *obj, bool mappable),
38 TP_ARGS(obj, mappable),
44 __field(bool, mappable)
51 __entry->mappable = mappable;
56 __entry->mappable ? ", mappable" : "")
194 TP_PROTO(struct drm_device *dev, u32 size, u32 align, bool mappable),
195 TP_ARGS(dev, size, align, mappable),
201 __field(bool, mappable)
208 __entry->mappable = mappable;
213 __entry->mappable ? ", mappable" : "")
|
| D | i915_gem_evict.c | 45 unsigned alignment, bool mappable) in i915_gem_evict_something() argument
55 if (mappable) { in i915_gem_evict_something()
67 trace_i915_gem_evict(dev, min_size, alignment, mappable); in i915_gem_evict_something()
93 if (mappable) in i915_gem_evict_something()
|
| D | i915_gem.c | 2745 bool mappable, fenceable; in i915_gem_object_bind_to_gtt() local
2862 mappable = in i915_gem_object_bind_to_gtt()
2865 obj->map_and_fenceable = mappable && fenceable; in i915_gem_object_bind_to_gtt()
|
| D | i915_drv.h | 1194 unsigned alignment, bool mappable);
|
| /linux-2.6.39/Documentation/block/ |
| D | ioprio.txt | 26 to be more directly mappable to performance, by passing in a wanted data
31 determines how much io bandwidth the process will get, it's directly mappable
|
| /linux-2.6.39/Documentation/fb/ |
| D | metronomefb.txt | 34 mappable frame buffer. It has been tested with tinyx (Xfbdev). It is known
|
| /linux-2.6.39/Documentation/ |
| D | io-mapping.txt | 13 mappable, while 'size' indicates how large a mapping region to
|
| /linux-2.6.39/Documentation/leds/ |
| D | leds-class.txt | 94 There are a number of cases where a trigger might only be mappable to a
|
| /linux-2.6.39/drivers/mtd/maps/ |
| D | Kconfig | 92 prompt "Maximum mappable memory available for flash IO"
|