From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Srikanth V, NagaVenkata" <nagavenkata.srikanth.v@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/dp: Limit max compressed bpp to 18 when forcing DSC
Date: Wed, 13 Nov 2024 14:22:08 +0530 [thread overview]
Message-ID: <3fb21945-7302-418b-ad2a-fea5ddfdd730@intel.com> (raw)
In-Reply-To: <CH0PR11MB5508C6F1C3D7A4FDAB7D5080C2582@CH0PR11MB5508.namprd11.prod.outlook.com>
On 11/11/2024 12:25 PM, Srikanth V, NagaVenkata wrote:
>
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Ankit
>> Nautiyal
>> Sent: Wednesday, October 30, 2024 2:11 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: intel-xe@lists.freedesktop.org
>> Subject: [PATCH] drm/i915/dp: Limit max compressed bpp to 18 when
>> forcing DSC
>>
>> While forcing DSC when it is not actually required, the max compressed bpp
>> from the source gets picked for compression for some pipe bpps.
>> Apparently, when DSC is not required, forcing DSC to the maximum
>> compressed bpp seems to cause underruns.
>>
>> To avoid this, limit the max compressed bpp to 18 while forcing DSC. This
>> value works across platforms with different pipe bpps and prevents
>> underruns.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Looks good to me.
> Reviewed-by: Naga Venkata Srikanth V <nagavenkata.srikanth.v@intel.com>
Thank you Srikanth for the review. This is now pushed to drm-intel-next.
Regards,
Ankit
>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
>> b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 28fa5e2d0c33..0ce29cefaa13 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -2021,6 +2021,15 @@ static int dsc_src_max_compressed_bpp(struct
>> intel_dp *intel_dp) {
>> struct drm_i915_private *i915 = dp_to_i915(intel_dp);
>>
>> + /*
>> + * Forcing DSC and using the platform's max compressed bpp is seen
>> to cause
>> + * underruns. Since DSC isn't needed in these cases, limit the
>> + * max compressed bpp to 18, which is a safe value across platforms
>> with different
>> + * pipe bpps.
>> + */
>> + if (intel_dp->force_dsc_en)
>> + return 18;
>> +
>> /*
>> * Max Compressed bpp for Gen 13+ is 27bpp.
>> * For earlier platform is 23bpp. (Bspec:49259).
>> --
>> 2.45.2
prev parent reply other threads:[~2024-11-13 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 8:41 [PATCH] drm/i915/dp: Limit max compressed bpp to 18 when forcing DSC Ankit Nautiyal
2024-10-30 8:43 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-30 8:43 ` ✓ CI.checkpatch: " Patchwork
2024-10-30 8:45 ` ✓ CI.KUnit: " Patchwork
2024-10-30 8:56 ` ✓ CI.Build: " Patchwork
2024-10-30 8:58 ` ✓ CI.Hooks: " Patchwork
2024-10-30 9:00 ` ✗ CI.checksparse: warning " Patchwork
2024-10-30 9:26 ` ✓ CI.BAT: success " Patchwork
2024-10-30 10:21 ` ✗ CI.FULL: failure " Patchwork
2024-11-11 6:06 ` [PATCH] " Srikanth V, NagaVenkata
2024-11-11 6:55 ` Srikanth V, NagaVenkata
2024-11-13 8:52 ` Nautiyal, Ankit K [this message]
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=3fb21945-7302-418b-ad2a-fea5ddfdd730@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nagavenkata.srikanth.v@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