public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com,
	maarten.lankhorst@linux.intel.com
Subject: [PATCH 0/2] drm/i915: move fence timeout to parent interface
Date: Wed,  8 Apr 2026 18:21:47 +0300	[thread overview]
Message-ID: <cover.1775661609.git.jani.nikula@intel.com> (raw)

This is not really something I like to do, but I'm not sure how to make
forward progress otherwise. This removes one of the few remaining direct
display to i915 or xe calls, and we can reconsider this later.

Jani Nikula (2):
  drm/i915: convert i915_fence_timeout() into a proper function
  drm/i915: move fence timeout to display parent interface

 drivers/gpu/drm/i915/display/intel_display.c     |  8 ++++++--
 drivers/gpu/drm/i915/display/intel_parent.c      |  6 ++++++
 drivers/gpu/drm/i915/display/intel_parent.h      |  3 ++-
 drivers/gpu/drm/i915/i915_config.c               |  5 +++++
 drivers/gpu/drm/i915/i915_config.h               |  7 +------
 drivers/gpu/drm/i915/i915_driver.c               |  2 ++
 .../gpu/drm/xe/compat-i915-headers/i915_config.h | 16 ----------------
 include/drm/intel/display_parent_interface.h     |  3 +++
 8 files changed, 25 insertions(+), 25 deletions(-)
 delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_config.h

-- 
2.47.3


             reply	other threads:[~2026-04-08 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 15:21 Jani Nikula [this message]
2026-04-08 15:21 ` [PATCH 1/2] drm/i915: convert i915_fence_timeout() into a proper function Jani Nikula
2026-04-08 15:21 ` [PATCH 2/2] drm/i915: move fence timeout to display parent interface Jani Nikula
2026-04-08 15:51   ` Maarten Lankhorst
2026-04-08 15:28 ` ✗ CI.checkpatch: warning for drm/i915: move fence timeout to " Patchwork
2026-04-08 15:29 ` ✗ CI.KUnit: failure " Patchwork

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=cover.1775661609.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --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