Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
	"Kulkarni, Vandita" <vandita.kulkarni@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Kulkarni, Vandita" <vandita.kulkarni@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix the dsc check while selecting min_cdclk
Date: Tue, 28 Sep 2021 08:07:58 +0000	[thread overview]
Message-ID: <4dd46926250b46459c27d26e774e63e4@intel.com> (raw)
In-Reply-To: <87fstqs6hh.fsf@intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani Nikula
> Sent: Monday, September 27, 2021 3:09 PM
> To: Kulkarni, Vandita <vandita.kulkarni@intel.com>; intel-gfx@lists.freedesktop.org
> Cc: Kulkarni, Vandita <vandita.kulkarni@intel.com>
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix the dsc check while selecting
> min_cdclk
> 
> On Wed, 15 Sep 2021, Vandita Kulkarni <vandita.kulkarni@intel.com> wrote:
> > The right parameter that selects second dsc engine is dsc_split.
> > Hence use dsc_split instead of slice_count while selecting the cdclk
> > in order to accommodate 1ppc limitaion of vdsc.
> >
> > Fixes: fe01883fdcef ("drm/i915: Get proper min cdclk if vDSC enabled")
> > Suggested-by: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
> 
> Sorry for the delay!
> 
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

Pushed the change to drm-intel-next. Thanks for the patch and review.

Regards,
Uma Shankar
> > ---
> >  drivers/gpu/drm/i915/display/intel_cdclk.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c
> > b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > index 9aec17b33819..3a1cdb3937aa 100644
> > --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> > +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > @@ -2140,13 +2140,11 @@ int intel_crtc_compute_min_cdclk(const struct
> intel_crtc_state *crtc_state)
> >  	min_cdclk = max(intel_planes_min_cdclk(crtc_state), min_cdclk);
> >
> >  	/*
> > -	 * VDSC engine can process only 1 pixel per Cd clock.
> > -	 * In case VDSC is used and max slice count == 1,
> > -	 * max supported pixel clock should be 100% of CD clock.
> > -	 * Then do min_cdclk and pixel clock comparison to get cdclk.
> > +	 * When we decide to use only one VDSC engine, since
> > +	 * each VDSC operates with 1 ppc throughput, pixel clock
> > +	 * cannot be higher than the VDSC clock (cdclk)
> >  	 */
> > -	if (crtc_state->dsc.compression_enable &&
> > -	    crtc_state->dsc.slice_count == 1)
> > +	if (crtc_state->dsc.compression_enable &&
> > +!crtc_state->dsc.dsc_split)
> >  		min_cdclk = max(min_cdclk, (int)crtc_state->pixel_rate);
> >
> >  	/*
> 
> --
> Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2021-09-28  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15  5:43 [Intel-gfx] [PATCH] drm/i915/display: Fix the dsc check while selecting min_cdclk Vandita Kulkarni
2021-09-15  6:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-09-15 11:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display: Fix the dsc check while selecting min_cdclk (rev2) Patchwork
2021-09-16  9:56   ` Kulkarni, Vandita
2021-09-21  4:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Fix the dsc check while selecting min_cdclk (rev3) Patchwork
2021-09-21  5:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-21 10:25   ` Kulkarni, Vandita
2021-09-21 15:20 ` Patchwork
2021-09-21 15:48 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-09-27  9:38 ` [Intel-gfx] [PATCH] drm/i915/display: Fix the dsc check while selecting min_cdclk Jani Nikula
2021-09-28  8:07   ` Shankar, Uma [this message]

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=4dd46926250b46459c27d26e774e63e4@intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=vandita.kulkarni@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