From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: Correct max compressed bpp bounds by using link bpp
Date: Thu, 16 Jan 2025 18:24:36 +0200 [thread overview]
Message-ID: <87h65yg20r.fsf@intel.com> (raw)
In-Reply-To: <Z4kmGN0RrY7VVBzQ@intel.com>
On Thu, 16 Jan 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Thu, Jan 16, 2025 at 03:24:16PM +0530, Ankit Nautiyal wrote:
>> While setting the bounds for compressed bpp we ensure that the
>> compressed bpp is less than the pipe bpp.
>>
>> This gives an issue with 420 output format where effective link bpp is
>> half that of the pipe bpp. Therefore instead of pipe bpp use link bpp to
>> set the bounds for the compressed bpp.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp.c | 10 ++++++++--
>
> patches to i915, even when they target only platforms supported by
> xe should also be sent to intel-gfx mainlinlist...
Agreed... but this one was? :)
BR,
Jani.
>
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 1ad25c37f3c2..47fcfbcb893b 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -2068,9 +2068,12 @@ icl_dsc_compute_link_config(struct intel_dp *intel_dp,
>> int timeslots)
>> {
>> int i, ret;
>> + int link_bpp;
>> +
>> + link_bpp = intel_dp_output_bpp(pipe_config->output_format, pipe_bpp);
>>
>> /* Compressed BPP should be less than the Input DSC bpp */
>> - dsc_max_bpp = min(dsc_max_bpp, pipe_bpp - 1);
>> + dsc_max_bpp = min(dsc_max_bpp, link_bpp - 1);
>>
>> for (i = 0; i < ARRAY_SIZE(valid_dsc_bpp); i++) {
>> if (valid_dsc_bpp[i] < dsc_min_bpp)
>> @@ -2113,6 +2116,7 @@ xelpd_dsc_compute_link_config(struct intel_dp *intel_dp,
>> u8 bppx16_incr = drm_dp_dsc_sink_bpp_incr(connector->dp.dsc_dpcd);
>> u16 compressed_bppx16;
>> u8 bppx16_step;
>> + int link_bpp;
>> int ret;
>>
>> if (DISPLAY_VER(display) < 14 || bppx16_incr <= 1)
>> @@ -2120,8 +2124,10 @@ xelpd_dsc_compute_link_config(struct intel_dp *intel_dp,
>> else
>> bppx16_step = 16 / bppx16_incr;
>>
>> + link_bpp = intel_dp_output_bpp(pipe_config->output_format, pipe_bpp);
>> +
>> /* Compressed BPP should be less than the Input DSC bpp */
>> - dsc_max_bpp = min(dsc_max_bpp << 4, (pipe_bpp << 4) - bppx16_step);
>> + dsc_max_bpp = min(dsc_max_bpp << 4, (link_bpp << 4) - bppx16_step);
>> dsc_min_bpp = dsc_min_bpp << 4;
>>
>> for (compressed_bppx16 = dsc_max_bpp;
>> --
>> 2.45.2
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-01-16 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 9:54 [PATCH] drm/i915/dp: Correct max compressed bpp bounds by using link bpp Ankit Nautiyal
2025-01-16 10:11 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-16 10:12 ` ✓ CI.checkpatch: " Patchwork
2025-01-16 10:13 ` ✓ CI.KUnit: " Patchwork
2025-01-16 10:35 ` ✓ CI.Build: " Patchwork
2025-01-16 10:39 ` ✓ CI.Hooks: " Patchwork
2025-01-16 10:41 ` ✓ CI.checksparse: " Patchwork
2025-01-16 13:02 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-16 14:11 ` ✗ Xe.CI.Full: " Patchwork
2025-01-16 15:30 ` [PATCH] " Rodrigo Vivi
2025-01-16 16:24 ` Jani Nikula [this message]
2025-01-16 16:41 ` Rodrigo Vivi
2025-01-16 17:43 ` Imre Deak
2025-01-17 5:15 ` 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=87h65yg20r.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.