All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 3/3] drm/i915: Add background color hardware readout and state check
Date: Tue, 5 Feb 2019 22:09:46 +0200	[thread overview]
Message-ID: <20190205200946.GZ20097@intel.com> (raw)
In-Reply-To: <20190131235508.6970-4-matthew.d.roper@intel.com>

On Thu, Jan 31, 2019 at 03:55:08PM -0800, Matt Roper wrote:
> We should support readout and verification of crtc background color as
> we do with other pipe state.  Note that our hardware holds less bits of
> precision than the CRTC state allows, so we need to take care to only
> verify the most significant bits of the color after performing readout.
> 
> At boot time the pipe color is already sanitized to full black as
> required by ABI, so the new readout here won't break that requirement.
> 
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> ---
>  drivers/gpu/drm/i915/intel_display.c | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 469480fe01a4..ecbfc8ce7b54 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -9740,6 +9740,7 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc,
>  	struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
>  	enum intel_display_power_domain power_domain;
>  	u64 power_domain_mask;
> +	u32 bgcolor;
>  	bool active;
>  
>  	intel_crtc_init_scalers(crtc, pipe_config);
> @@ -9806,6 +9807,15 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc,
>  		pipe_config->pixel_multiplier = 1;
>  	}
>  
> +	if (INTEL_GEN(dev_priv) >= 9) {
> +		bgcolor = I915_READ(SKL_BOTTOM_COLOR(crtc->pipe));
> +		pipe_config->base.bgcolor =
> +			drm_argb(10, 0xFFFF,
> +				 bgcolor >> 20 & 0x3FF,
> +				 bgcolor >> 10 & 0x3FF,
> +				 bgcolor       & 0x3FF);
> +	}
> +
>  out:
>  	for_each_power_domain(power_domain, power_domain_mask)
>  		intel_display_power_put_unchecked(dev_priv, power_domain);
> @@ -11422,6 +11432,10 @@ static void intel_dump_pipe_config(struct intel_crtc *crtc,
>  				      drm_rect_width(&state->base.dst),
>  				      drm_rect_height(&state->base.dst));
>  	}
> +
> +	if (INTEL_GEN(dev_priv) >= 9)
> +		DRM_DEBUG_KMS("background color: %llx\n",
> +			      pipe_config->base.bgcolor);
>  }
>  
>  static bool check_digital_port_conflicts(struct drm_atomic_state *state)
> @@ -11784,6 +11798,16 @@ intel_pipe_config_compare(struct drm_i915_private *dev_priv,
>  	} \
>  } while (0)
>  
> +#define PIPE_CONF_CHECK_LLX_MASKED(name, mask) do { \
> +	if ((current_config->name & mask) != (pipe_config->name & mask)) { \
> +		pipe_config_err(adjust, __stringify(name), \
> +			  "(expected 0x%016llx, found 0x%016llx)\n", \
> +			  current_config->name & mask, \
> +			  pipe_config->name & mask); \
> +		ret = false; \
> +	} \
> +} while (0)
> +
>  #define PIPE_CONF_CHECK_I(name) do { \
>  	if (current_config->name != pipe_config->name) { \
>  		pipe_config_err(adjust, __stringify(name), \
> @@ -12035,6 +12059,14 @@ intel_pipe_config_compare(struct drm_i915_private *dev_priv,
>  
>  	PIPE_CONF_CHECK_I(min_voltage_level);
>  
> +	/*
> +	 * Hardware only holds top 10 bits of each color component; ignore
> +	 * bottom six bits (and all of alpha) when comparing against readout.
> +	 */
> +	if (INTEL_GEN(dev_priv) >= 9)
> +		PIPE_CONF_CHECK_LLX_MASKED(base.bgcolor, 0x0000FFC0FFC0FFC0);
> +
> +#undef PIPE_CONF_CHECK_LLX_MASKED
>  #undef PIPE_CONF_CHECK_X
>  #undef PIPE_CONF_CHECK_I
>  #undef PIPE_CONF_CHECK_BOOL
> -- 
> 2.14.5

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-02-05 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 23:55 [PATCH v5 0/3] CRTC background color Matt Roper
2019-01-31 23:55 ` [PATCH v5 1/3] drm: Add CRTC background color property (v5) Matt Roper
2019-01-31 23:55 ` [PATCH v5 2/3] drm/i915/gen9+: Add support for pipe background color (v5) Matt Roper
2019-01-31 23:55 ` [PATCH v5 3/3] drm/i915: Add background color hardware readout and state check Matt Roper
2019-02-05 20:09   ` Ville Syrjälä [this message]
2019-02-01  0:29 ` ✗ Fi.CI.CHECKPATCH: warning for CRTC background color (rev6) Patchwork
2019-02-01  0:31 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-01  1:06 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-01  4:36 ` ✓ 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=20190205200946.GZ20097@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.