[Intel-gfx] [PATCH 2/2] drm/i915: use devm_request_mem_region_ram() for i915 stolen reservations
Jesse Barnes
jbarnes at virtuousgeek.org
Tue Jul 23 20:42:58 CEST 2013
Since this is actual RAM space we can clobber any padding intended to
prevent MMIO allocations in this space.
Signed-off-by: Jesse Barnes <jbarnes at virtuousgeek.org>
---
drivers/gpu/drm/i915/i915_gem_stolen.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c
index 5c1a535..e057649 100644
--- a/drivers/gpu/drm/i915/i915_gem_stolen.c
+++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
@@ -97,8 +97,9 @@ static unsigned long i915_stolen_to_physical(struct drm_device *dev)
* kernel. So if the region is already marked as busy, something
* is seriously wrong.
*/
- r = devm_request_mem_region(dev->dev, base, dev_priv->gtt.stolen_size,
- "Graphics Stolen Memory");
+ r = devm_request_mem_region_ram(dev->dev, base,
+ dev_priv->gtt.stolen_size,
+ "Graphics Stolen Memory");
if (r == NULL) {
DRM_ERROR("conflict detected with stolen region: [0x%08x - 0x%08x]\n",
base, base + (uint32_t)dev_priv->gtt.stolen_size);
--
1.7.9.5
More information about the Intel-gfx
mailing list