intel-gfx.lists.freedesktop.org archive mirror
 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
Subject: [PATCH 0/7] drm/i915 & drm/xe: prep work towards opaque struct intel_display
Date: Fri, 16 May 2025 15:16:53 +0300	[thread overview]
Message-ID: <cover.1747397638.git.jani.nikula@intel.com> (raw)

This is more prep work towards making struct intel_display and thus
i915->display and xe->display pointers opaque in the i915 and xe driver
cores.

I've included and rebased a couple of fixes from Haoxiang Li that had
unfortunately fallen between the cracks, and would conflict even more
after this.

BR,
Jani.


Haoxiang Li (2):
  drm/i915/display: Add check for alloc_ordered_workqueue() and
    alloc_workqueue()
  drm/xe/display: Add check for alloc_ordered_workqueue()

Jani Nikula (5):
  drm/xe/display: drop duplicate display->fb_tracking.lock init
  drm/i915/display: move hotplug.dp_wq init from xe and i915 to display
  drm/xe/display: move xe->display initialization to xe_display_probe()
  drm/xe/display: add notes about how early a few functions can be
    called
  drm/xe/display: use xe->display to decide whether to do anything

 .../drm/i915/display/intel_display_driver.c   | 39 +++++++-
 drivers/gpu/drm/i915/i915_driver.c            | 13 +--
 drivers/gpu/drm/xe/display/xe_display.c       | 91 ++++++++-----------
 drivers/gpu/drm/xe/display/xe_display.h       |  4 -
 drivers/gpu/drm/xe/xe_device.c                |  4 -
 5 files changed, 73 insertions(+), 78 deletions(-)

-- 
2.39.5


             reply	other threads:[~2025-05-16 12:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 12:16 Jani Nikula [this message]
2025-05-16 12:16 ` [PATCH 1/7] drm/i915/display: Add check for alloc_ordered_workqueue() and alloc_workqueue() Jani Nikula
2025-05-16 14:04   ` Matthew Auld
2025-05-20 18:10     ` Jani Nikula
2025-05-16 12:16 ` [PATCH 2/7] drm/xe/display: Add check for alloc_ordered_workqueue() Jani Nikula
2025-05-16 14:05   ` Matthew Auld
2025-05-16 12:16 ` [PATCH 3/7] drm/xe/display: drop duplicate display->fb_tracking.lock init Jani Nikula
2025-05-16 12:16 ` [PATCH 4/7] drm/i915/display: move hotplug.dp_wq init from xe and i915 to display Jani Nikula
2025-05-16 14:11   ` Matthew Auld
2025-05-16 12:16 ` [PATCH 5/7] drm/xe/display: move xe->display initialization to xe_display_probe() Jani Nikula
2025-05-16 14:24   ` Matthew Auld
2025-05-16 12:16 ` [PATCH 6/7] drm/xe/display: add notes about how early a few functions can be called Jani Nikula
2025-05-16 14:25   ` Matthew Auld
2025-05-16 12:17 ` [PATCH 7/7] drm/xe/display: use xe->display to decide whether to do anything Jani Nikula
2025-05-16 14:27   ` Matthew Auld
2025-05-16 12:53 ` ✗ Fi.CI.SPARSE: warning for drm/i915 & drm/xe: prep work towards opaque struct intel_display Patchwork
2025-05-16 13:16 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-19 11:39   ` Jani Nikula
2025-05-19 18:36 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-20 12:06 ` ✗ Fi.CI.SPARSE: warning for drm/i915 & drm/xe: prep work towards opaque struct intel_display (rev2) Patchwork
2025-05-20 12:33 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-20 14:14 ` ✗ i915.CI.Full: 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.1747397638.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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;
as well as URLs for NNTP newsgroup(s).