From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/6] drm/i915: Use intel_crtc_state everywhere!
Date: Fri, 28 Jun 2019 10:55:11 +0200 [thread overview]
Message-ID: <20190628085517.31886-1-maarten.lankhorst@linux.intel.com> (raw)
To prepare for a hw and uapi state split in intel_crtc_state, we need
to start replacing all internal usage of drm_crtc_state with intel_crtc_state.
This makes it easier to convert to split state later, and cleans up the code
slightly.
Maarten Lankhorst (6):
drm/i915: Pass intel_crtc_state to needs_modeset()
drm/i915: Convert most of atomic commit to take more intel state
drm/i915: Convert hw state verifier to take more intel state, v2.
drm/i915: Use intel_crtc_state in sanitize_watermarks() too
drm/i915: Pass intel state to plane functions as well
drm/i915: Use intel state as much as possible in wm code
.../gpu/drm/i915/display/intel_atomic_plane.c | 56 +-
.../gpu/drm/i915/display/intel_atomic_plane.h | 5 +-
drivers/gpu/drm/i915/display/intel_display.c | 681 ++++++++----------
drivers/gpu/drm/i915/i915_drv.h | 18 +-
drivers/gpu/drm/i915/intel_pm.c | 413 +++++------
drivers/gpu/drm/i915/intel_pm.h | 4 +-
6 files changed, 566 insertions(+), 611 deletions(-)
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-06-28 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:55 Maarten Lankhorst [this message]
2019-06-28 8:55 ` [PATCH v2 1/6] drm/i915: Pass intel_crtc_state to needs_modeset() Maarten Lankhorst
2019-06-28 8:55 ` [PATCH v2 2/6] drm/i915: Convert most of atomic commit to take more intel state Maarten Lankhorst
2019-06-28 8:55 ` [PATCH v2 3/6] drm/i915: Convert hw state verifier to take more intel state, v2 Maarten Lankhorst
2019-06-28 8:55 ` [PATCH v2 4/6] drm/i915: Use intel_crtc_state in sanitize_watermarks() too Maarten Lankhorst
2019-06-28 8:55 ` [PATCH v2 5/6] drm/i915: Pass intel state to plane functions as well Maarten Lankhorst
2019-06-28 8:55 ` [PATCH v2 6/6] drm/i915: Use intel state as much as possible in wm code Maarten Lankhorst
2019-07-01 8:34 ` Maarten Lankhorst
2019-06-28 9:21 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use intel_crtc_state everywhere! Patchwork
2019-06-28 9:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-28 15:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-28 23:21 ` ✓ 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=20190628085517.31886-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@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