Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Navare, Manasi" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v5 5/6] drm/i915/dp: Prep for bigjoiner atomic check
Date: Thu, 5 Nov 2020 18:16:41 +0200	[thread overview]
Message-ID: <20201105161641.GZ6112@intel.com> (raw)
In-Reply-To: <20201105160938.GA10935@labuser-Z97X-UD5H>

On Thu, Nov 05, 2020 at 08:09:38AM -0800, Navare, Manasi wrote:
> On Thu, Nov 05, 2020 at 05:23:33PM +0200, Ville Syrjälä wrote:
> > On Thu, Nov 05, 2020 at 05:21:31PM +0200, Ville Syrjälä wrote:
> > > On Mon, Nov 02, 2020 at 01:19:05PM -0800, Manasi Navare wrote:
> > > > No functional changes here. Just pass intel_atomic_state
> > > > along with crtc_state to certain atomic_check functions.
> > > > This will lay the foundation for adding bigjoiner master/slave
> > > > states in atomic check.
> > > > 
> > > > v2:
> > > > * More prep with intel_atomic_state (Ville)
> > > > 
> > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > > > ---
> > > >  drivers/gpu/drm/i915/display/intel_atomic.c  |  9 +++++----
> > > >  drivers/gpu/drm/i915/display/intel_atomic.h  |  3 ++-
> > > >  drivers/gpu/drm/i915/display/intel_display.c | 21 ++++++++++++--------
> > > >  3 files changed, 20 insertions(+), 13 deletions(-)
> > > > 
> > > > diff --git a/drivers/gpu/drm/i915/display/intel_atomic.c b/drivers/gpu/drm/i915/display/intel_atomic.c
> > > > index 86be032bcf96..e243ce97b534 100644
> > > > --- a/drivers/gpu/drm/i915/display/intel_atomic.c
> > > > +++ b/drivers/gpu/drm/i915/display/intel_atomic.c
> > > > @@ -270,14 +270,15 @@ void intel_crtc_free_hw_state(struct intel_crtc_state *crtc_state)
> > > >  	intel_crtc_put_color_blobs(crtc_state);
> > > >  }
> > > >  
> > > > -void intel_crtc_copy_color_blobs(struct intel_crtc_state *crtc_state)
> > > > +void intel_crtc_copy_color_blobs(struct intel_crtc_state *crtc_state,
> > > > +				 const struct intel_crtc_state *from_crtc_state)
> > > >  {
> > > >  	drm_property_replace_blob(&crtc_state->hw.degamma_lut,
> > > > -				  crtc_state->uapi.degamma_lut);
> > > > +				  from_crtc_state->uapi.degamma_lut);
> > > >  	drm_property_replace_blob(&crtc_state->hw.gamma_lut,
> > > > -				  crtc_state->uapi.gamma_lut);
> > > > +				  from_crtc_state->uapi.gamma_lut);
> > > >  	drm_property_replace_blob(&crtc_state->hw.ctm,
> > > > -				  crtc_state->uapi.ctm);
> > > > +				  from_crtc_state->uapi.ctm);
> > > 
> > > This patch still seems to do two totally separate things:
> > > 1) pass intel_atomic_State all over (for which there was another
> > >    patch in the series as well?)
> > 
> > Looks like it was patch 4. So I would just squash all those changes from
> > here into patch 4.
> 
> Okay so all the changes where I am sending the intel_atomic_state to functions
> move those to Patch 4 and then just keep the
> color blobs change here?

Yeah. Not entirely certain the color blob thing needs its own patch
anymore then, but no real harm in having it like that I guess.

> 
> Manasi
> 
> > 
> > > 2) this intel_crtc_copy_color_blobs() change
> > > 
> > > I would split these up because the commit message doesn't
> > > even mention the second change.
> > > 
> > > Each part looks fine on its own so with a proper split they are
> > > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > 
> > > >  }
> > > >  
> > > >  /**
> > > > diff --git a/drivers/gpu/drm/i915/display/intel_atomic.h b/drivers/gpu/drm/i915/display/intel_atomic.h
> > > > index 285de07011dc..62a3365ed5e6 100644
> > > > --- a/drivers/gpu/drm/i915/display/intel_atomic.h
> > > > +++ b/drivers/gpu/drm/i915/display/intel_atomic.h
> > > > @@ -43,7 +43,8 @@ struct drm_crtc_state *intel_crtc_duplicate_state(struct drm_crtc *crtc);
> > > >  void intel_crtc_destroy_state(struct drm_crtc *crtc,
> > > >  			       struct drm_crtc_state *state);
> > > >  void intel_crtc_free_hw_state(struct intel_crtc_state *crtc_state);
> > > > -void intel_crtc_copy_color_blobs(struct intel_crtc_state *crtc_state);
> > > > +void intel_crtc_copy_color_blobs(struct intel_crtc_state *crtc_state,
> > > > +				 const struct intel_crtc_state *from_crtc_state);
> > > >  struct drm_atomic_state *intel_atomic_state_alloc(struct drm_device *dev);
> > > >  void intel_atomic_state_free(struct drm_atomic_state *state);
> > > >  void intel_atomic_state_clear(struct drm_atomic_state *state);
> > > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > > > index 0bea90cdf242..ab10dfe705e4 100644
> > > > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > > > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > > > @@ -13459,13 +13459,17 @@ static bool check_digital_port_conflicts(struct intel_atomic_state *state)
> > > >  }
> > > >  
> > > >  static void
> > > > -intel_crtc_copy_uapi_to_hw_state_nomodeset(struct intel_crtc_state *crtc_state)
> > > > +intel_crtc_copy_uapi_to_hw_state_nomodeset(struct intel_atomic_state *state,
> > > > +					   struct intel_crtc_state *crtc_state)
> > > >  {
> > > > -	intel_crtc_copy_color_blobs(crtc_state);
> > > > +	const struct intel_crtc_state *from_crtc_state = crtc_state;
> > > > +
> > > > +	intel_crtc_copy_color_blobs(crtc_state, from_crtc_state);
> > > >  }
> > > >  
> > > >  static void
> > > > -intel_crtc_copy_uapi_to_hw_state(struct intel_crtc_state *crtc_state)
> > > > +intel_crtc_copy_uapi_to_hw_state(struct intel_atomic_state *state,
> > > > +				 struct intel_crtc_state *crtc_state)
> > > >  {
> > > >  	crtc_state->hw.enable = crtc_state->uapi.enable;
> > > >  	crtc_state->hw.active = crtc_state->uapi.active;
> > > > @@ -13473,7 +13477,7 @@ intel_crtc_copy_uapi_to_hw_state(struct intel_crtc_state *crtc_state)
> > > >  	crtc_state->hw.pipe_mode = crtc_state->hw.adjusted_mode = crtc_state->uapi.adjusted_mode;
> > > >  	crtc_state->hw.scaling_filter = crtc_state->uapi.scaling_filter;
> > > >  
> > > > -	intel_crtc_copy_uapi_to_hw_state_nomodeset(crtc_state);
> > > > +	intel_crtc_copy_uapi_to_hw_state_nomodeset(state, crtc_state);
> > > >  }
> > > >  
> > > >  static void intel_crtc_copy_hw_to_uapi_state(struct intel_crtc_state *crtc_state)
> > > > @@ -13496,7 +13500,8 @@ static void intel_crtc_copy_hw_to_uapi_state(struct intel_crtc_state *crtc_state
> > > >  }
> > > >  
> > > >  static int
> > > > -intel_crtc_prepare_cleared_state(struct intel_crtc_state *crtc_state)
> > > > +intel_crtc_prepare_cleared_state(struct intel_atomic_state *state,
> > > > +				 struct intel_crtc_state *crtc_state)
> > > >  {
> > > >  	struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc);
> > > >  	struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> > > > @@ -13528,7 +13533,7 @@ intel_crtc_prepare_cleared_state(struct intel_crtc_state *crtc_state)
> > > >  	memcpy(crtc_state, saved_state, sizeof(*crtc_state));
> > > >  	kfree(saved_state);
> > > >  
> > > > -	intel_crtc_copy_uapi_to_hw_state(crtc_state);
> > > > +	intel_crtc_copy_uapi_to_hw_state(state, crtc_state);
> > > >  
> > > >  	return 0;
> > > >  }
> > > > @@ -15233,12 +15238,12 @@ static int intel_atomic_check(struct drm_device *dev,
> > > >  					    new_crtc_state, i) {
> > > >  		if (!needs_modeset(new_crtc_state)) {
> > > >  			/* Light copy */
> > > > -			intel_crtc_copy_uapi_to_hw_state_nomodeset(new_crtc_state);
> > > > +			intel_crtc_copy_uapi_to_hw_state_nomodeset(state, new_crtc_state);
> > > >  
> > > >  			continue;
> > > >  		}
> > > >  
> > > > -		ret = intel_crtc_prepare_cleared_state(new_crtc_state);
> > > > +		ret = intel_crtc_prepare_cleared_state(state, new_crtc_state);
> > > >  		if (ret)
> > > >  			goto fail;
> > > >  
> > > > -- 
> > > > 2.19.1
> > > 
> > > -- 
> > > Ville Syrjälä
> > > Intel
> > 
> > -- 
> > Ville Syrjälä
> > Intel

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

  reply	other threads:[~2020-11-05 16:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 21:19 [Intel-gfx] [PATCH v5 1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes Manasi Navare
2020-11-02 21:19 ` [Intel-gfx] [PATCH v5 2/6] drm/i915: Move encoder->get_config to a new function Manasi Navare
2020-11-05 15:15   ` Ville Syrjälä
2020-11-02 21:19 ` [Intel-gfx] [PATCH v5 3/6] drm/i915: Add hw.pipe_mode to allow bigjoiner pipe/transcoder split Manasi Navare
2020-11-02 23:04   ` [Intel-gfx] [PATCH v6 " Manasi Navare
2020-11-05 15:13     ` Ville Syrjälä
2020-11-05 16:03       ` Navare, Manasi
2020-11-05 16:15         ` Ville Syrjälä
2020-11-05 18:59           ` Navare, Manasi
2020-11-02 21:19 ` [Intel-gfx] [PATCH v5 4/6] drm/i915: Pass intel_atomic_state instead of drm_atomic_state Manasi Navare
2020-11-05 15:14   ` Ville Syrjälä
2020-11-02 21:19 ` [Intel-gfx] [PATCH v5 5/6] drm/i915/dp: Prep for bigjoiner atomic check Manasi Navare
2020-11-05 15:21   ` Ville Syrjälä
2020-11-05 15:23     ` Ville Syrjälä
2020-11-05 16:09       ` Navare, Manasi
2020-11-05 16:16         ` Ville Syrjälä [this message]
2020-11-02 21:19 ` [Intel-gfx] [PATCH v5 6/6] drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid(), v3 Manasi Navare
2020-11-03 16:00   ` [Intel-gfx] [PATCH v6 " Manasi Navare
2020-11-05 16:11     ` Navare, Manasi
2020-11-05 16:27     ` Ville Syrjälä
2020-11-02 21:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes Patchwork
2020-11-02 22:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-11-02 23:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes (rev2) Patchwork
2020-11-02 23:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-03  7:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-11-03 16:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes (rev3) Patchwork
2020-11-03 16:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-03 22:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-11-12  0:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes (rev4) Patchwork
2020-11-12  1:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-12  4:09 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-11-12  6:29   ` Navare, Manasi

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=20201105161641.GZ6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=manasi.d.navare@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox