From: Manasi Navare <manasi.d.navare@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Small joiner RAM buffer size is platform-specific
Date: Wed, 25 Sep 2019 15:12:18 -0700 [thread overview]
Message-ID: <20190925221218.GB22579@intel.com> (raw)
In-Reply-To: <20190925055311.18086-1-matthew.d.roper@intel.com>
On Tue, Sep 24, 2019 at 10:53:11PM -0700, Matt Roper wrote:
> According to the bspec, GLK/CNL have a smaller small joiner RAM buffer
> than ICL+. This feels like something that could easily change again on
> future platforms, so let's just add a function to return the proper
> per-platform buffer size. That may also slightly simplify the upcoming
> bigjoiner enabling.
>
> Since we have to change intel_dp_dsc_get_output_bpp()'s signature to
> pass the dev_priv down for the platform check, let's take the
> opportunity to also make that function static since it isn't used
> outside the intel_dp file.
>
> Bspec: 20388
> Bspec: 49259
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 29 ++++++++++++++++++-------
> drivers/gpu/drm/i915/display/intel_dp.h | 2 --
> 2 files changed, 21 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 829559f97440..e38db7278cf2 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -68,9 +68,6 @@
>
> #define DP_DPRX_ESI_LEN 14
>
> -/* DP DSC small joiner has 2 FIFOs each of 640 x 6 bytes */
> -#define DP_DSC_MAX_SMALL_JOINER_RAM_BUFFER 61440
> -
> /* DP DSC throughput values used for slice count calculations KPixels/s */
> #define DP_DSC_PEAK_PIXEL_RATE 2720000
> #define DP_DSC_MAX_ENC_THROUGHPUT_0 340000
> @@ -164,6 +161,10 @@ static void vlv_steal_power_sequencer(struct drm_i915_private *dev_priv,
> enum pipe pipe);
> static void intel_dp_unset_edid(struct intel_dp *intel_dp);
>
> +static u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
> + int link_clock, u8 lane_count,
> + int mode_clock, int mode_hdisplay);
> +
> /* update sink rates from dpcd */
> static void intel_dp_set_sink_rates(struct intel_dp *intel_dp)
> {
> @@ -541,7 +542,8 @@ intel_dp_mode_valid(struct drm_connector *connector,
> true);
> } else if (drm_dp_sink_supports_fec(intel_dp->fec_capable)) {
> dsc_max_output_bpp =
> - intel_dp_dsc_get_output_bpp(max_link_clock,
> + intel_dp_dsc_get_output_bpp(dev_priv,
> + max_link_clock,
> max_lanes,
> target_clock,
> mode->hdisplay) >> 4;
> @@ -1968,7 +1970,8 @@ static int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
> u8 dsc_dp_slice_count;
>
> dsc_max_output_bpp =
> - intel_dp_dsc_get_output_bpp(pipe_config->port_clock,
> + intel_dp_dsc_get_output_bpp(dev_priv,
> + pipe_config->port_clock,
> pipe_config->lane_count,
> adjusted_mode->crtc_clock,
> adjusted_mode->crtc_hdisplay);
> @@ -4373,8 +4376,18 @@ intel_dp_get_sink_irq_esi(struct intel_dp *intel_dp, u8 *sink_irq_vector)
> DP_DPRX_ESI_LEN;
> }
>
> -u16 intel_dp_dsc_get_output_bpp(int link_clock, u8 lane_count,
> - int mode_clock, int mode_hdisplay)
> +static int
> +small_joiner_ram_size_bits(struct drm_i915_private *i915)
> +{
> + if (INTEL_GEN(i915) >= 11)
> + return 7680 * 8;
> + else
> + return 6144 * 8;
> +}
This makes sense,
Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
Manasi
> +
> +static u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
> + int link_clock, u8 lane_count,
> + int mode_clock, int mode_hdisplay)
> {
> u16 bits_per_pixel, max_bpp_small_joiner_ram;
> int i;
> @@ -4390,7 +4403,7 @@ u16 intel_dp_dsc_get_output_bpp(int link_clock, u8 lane_count,
> mode_clock;
>
> /* Small Joiner Check: output bpp <= joiner RAM (bits) / Horiz. width */
> - max_bpp_small_joiner_ram = DP_DSC_MAX_SMALL_JOINER_RAM_BUFFER /
> + max_bpp_small_joiner_ram = small_joiner_ram_size_bits(i915) /
> mode_hdisplay;
>
> /*
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.h b/drivers/gpu/drm/i915/display/intel_dp.h
> index e01d1f89409d..1bcbf44b0b4e 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.h
> +++ b/drivers/gpu/drm/i915/display/intel_dp.h
> @@ -103,8 +103,6 @@ bool intel_dp_source_supports_hbr2(struct intel_dp *intel_dp);
> bool intel_dp_source_supports_hbr3(struct intel_dp *intel_dp);
> bool
> intel_dp_get_link_status(struct intel_dp *intel_dp, u8 *link_status);
> -u16 intel_dp_dsc_get_output_bpp(int link_clock, u8 lane_count,
> - int mode_clock, int mode_hdisplay);
> u8 intel_dp_dsc_get_slice_count(struct intel_dp *intel_dp, int mode_clock,
> int mode_hdisplay);
>
> --
> 2.21.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-25 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 5:53 [PATCH] drm/i915: Small joiner RAM buffer size is platform-specific Matt Roper
2019-09-25 6:25 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-09-25 8:23 ` [PATCH] " Maarten Lankhorst
2019-09-25 20:40 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-09-26 17:20 ` Matt Roper
2019-09-25 22:12 ` Manasi Navare [this message]
2019-09-25 23:45 ` [CI] " Matt Roper
2019-09-26 1:26 ` ✗ Fi.CI.BAT: failure for drm/i915: Small joiner RAM buffer size is platform-specific (rev2) Patchwork
2019-09-26 2:45 ` Matt Roper
2019-09-26 4:35 ` ✓ Fi.CI.BAT: success for drm/i915: Small joiner RAM buffer size is platform-specific (rev3) Patchwork
2019-09-27 1:07 ` ✓ Fi.CI.IGT: " 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=20190925221218.GB22579@intel.com \
--to=manasi.d.navare@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox