From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/3] drm/i915: Plane/wm cleanups
Date: Thu, 17 Feb 2022 01:28:03 +0200 [thread overview]
Message-ID: <20220216232806.6194-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Leftovers from the earlier series. Addressed Jani's review
comments to some degree and dealt with intel_mchbar_regs.h
appearing in the tree.
Ville Syrjälä (3):
drm/i915: Introduce intel_crtc_planes_update_arm()
drm/i915: Clean up SSKPD/MLTR defines
drm/i915: Polish ilk+ wm register bits
.../gpu/drm/i915/display/intel_atomic_plane.c | 23 +++--
.../gpu/drm/i915/display/intel_atomic_plane.h | 10 +--
drivers/gpu/drm/i915/display/intel_display.c | 8 +-
.../drm/i915/display/intel_display_debugfs.c | 2 +-
drivers/gpu/drm/i915/i915_reg.h | 49 +++++------
drivers/gpu/drm/i915/intel_mchbar_regs.h | 17 ++--
drivers/gpu/drm/i915/intel_pm.c | 83 +++++++++----------
7 files changed, 97 insertions(+), 95 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-16 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 23:28 Ville Syrjala [this message]
2022-02-16 23:28 ` [Intel-gfx] [PATCH v2 1/3] drm/i915: Introduce intel_crtc_planes_update_arm() Ville Syrjala
2022-02-17 6:15 ` Jani Nikula
2022-02-16 23:28 ` [Intel-gfx] [PATCH v2 2/3] drm/i915: Clean up SSKPD/MLTR defines Ville Syrjala
2022-02-16 23:28 ` [Intel-gfx] [PATCH v2 3/3] drm/i915: Polish ilk+ wm register bits Ville Syrjala
2022-02-17 17:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Plane/wm cleanups (rev3) Patchwork
2022-02-17 17:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-17 18:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-18 4:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220216232806.6194-1-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@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