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: Fix timeslots argument for DP DSC SST case
Date: Tue, 3 Jan 2023 11:14:16 -0500 [thread overview]
Message-ID: <Y7RUWCLR8oxywAzI@intel.com> (raw)
In-Reply-To: <20230102132306.9663-1-stanislav.lisovskiy@intel.com>
On Mon, Jan 02, 2023 at 03:23:06PM +0200, Stanislav Lisovskiy wrote:
> We now accept timeslots param exactly how the variable
> sounds: amount of timeslots, but not ratio timeslots/64.
> So for SST case(when we have all timeslots for use), it
> should be 64, but not 1.
I noticed that at intel_dp_dsc_get_output_bpp() we have this comment:
* for SST -> TimeSlotsPerMTP is 1,
and there's a bunch of math used with this timeslots, but none of them
is a direct division by 64.
So I wonder if a refactor to reflect the "perMTP" is not needed there.
Or the reverse math instead of passing the 64 directly.
> This caused some issues in the tests.
could you also expand on what tests?
any "References:" link to cibuglog or so?
Oh, any "Fixes:" tag as well?
Thanks for the patch,
Rodrigo.
>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 13baf3cb5f934..362fb394d613c 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1696,7 +1696,7 @@ intel_dp_compute_link_config(struct intel_encoder *encoder,
> str_yes_no(ret), str_yes_no(joiner_needs_dsc),
> str_yes_no(intel_dp->force_dsc_en));
> ret = intel_dp_dsc_compute_config(intel_dp, pipe_config,
> - conn_state, &limits, 1, true);
> + conn_state, &limits, 64, true);
> if (ret < 0)
> return ret;
> }
> --
> 2.37.3
>
next prev parent reply other threads:[~2023-01-03 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 13:23 [Intel-gfx] [PATCH] drm/i915: Fix timeslots argument for DP DSC SST case Stanislav Lisovskiy
2023-01-02 14:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-02 17:04 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-01-03 16:14 ` Rodrigo Vivi [this message]
2023-01-09 13:36 ` [Intel-gfx] [PATCH] " Lisovskiy, Stanislav
2023-01-03 17:55 ` Navare, Manasi
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 14:02 Stanislav Lisovskiy
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=Y7RUWCLR8oxywAzI@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