Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/dp: Fix the computation for compressed_bpp for DISPLAY < 13
Date: Tue, 2 Apr 2024 11:27:11 +0530	[thread overview]
Message-ID: <c79bbdbf-73f9-4fa4-8769-30839abab09c@intel.com> (raw)
In-Reply-To: <SN7PR11MB67505CB6CA830E1553138A31E3342@SN7PR11MB6750.namprd11.prod.outlook.com>


On 3/27/2024 9:35 AM, Kandpal, Suraj wrote:
>> Subject: [PATCH] drm/i915/dp: Fix the computation for compressed_bpp for
>> DISPLAY < 13
>>
>> For DISPLAY < 13, compressed bpp is chosen from a list of supported
>> compressed bpps. Fix the condition to choose the appropriate compressed
>> bpp from the list.
>>
> LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>

Thanks for the review. Patch was pushed to drm-intel-next.

Regards,

Ankit

>
>> Fixes: 1c56e9a39833 ("drm/i915/dp: Get optimal link config to have best
>> compressed bpp")
>> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: <stable@vger.kernel.org> # v6.7+
>> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/10162
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dp.c | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
>> b/drivers/gpu/drm/i915/display/intel_dp.c
>> index e13121dc3a03..d579195f84ee 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -1918,8 +1918,9 @@ icl_dsc_compute_link_config(struct intel_dp
>> *intel_dp,
>>   	dsc_max_bpp = min(dsc_max_bpp, pipe_bpp - 1);
>>
>>   	for (i = 0; i < ARRAY_SIZE(valid_dsc_bpp); i++) {
>> -		if (valid_dsc_bpp[i] < dsc_min_bpp ||
>> -		    valid_dsc_bpp[i] > dsc_max_bpp)
>> +		if (valid_dsc_bpp[i] < dsc_min_bpp)
>> +			continue;
>> +		if (valid_dsc_bpp[i] > dsc_max_bpp)
>>   			break;
>>
>>   		ret = dsc_compute_link_config(intel_dp,
>> --
>> 2.40.1

      reply	other threads:[~2024-04-02  5:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  5:44 [PATCH] drm/i915/dp: Fix the computation for compressed_bpp for DISPLAY < 13 Ankit Nautiyal
2024-03-05  6:53 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-05  6:53 ` ✓ CI.checkpatch: " Patchwork
2024-03-05  6:54 ` ✓ CI.KUnit: " Patchwork
2024-03-05  7:04 ` ✓ CI.Build: " Patchwork
2024-03-05  7:05 ` ✓ CI.Hooks: " Patchwork
2024-03-05  7:06 ` ✗ CI.checksparse: warning " Patchwork
2024-03-05  7:26 ` ✓ CI.BAT: success " Patchwork
2024-03-27  4:05 ` [PATCH] " Kandpal, Suraj
2024-04-02  5:57   ` 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=c79bbdbf-73f9-4fa4-8769-30839abab09c@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=suraj.kandpal@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