From: Jani Nikula <jani.nikula@intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Maarten Lankhorst" <dev@lankhorst.se>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: [PATCH v2] drm/i915/display: stop using the configurable fence timeout
Date: Thu, 13 Nov 2025 17:53:32 +0200 [thread overview]
Message-ID: <20251113155332.789554-1-jani.nikula@intel.com> (raw)
In-Reply-To: <20251112155612.8320-1-jani.nikula@intel.com>
i915 has the Kconfig option DRM_I915_FENCE_TIMEOUT, defaulting to 10
seconds. xe doesn't use it, instead defaulting to
MAX_SCHEDULE_TIMEOUT. Unify the behaviour by switching to
dma_fence_wait() which defaults to MAX_SCHEDULE_TIMEOUT.
As dma_fence_wait() returns 0 when the fence was signaled, update the
return value check.
v2: Use dma_fence_wait(), fix return value check (Maarten)
Reviewed-by: Maarten Lankhorst <dev@lankhorst.se>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
I am not sure about all the implications here. I'm just wondering if we
need to go through all the trouble of adding an interface to query this
from the parent driver.
---
drivers/gpu/drm/i915/display/intel_display.c | 7 ++-----
| 19 -------------------
2 files changed, 2 insertions(+), 24 deletions(-)
delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_config.h
diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
index 069967114bd9..18d2f326d7f4 100644
--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -49,7 +49,6 @@
#include "g4x_dp.h"
#include "g4x_hdmi.h"
#include "hsw_ips.h"
-#include "i915_config.h"
#include "i915_drv.h"
#include "i915_reg.h"
#include "i9xx_plane.h"
@@ -7160,7 +7159,6 @@ static void skl_commit_modeset_enables(struct intel_atomic_state *state)
static void intel_atomic_commit_fence_wait(struct intel_atomic_state *intel_state)
{
- struct drm_i915_private *i915 = to_i915(intel_state->base.dev);
struct drm_plane *plane;
struct drm_plane_state *new_plane_state;
long ret;
@@ -7168,9 +7166,8 @@ static void intel_atomic_commit_fence_wait(struct intel_atomic_state *intel_stat
for_each_new_plane_in_state(&intel_state->base, plane, new_plane_state, i) {
if (new_plane_state->fence) {
- ret = dma_fence_wait_timeout(new_plane_state->fence, false,
- i915_fence_timeout(i915));
- if (ret <= 0)
+ ret = dma_fence_wait(new_plane_state->fence, false);
+ if (ret < 0)
break;
dma_fence_put(new_plane_state->fence);
diff --git a/drivers/gpu/drm/xe/compat-i915-headers/i915_config.h b/drivers/gpu/drm/xe/compat-i915-headers/i915_config.h
deleted file mode 100644
index e835bea08d1b..000000000000
--- a/drivers/gpu/drm/xe/compat-i915-headers/i915_config.h
+++ /dev/null
@@ -1,19 +0,0 @@
-/* SPDX-License-Identifier: MIT */
-/*
- * Copyright © 2023 Intel Corporation
- */
-
-#ifndef __I915_CONFIG_H__
-#define __I915_CONFIG_H__
-
-#include <linux/sched.h>
-
-struct drm_i915_private;
-
-static inline unsigned long
-i915_fence_timeout(const struct drm_i915_private *i915)
-{
- return MAX_SCHEDULE_TIMEOUT;
-}
-
-#endif /* __I915_CONFIG_H__ */
--
2.47.3
next prev parent reply other threads:[~2025-11-13 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 15:56 [PATCH] drm/i915/display: stop using the configurable fence timeout Jani Nikula
2025-11-12 20:39 ` ✓ i915.CI.BAT: success for " Patchwork
2025-11-12 22:54 ` ✗ i915.CI.Full: failure " Patchwork
2025-11-13 10:08 ` [PATCH] " Maarten Lankhorst
2025-11-13 15:53 ` Jani Nikula [this message]
2025-11-13 23:24 ` ✓ i915.CI.BAT: success for drm/i915/display: stop using the configurable fence timeout (rev2) Patchwork
2025-11-14 7:53 ` ✗ i915.CI.Full: failure " Patchwork
2025-11-25 13:55 ` Jani Nikula
2025-11-25 17:24 ` Ville Syrjälä
2025-12-03 10:48 ` Maarten Lankhorst
2026-04-02 9:40 ` Jani Nikula
2026-04-02 15:41 ` Maarten Lankhorst
2026-04-08 15:14 ` Jani Nikula
2026-04-08 15:49 ` Maarten Lankhorst
2026-04-08 16:10 ` Jani Nikula
2026-04-08 16:47 ` Ville Syrjälä
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251113155332.789554-1-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox