public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 6/6] drm/i915: Do state check for color management changes
Date: Wed, 12 Apr 2023 01:29:31 +0300	[thread overview]
Message-ID: <20230411222931.15127-7-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20230411222931.15127-1-ville.syrjala@linux.intel.com>

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

In order to validate LUT programming more thoroughly let's
do a state check for all color management updates as well.

Not sure we really want this outside CI. It is rather heavy
and color management updates could become rather common
with all the HDR/etc. stuff happening. Maybe we should have
an extra knob for this that we could enable in CI?

v2: Skip for initial_commit to avoid FDI dotclock
    sanity checks/etc. tripping up

Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 drivers/gpu/drm/i915/display/intel_modeset_verify.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_modeset_verify.c b/drivers/gpu/drm/i915/display/intel_modeset_verify.c
index 842d70f0dfd2..9e4767e1b900 100644
--- a/drivers/gpu/drm/i915/display/intel_modeset_verify.c
+++ b/drivers/gpu/drm/i915/display/intel_modeset_verify.c
@@ -228,6 +228,8 @@ void intel_modeset_verify_crtc(struct intel_crtc *crtc,
 			       struct intel_crtc_state *new_crtc_state)
 {
 	if (!intel_crtc_needs_modeset(new_crtc_state) &&
+	    (!intel_crtc_needs_color_update(new_crtc_state) ||
+	     new_crtc_state->inherited) &&
 	    !intel_crtc_needs_fastset(new_crtc_state))
 		return;
 
-- 
2.39.2


  parent reply	other threads:[~2023-04-11 22:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 22:29 [Intel-gfx] [PATCH 0/6] drm/i915: CTM stuff mostly Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 1/6] drm/uapi: Document CTM matrix better Ville Syrjala
2023-04-27 22:31   ` Xaver Hugl
2023-04-28 13:39     ` Ville Syrjälä
2023-04-28  9:27   ` Simon Ser
2023-04-11 22:29 ` [Intel-gfx] [PATCH 2/6] drm/i915: Expose crtc CTM property on ilk/snb Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 3/6] drm/i915: Fix CHV CGM CSC coefficient sign handling Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 4/6] drm/i915: Implement CTM property support for VLV Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 5/6] drm/i915: No 10bit gamma on desktop gen3 parts Ville Syrjala
2023-04-11 22:29 ` Ville Syrjala [this message]
2023-04-12  1:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTM stuff mostly Patchwork
2023-04-12  1:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-12  2:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-12  6:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTM stuff mostly (rev2) Patchwork
2023-04-12  6:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-12  6:27 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-13  5:50 ` 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=20230411222931.15127-7-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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