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 04/10] drm/i915: Extract chv_color_check()
Date: Wed, 20 Mar 2019 16:43:15 +0200	[thread overview]
Message-ID: <20190320144315.GM3888@intel.com> (raw)
In-Reply-To: <20190319220026.GW4773@mdroper-desk.amr.corp.intel.com>

On Tue, Mar 19, 2019 at 03:00:26PM -0700, Matt Roper wrote:
> On Mon, Mar 18, 2019 at 06:13:11PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Since CHV has the CGM unit we require a custom implementation
> > of .color_check().
> > 
> > This fixes the computation of gamma_enable as previously we
> > left it enabled even when were using the CGM gamma instead.
> > Now we turn off the legacy LUT unless it's actually required.
> 
> The CGM stuff is a bit non-obvious to anyone who hasn't focused on the
> CHV platform specifically, so it might be worth adding this
> justification in a code comment.
> 
> In fact, a general overview comment somewhere (maybe on the CHV_COLORS
> definition?) about the difference between legacy gamma and CGM might be
> helpful.  It looks like our public PRM's for CHV don't really cover
> anything display-wise.

Yeah. I think I had a patch somewhere where I document the full 
pipeline for VLV/CHV. I'll see if I can dig it out.

> 
> Anyway, the code change looks correct, so
> 
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> 
> 
> Matt
> 
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/intel_color.c | 28 ++++++++++++++++++++++++----
> >  1 file changed, 24 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_color.c b/drivers/gpu/drm/i915/intel_color.c
> > index 3d19b1a7ee95..cb88651f1da4 100644
> > --- a/drivers/gpu/drm/i915/intel_color.c
> > +++ b/drivers/gpu/drm/i915/intel_color.c
> > @@ -848,6 +848,29 @@ static u32 chv_cgm_mode(const struct intel_crtc_state *crtc_state)
> >  	return cgm_mode;
> >  }
> >  
> > +static int chv_color_check(struct intel_crtc_state *crtc_state)
> > +{
> > +	int ret;
> > +
> > +	ret = check_luts(crtc_state);
> > +	if (ret)
> > +		return ret;
> > +
> > +	crtc_state->gamma_enable =
> > +		crtc_state_is_legacy_gamma(crtc_state) &&
> > +		!crtc_state->c8_planes;
> > +
> > +	crtc_state->gamma_mode = GAMMA_MODE_MODE_8BIT;
> > +
> > +	crtc_state->cgm_mode = chv_cgm_mode(crtc_state);
> > +
> > +	ret = intel_color_add_affected_planes(crtc_state);
> > +	if (ret)
> > +		return ret;
> > +
> > +	return 0;
> > +}
> > +
> >  static int _intel_color_check(struct intel_crtc_state *crtc_state)
> >  {
> >  	struct drm_i915_private *dev_priv = to_i915(crtc_state->base.crtc->dev);
> > @@ -877,9 +900,6 @@ static int _intel_color_check(struct intel_crtc_state *crtc_state)
> >  
> >  	crtc_state->csc_mode = 0;
> >  
> > -	if (IS_CHERRYVIEW(dev_priv))
> > -		crtc_state->cgm_mode = chv_cgm_mode(crtc_state);
> > -
> >  	if (!crtc_state->gamma_enable ||
> >  	    crtc_state_is_legacy_gamma(crtc_state))
> >  		crtc_state->gamma_mode = GAMMA_MODE_MODE_8BIT;
> > @@ -917,7 +937,7 @@ void intel_color_init(struct intel_crtc *crtc)
> >  
> >  	if (HAS_GMCH(dev_priv)) {
> >  		if (IS_CHERRYVIEW(dev_priv)) {
> > -			dev_priv->display.color_check = _intel_color_check;
> > +			dev_priv->display.color_check = chv_color_check;
> >  			dev_priv->display.color_commit = i9xx_color_commit;
> >  			dev_priv->display.load_luts = cherryview_load_luts;
> >  		} else {
> > -- 
> > 2.19.2
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> IoTG Platform Enabling & Development
> Intel Corporation
> (916) 356-2795

-- 
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-03-20 14:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:13 [PATCH 00/10] drm/i915: Clean up intel_color_check() Ville Syrjala
2019-03-18 16:13 ` [PATCH 01/10] drm/i915: Extract check_luts() Ville Syrjala
2019-03-19 16:24   ` Jani Nikula
2019-03-20 14:46     ` Ville Syrjälä
2019-03-19 21:59   ` Matt Roper
2019-03-20 14:41     ` Ville Syrjälä
2019-03-20 15:14       ` Matt Roper
2019-03-20 15:31         ` Ville Syrjälä
2019-03-20 22:48           ` Matt Roper
2019-03-18 16:13 ` [PATCH 02/10] drm/i915: Turn intel_color_check() into a vfunc Ville Syrjala
2019-03-19 21:59   ` Matt Roper
2019-03-18 16:13 ` [PATCH 03/10] drm/i915: Extract i9xx_color_check() Ville Syrjala
2019-03-19 22:00   ` Matt Roper
2019-03-18 16:13 ` [PATCH 04/10] drm/i915: Extract chv_color_check() Ville Syrjala
2019-03-19 22:00   ` Matt Roper
2019-03-20 14:43     ` Ville Syrjälä [this message]
2019-03-18 16:13 ` [PATCH 05/10] drm/i915: Extract icl_color_check() Ville Syrjala
2019-03-18 16:13 ` [PATCH 06/10] drm/i915: Extract glk_color_check() Ville Syrjala
2019-03-18 16:13 ` [PATCH 07/10] drm/i915: Extract bdw_color_check() Ville Syrjala
2019-03-20 22:49   ` Matt Roper
2019-03-18 16:13 ` [PATCH 08/10] drm/i915: Extract ilk_color_check() Ville Syrjala
2019-03-20 22:49   ` Matt Roper
2019-03-21 10:05     ` Ville Syrjälä
2019-03-18 16:13 ` [PATCH 09/10] drm/i915: Drop the pointless linear legacy LUT load on CHV Ville Syrjala
2019-03-20 22:50   ` Matt Roper
2019-03-18 16:13 ` [PATCH 10/10] drm/i915: Skip the linear degamma LUT load on ICL+ Ville Syrjala
2019-03-20 22:50   ` Matt Roper
2019-03-18 20:15 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Clean up intel_color_check() Patchwork
2019-03-18 20:41 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-19  9:01 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-19 16:26 ` [PATCH 00/10] " Jani Nikula
2019-03-19 16:31   ` Ville Syrjälä

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=20190320144315.GM3888@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.