From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/dp: Update Bigjoiner interface bits for computing compressed bpp
Date: Wed, 29 Mar 2023 14:59:33 +0300 [thread overview]
Message-ID: <ZCQoJd06J8fwIG9P@intel.com> (raw)
In-Reply-To: <abba986c-3626-2cc6-6d94-744e94d4ba89@intel.com>
On Wed, Mar 29, 2023 at 04:53:13PM +0530, Nautiyal, Ankit K wrote:
>
> On 3/29/2023 4:24 PM, Ville Syrjälä wrote:
> > On Wed, Mar 29, 2023 at 02:37:45PM +0530, Ankit Nautiyal wrote:
> >> In Bigjoiner check for DSC, bigjoiner interface bits for DP for
> >> DISPLAY > 13 is 36 (Bspec: 49259).
> >>
> >> v2: Corrected Display ver to 13.
> >>
> >> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/display/intel_dp.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> >> index da1c00ee92fb..0b59c1e53678 100644
> >> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> >> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> >> @@ -756,8 +756,9 @@ u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
> >> bits_per_pixel = min(bits_per_pixel, max_bpp_small_joiner_ram);
> >>
> >> if (bigjoiner) {
> >> + int bigjoiner_interface_bits = DISPLAY_VER(i915) <= 13 ? 24 : 36;
> > We generally prefer "new -> old" order. So please flip that around.
>
> Noted. Will do this in next version.
>
>
> >
> >> u32 max_bpp_bigjoiner =
> >> - i915->display.cdclk.max_cdclk_freq * 48 /
> >> + i915->display.cdclk.max_cdclk_freq * 2 * bigjoiner_interface_bits /
> >> intel_dp_mode_to_fec_clock(mode_clock);
> > Hmm. Why is this using the FEC adjusted clock here?
>
> AFAIU we always use FEC for DP when DSC is enabled, provided sink and
> source both support FEC.
>
> Bspec mentions : For cases where FEC is enabled, pixel clock is replaced
> by pixel clock/0.972261 in the above calculations.
That doesn't make sense to me. FEC happens in the PHY
layer, DSC compression happens earlier.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-03-29 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 8:44 [Intel-gfx] [PATCH 0/2] Update DSC Bigjoiner BW check Ankit Nautiyal
2023-03-29 8:44 ` [Intel-gfx] [PATCH 1/2] drm/i915/dp: Update Bigjoiner interface bits for computing compressed bpp Ankit Nautiyal
2023-03-29 9:07 ` [Intel-gfx] [PATCH v2 " Ankit Nautiyal
2023-03-29 10:54 ` Ville Syrjälä
2023-03-29 11:23 ` Nautiyal, Ankit K
2023-03-29 11:59 ` Ville Syrjälä [this message]
2023-03-29 8:44 ` [Intel-gfx] [PATCH 2/2] drm/i915/dp: Use current cdclk for DSC Bigjoiner BW check Ankit Nautiyal
2023-03-29 9:57 ` Ville Syrjälä
2023-03-29 10:36 ` Nautiyal, Ankit K
2023-03-29 10:53 ` Ville Syrjälä
2023-03-29 11:30 ` Nautiyal, Ankit K
2023-03-29 11:35 ` Ville Syrjälä
2023-03-29 13:44 ` Lisovskiy, Stanislav
2023-03-29 14:05 ` Ville Syrjälä
2023-03-30 11:07 ` Nautiyal, Ankit K
2023-03-30 11:11 ` Nautiyal, Ankit K
2023-04-03 21:33 ` Manasi Navare
2023-04-04 5:13 ` Nautiyal, Ankit K
2023-03-29 16:52 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Update DSC Bigjoiner BW check (rev2) 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=ZCQoJd06J8fwIG9P@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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