From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/4] drm/i915: Clean up crtc state flag checks
Date: Thu, 20 Oct 2022 15:04:53 +0300 [thread overview]
Message-ID: <20221020120457.19528-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Some cleanups for checking whether the crtc was flagged for
modesets/fastsets/color update.
Ville Syrjälä (4):
drm/i915: Introduce intel_crtc_needs_fastset()
drm/i915: Remove some local 'mode_changed' bools
drm/i915: Don't flag both full modeset and fastset at the same time
drm/i915: Introduce intel_crtc_needs_color_update()
drivers/gpu/drm/i915/display/hsw_ips.c | 8 ++--
drivers/gpu/drm/i915/display/intel_crtc.c | 3 +-
drivers/gpu/drm/i915/display/intel_cursor.c | 6 ++-
drivers/gpu/drm/i915/display/intel_display.c | 46 +++++++++----------
.../drm/i915/display/intel_display_types.h | 14 ++++++
.../drm/i915/display/intel_modeset_verify.c | 3 +-
6 files changed, 46 insertions(+), 34 deletions(-)
--
2.35.1
next reply other threads:[~2022-10-20 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 12:04 Ville Syrjala [this message]
2022-10-20 12:04 ` [Intel-gfx] [PATCH 1/4] drm/i915: Introduce intel_crtc_needs_fastset() Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 2/4] drm/i915: Remove some local 'mode_changed' bools Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 3/4] drm/i915: Don't flag both full modeset and fastset at the same time Ville Syrjala
2022-10-20 12:04 ` [Intel-gfx] [PATCH 4/4] drm/i915: Introduce intel_crtc_needs_color_update() Ville Syrjala
2022-10-20 13:45 ` [Intel-gfx] [PATCH 0/4] drm/i915: Clean up crtc state flag checks Jani Nikula
2022-10-20 14:17 ` Ville Syrjälä
2022-10-20 15:02 ` Jani Nikula
2022-10-20 15:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-10-21 15:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Clean up crtc state flag checks (rev2) 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=20221020120457.19528-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