[PATCH 3/3] drm/radeon: uvd/vce properly pin/unpin firmware accross suspend/resume.

2016-03-16 Thread jgli...@redhat.com
From: Jérome Glisse <jgli...@redhat.com> We need to unpin on suspend and pin on resume. This shuffle code around to do just that. Signed-off-by: Jérôme Glisse Cc: Alex Deucher Cc: Christian König --- drivers/gpu/drm/radeon/radeon_uvd.c | 61 - d

[PATCH 2/3] drm/radeon: add driver option to disable uvd/vce block.

2016-03-16 Thread jgli...@redhat.com
From: Jérome Glisse <jgli...@redhat.com> Quite few suspend/hibernation bugs are related to this block. Add an option to disable those as a work around. Signed-off-by: Jérôme Glisse Cc: Alex Deucher Cc: Christian König --- drivers/gpu/drm/radeon/radeon.h | 1 + drivers/gpu/drm/

[PATCH 1/3] drm/radeon: fix indentation.

2016-03-16 Thread jgli...@redhat.com
From: Jérome Glisse <jgli...@redhat.com> I hate doing this but it hurts my eyes to go over code that does not comply with indentation rules. Only thing that is not only space change is in atom.c all other files are space indentation issues. Signed-off-by: Jérôme Glisse Cc: Alex D

[PATCH 6/6] drm/amdgpu: Use swiotlb_in_use() to know if swiotlb is enabled.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> We can not rely on swiotlb_nr_tbl() to know if swiotlb is in use or not for our device. Use the new helper to determine that. Signed-off-by: Jérôme Glisse Cc: Konrad Rzeszutek Wilk Cc: Alex Deucher Cc: Ben Skeggs Cc: Dave Airlie Cc

[PATCH 5/6] drm/i915: Use swiotlb_in_use() to know if swiotlb is enabled.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> We can not rely on swiotlb_nr_tbl() to know if swiotlb is in use or not for our device. Use the new helper to determine that. Signed-off-by: Jérôme Glisse Cc: Konrad Rzeszutek Wilk Cc: Alex Deucher Cc: Ben Skeggs Cc: Dave Airlie Cc

[PATCH 4/6] drm/vmwgfx: Use swiotlb_in_use() to know if swiotlb is enabled.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> We can not rely on swiotlb_nr_tbl() to know if swiotlb is in use or not for our device. Use the new helper to determine that. Signed-off-by: Jérôme Glisse Cc: Konrad Rzeszutek Wilk Cc: Alex Deucher Cc: Ben Skeggs Cc: Dave Airlie Cc

[PATCH 3/6] drm/nouveau: Use swiotlb_in_use() to know if swiotlb is enabled or not.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> We can not rely on swiotlb_nr_tbl() to know if swiotlb is in use or not for our device. Use the new helper to determine that. Signed-off-by: Jérôme Glisse Cc: Konrad Rzeszutek Wilk Cc: Alex Deucher Cc: Ben Skeggs Cc: Dave Airlie Cc

[PATCH 2/6] drm/radeon: Use swiotlb_in_use() to know if swiotlb is enabled or not.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> We can not rely on swiotlb_nr_tbl() to know if swiotlb is in use or not for our device. Use the new helper to determine that. Signed-off-by: Jérôme Glisse Cc: Konrad Rzeszutek Wilk Cc: Alex Deucher Cc: Ben Skeggs Cc: Dave Airlie Cc

[PATCH 1/6] swiotlb: Add helper to know if it is in use for a specific device.

2015-08-26 Thread jgli...@redhat.com
From: Jérôme Glisse <jgli...@redhat.com> Some device like GPU do things differently if swiotlb is in use. We use to rely on swiotlb_nr_tbl() to know if swiotlb was enabled or not but this is unreliable. Patch add a simple helpers to check if any of the dma_ops associated with a device

[PATCH 0/6] Properly detect swiotlb.

2015-08-26 Thread jgli...@redhat.com
So this is only build tested as i am away from hardware right now. Idea is to provide reliable way to check if swiotlb is in use for a device or not. It seems swiotlb_nr_tbl() is no longer reliable for that. Please test. Cheers, Jérôme Glisse

[PATCH] radeon/kms: fix dp displayport mode validation

2011-01-26 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Check if there is a big enough dp clock & enough dp lane to drive the video mode provided. Signed-off-by: Jerome Glisse Cc: --- drivers/gpu/drm/radeon/atombios_dp.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/d

[PATCH] drm/radeon/kms: forbid big bo allocation (fdo 31708) v4

2010-12-09 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Forbid allocating buffer bigger than visible VRAM or GTT, also properly set lpfn field. v2 - use max macro - silence warning v3 - don't explicitly set range limit - use min macro v4 - use max btw GTT & VRAM size Cc: stable Signed-off-

[PATCH] drm/radeon/kms: forbid big bo allocation (fdo 31708) v3

2010-12-03 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Forbid allocating buffer bigger than visible VRAM or GTT, also properly set lpfn field. v2 - use max macro - silence warning v3 - don't explicitly set range limit - use min macro Cc: stable Signed-off-by: Jerome Glisse --- drivers/g

[PATCH] drm/radeon/kms: forbid big bo allocation (fdo 31708) v2

2010-11-19 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Forbid allocating buffer bigger than visible VRAM or GTT, also properly set lpfn field. v2 - use max macro - silence warning Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_object.c | 34 ++- 1

[PATCH] drm/radeon/kms: forbid big bo allocation (fdo 31708)

2010-11-19 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Forbid allocating buffer bigger than visible VRAM or GTT, also properly set lpfn field. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_object.c | 36 ++- 1 files changed, 30 insertions(+), 6 del

[PATCH] drm/radeon/kms: forbid allocating bo bigger than VRAM or GTT (fdo 31708)

2010-11-18 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> Forbid allocating buffer bigger than VRAM or GTT, also properly set lpfn field of placement if VRAM is too small. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h|2 +- drivers/gpu/drm/radeon/radeon_object.c

[PATCH] drm/radeon/kms: r6xx/r7xx flush shader cache at fence emision V2

2010-08-27 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> GPU is prone to lockup if we deallocate shader bo right after submitting command using the shader. Force shader cache flush after each batch submission seems to fix the issue. It could fix some of the lockup people were experiencing. V2 move shader

[PATCH] drm/radeon/kms: r6xx/r7xx flush shader cache at fence emision

2010-08-27 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> GPU is prone to lockup if we deallocate shader bo right after submitting command using the shader. Force shader cache flush after each batch submission seems to fix the issue. It could fix some of the lockup people were experiencing. Signed-off-by:

[PATCH] drm/radeon/kms: fix GTT/VRAM overlapping test

2010-08-16 Thread jgli...@redhat.com
From: Jerome Glisse <jgli...@redhat.com> GTT/VRAM overlapping test had a typo which leaded to not detecting case when vram_end > gtt_end. This patch fix the logic and should fix #16574 cc: stable Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_device.c |2 +-