[PATCH v2] drm/prime: fix drm_prime_gem_destroy comment

2025-03-26 Thread Chris Bainbridge
: Chris Bainbridge Suggested-by: Christian König --- drivers/gpu/drm/drm_prime.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index 32a8781cfd67..452d5c7cd292 100644 --- a/drivers/gpu/drm/drm_prime.c +++ b

[PATCH] drm/nouveau: prime: drm_prime_gem_destroy comment

2025-03-26 Thread Chris Bainbridge
: Chris Bainbridge Suggested-by: Christian König --- drivers/gpu/drm/drm_prime.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index 32a8781cfd67..452d5c7cd292 100644 --- a/drivers/gpu/drm/drm_prime.c +++ b

[PATCH v3] drm/nouveau: prime: fix ttm_bo_delayed_delete oops

2025-03-26 Thread Chris Bainbridge
ete. Signed-off-by: Chris Bainbridge Suggested-by: Christian König Fixes: 22b33e8ed0e3 ("22b33e8ed0e3nouveau: add PRIME support") Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3937 Cc: --- drivers/gpu/drm/nouveau/nouveau_bo.c | 3 +++ drivers/gpu/drm/nouveau/nouveau_gem.c |

[BUG] drm_connector reference counting and USB-C docks

2025-03-23 Thread Chris Bainbridge
There is a reference couting / lifecycle issue with drm_connector when used with a USB-C dock. The problem has been previously reproduced on both Intel and AMD GPUs. On both Intel and AMD, the symptoms are: - multiple connectors being listed in sysfs `sys/class/drm/cardX/` (because the old

[PATCH v2] drm/nouveau: prime: fix ttm_bo_delayed_delete oops

2025-03-19 Thread Chris Bainbridge
ete. Signed-off-by: Chris Bainbridge Co-Developed-by: Christian König Fixes: https://gitlab.freedesktop.org/drm/amd/-/issues/3937 --- drivers/gpu/drm/drm_prime.c | 8 ++-- drivers/gpu/drm/nouveau/nouveau_bo.c | 3 +++ drivers/gpu/drm/nouveau/nouveau_gem.c | 3 --- 3 files chang

[PATCH] drm/nouveau: prime: fix ttm_bo_delayed_delete oops

2025-03-12 Thread Chris Bainbridge
ete. Signed-off-by: Chris Bainbridge Co-Developed-by: Christian König Link: https://gitlab.freedesktop.org/drm/amd/-/issues/3937 --- drivers/gpu/drm/drm_prime.c | 8 ++-- drivers/gpu/drm/nouveau/nouveau_bo.c | 3 +++ drivers/gpu/drm/nouveau/nouveau_gem.c | 3 --- 3 files chang

[BUG,BISECTED] WARNING dcn20_find_secondary_pipe

2025-01-26 Thread Chris Bainbridge
Hardware is HP Pavilion Aero 13 laptop with Dell WD19 dock and three external monitors. I get a warning with recent kernel builds when enabling the external monitors with xrandr after initial boot: 16:57:49 kernel: WARNING: CPU: 4 PID: 1347 at drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn

Re: [PATCH v2] drm/client: Detect when ACPI lid is closed during initialization

2024-06-05 Thread Chris Bainbridge
On Tue, Jun 04, 2024 at 10:02:29AM +0800, kernel test robot wrote: > Hi Mario, > > kernel test robot noticed the following build errors: > > [auto build test ERROR on drm-misc/drm-misc-next] > [also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next > drm-intel/for-linux-next drm-intel/

Re: [PATCH] drm/client: Detect when ACPI lid is closed during initialization

2024-05-27 Thread Chris Bainbridge
I > lid status and if it's closed disable any eDP connectors. > > Suggested-by: Alex Deucher > Reported-by: Chris Bainbridge > Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3349 > Signed-off-by: Mario Limonciello > --- > drivers/gpu/drm/drm_client_modeset.c

Re: 6.10/regression/bisected commit c4cb23111103 causes sleeping function called from invalid context at kernel/locking/mutex.c:585

2024-05-22 Thread Chris Bainbridge
On Tue, May 21, 2024 at 02:39:06PM +0500, Mikhail Gavrilov wrote: > Hi, > Yesterday on the fresh kernel snapshot > I spotted a new bug message with follow stacktrace: > [4.307097] BUG: sleeping function called from invalid context at > kernel/locking/mutex.c:585 > [4.307135] in_atomic(): 1,

Re: [PATCH v2] drm: use mgr->dev in drm_dbg_kms in drm_dp_add_payload_part2

2024-04-28 Thread Chris Bainbridge
On Tue, Jun 20, 2023 at 03:59:24PM -0400, Lyude Paul wrote: > Also since I forgot, so patchwork picks this up: > > Reviewed-by: Lyude Paul > > On Tue, 2023-06-20 at 15:50 -0400, Lyude Paul wrote: > > Eek - this might have been a situation where everyone involved assumed > > someone > > else wou

[PATCH v4] Fix divide-by-zero regression on DP MST unplug with nouveau

2024-03-16 Thread Chris Bainbridge
-[ end trace ]--- Fix this by avoiding the divide if bpp is 0. Fixes: c1d6a22b7219 ("drm/dp: Add helpers to calculate the link BW overhead") Cc: sta...@vger.kernel.org Acked-by: Imre Deak Signed-off-by: Chris Bainbridge --- drivers/gpu/drm/display/drm_dp_helper.c | 7

[PATCH v3] Fix divide-by-zero regression on DP MST unplug with nouveau

2024-03-13 Thread Chris Bainbridge
-[ end trace ]--- Fix this by avoiding the divide if bpp is 0. Fixes: c1d6a22b7219 ("drm/dp: Add helpers to calculate the link BW overhead") Cc: sta...@vger.kernel.org Acked-by: Imre Deak Signed-off-by: Chris Bainbridge --- drivers/gpu/drm/display/drm_dp_helper.c | 6 +++

[PATCH v2] Fix divide-by-zero regression on DP MST unplug with nouveau

2024-03-11 Thread Chris Bainbridge
-[ end trace ]--- Fix this by avoiding the divide if bpp is 0. Fixes: c1d6a22b7219 ("drm/dp: Add helpers to calculate the link BW overhead") Signed-off-by: Chris Bainbridge Acked-by: Imre Deak --- drivers/gpu/drm/display/drm_dp_helper.c | 7 +++ 1 file changed, 7 ins

[PATCH] Fix divide-by-zero on DP unplug with nouveau

2024-02-11 Thread Chris Bainbridge
p: Add helpers to calculate the link BW overhead") Signed-off-by: Chris Bainbridge --- drivers/gpu/drm/display/drm_dp_helper.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c index b1ca3a1100da..bb8794c8f99

4.4-rc, intel dri i915, regular hangs and corruptions

2015-12-29 Thread Chris Bainbridge
On 17 December 2015 at 18:34, Norbert Preining wrote: > * font corruption > sometime sets of glyphs, or practically all glyphs disappear > related probably to bug > https://bugs.freedesktop.org/show_bug.cgi?id=55500 > I have sent some info there already, without response > > Currently my