Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Use compressed bpp when calculating m/n value for DP MST DSC
Date: Mon, 27 Mar 2023 08:51:46 +0000	[thread overview]
Message-ID: <b6f702e4bf46f8fb6f3e15416c20208f6864c356.camel@intel.com> (raw)
In-Reply-To: <20230327064217.24033-1-stanislav.lisovskiy@intel.com>

On Mon, 2023-03-27 at 09:42 +0300, Stanislav Lisovskiy wrote:
> For obvious reasons, we use compressed bpp instead of pipe bpp for
> DSC DP SST case. Lets be consistent and use compressed bpp instead of
> pipe bpp, also in DP MST DSC case.
> 
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp_mst.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>

> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index a860cbc5dbea..c3e8db943e9c 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -232,7 +232,7 @@ static int intel_dp_dsc_mst_compute_link_config(struct intel_encoder *encoder,
>                         return slots;
>         }
>  
> -       intel_link_compute_m_n(crtc_state->pipe_bpp,
> +       intel_link_compute_m_n(crtc_state->dsc.compressed_bpp,
>                                crtc_state->lane_count,
>                                adjusted_mode->crtc_clock,
>                                crtc_state->port_clock,


  parent reply	other threads:[~2023-03-27  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  6:42 [Intel-gfx] [PATCH] drm/i915: Use compressed bpp when calculating m/n value for DP MST DSC Stanislav Lisovskiy
2023-03-27  7:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-27  8:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-03-27  8:51 ` Govindapillai, Vinod [this message]
2023-03-27  9:32 ` [Intel-gfx] [PATCH] " Nautiyal, Ankit K

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=b6f702e4bf46f8fb6f3e15416c20208f6864c356.camel@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=stanislav.lisovskiy@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