public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/3] drm/i915/de: Move register polling into display code
Date: Fri, 13 Mar 2026 13:10:25 +0200	[thread overview]
Message-ID: <20260313111028.25159-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Implement register polling directly in the display code
In an effort to decouple the display code from i915/xe.

This is just the first step in a larger display mmio rework.
My final aim is to move the entire mmio stuff into the display
code. That will give us:
- better control over how things are done
- decouple display register locking from forcewake/etc
- less overhead. We access a lot of registers, and
  during vblank evasion critical section performance is
  especially important.
- unified RMbus unclaimed error checking for both i915 and xe

Ville Syrjälä (3):
  drm/i915/de: Introduce intel_de.c and move intel_de_{read,write}8()
    there
  drm/i915/de: Move intel_de_wait*() into intel_de.c
  drm/i915/de: Implement register polling in the display code

 drivers/gpu/drm/i915/Makefile                 |   1 +
 drivers/gpu/drm/i915/display/intel_de.c       | 178 ++++++++++++++++++
 drivers/gpu/drm/i915/display/intel_de.h       | 121 +++---------
 drivers/gpu/drm/xe/Makefile                   |   1 +
 .../drm/xe/compat-i915-headers/intel_uncore.h |  31 ---
 5 files changed, 203 insertions(+), 129 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/display/intel_de.c

-- 
2.52.0


             reply	other threads:[~2026-03-13 11:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 11:10 Ville Syrjala [this message]
2026-03-13 11:10 ` [PATCH 1/3] drm/i915/de: Introduce intel_de.c and move intel_de_{read, write}8() there Ville Syrjala
2026-03-13 14:21   ` Jani Nikula
2026-03-13 11:10 ` [PATCH 2/3] drm/i915/de: Move intel_de_wait*() into intel_de.c Ville Syrjala
2026-03-13 14:21   ` Jani Nikula
2026-03-13 11:10 ` [PATCH 3/3] drm/i915/de: Implement register polling in the display code Ville Syrjala
2026-03-13 15:03   ` Jani Nikula
2026-03-17  7:52     ` Ville Syrjälä
2026-03-23  9:50     ` Ville Syrjälä
2026-03-14  8:09   ` kernel test robot
2026-03-23  9:43   ` [PATCH v2 " Ville Syrjala
2026-03-13 11:15 ` ✗ CI.checkpatch: warning for drm/i915/de: Move register polling into " Patchwork
2026-03-13 11:17 ` ✓ CI.KUnit: success " Patchwork
2026-03-13 11:51 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-14 14:29 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-23 10:43 ` ✗ CI.checkpatch: warning for drm/i915/de: Move register polling into display code (rev2) Patchwork
2026-03-23 10:45 ` ✓ CI.KUnit: success " Patchwork
2026-03-23 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-23 13:56 ` ✓ Xe.CI.FULL: " 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=20260313111028.25159-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.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