From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Implement workaround for DP2 UHBR bandwidth check
Date: Tue, 3 Jan 2023 11:32:28 -0500 [thread overview]
Message-ID: <Y7RYnHQEFntiPLYV@intel.com> (raw)
In-Reply-To: <20230102113937.9263-1-stanislav.lisovskiy@intel.com>
on the subject: This is not a hw workaround. Please remove the workaround from
the subject and the wrong comment.
"The HSD given is a 'feature' rather than 'bugeco' so no workaround details are
present here."
On Mon, Jan 02, 2023 at 01:39:37PM +0200, Stanislav Lisovskiy wrote:
> According to spec, we should check if output_bpp * pixel_rate is less
> than DDI clock * 72, if UHBR is used.
>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index bf80f296a8fdb..13baf3cb5f934 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1582,6 +1582,17 @@ int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
> drm_dbg_kms(&dev_priv->drm, "DSC: compressed bpp %d slice count %d\n",
> pipe_config->dsc.compressed_bpp,
> pipe_config->dsc.slice_count);
> +
> + /* wa1406899791 */
even if it was a bugeco, the notation doesn't follow the standard.
But anyway, as I pointed out, this is not a workaround so
you probably just want a
HSDES: 1406899791
BSPEC: 49259
in your commit msg.
Also maybe a "Fixes:" tag pointing to the commit that added the sequence
but didn't added this part of the sequence?
> + if (intel_dp_is_uhbr(pipe_config)) {
> + int output_bpp = pipe_config->dsc.compressed_bpp;
> +
> + if (output_bpp * adjusted_mode->crtc_clock >=
> + pipe_config->port_clock * 72) {
> + drm_dbg_kms(&dev_priv->drm, "DP2 UHBR check failed\n");
some probably dummy question:
do we need to add a check for the DP 2.0 above as well?
or it is unecessary/redundant?
> + return -EINVAL;
> + }
> + }
> }
> /*
> * VDSC engine operates at 1 Pixel per clock, so if peak pixel rate
> --
> 2.37.3
>
next prev parent reply other threads:[~2023-01-03 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 11:39 [Intel-gfx] [PATCH] drm/i915: Implement workaround for DP2 UHBR bandwidth check Stanislav Lisovskiy
2023-01-02 13:47 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-01-03 16:32 ` Rodrigo Vivi [this message]
2023-01-09 15:06 ` [Intel-gfx] [PATCH] " Lisovskiy, Stanislav
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 12:33 Stanislav Lisovskiy
2023-01-10 19:12 ` Rodrigo Vivi
2023-01-11 9:17 ` Lisovskiy, Stanislav
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=Y7RYnHQEFntiPLYV@intel.com \
--to=rodrigo.vivi@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