From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: <imre.deak@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <suraj.kandpal@intel.com>,
<jani.nikula@linux.intel.com>
Subject: Re: [PATCH 1/7] drm/i915/dp: Use HAS_DSC macro in intel_dp_dsc_max_src_input_bpc
Date: Fri, 15 Nov 2024 13:40:19 +0530 [thread overview]
Message-ID: <6ac692c9-6ef1-42c2-a154-45fe82e07b80@intel.com> (raw)
In-Reply-To: <ZxD_fiyWKZTO5f_3@ideak-desk.fi.intel.com>
On 10/17/2024 5:43 PM, Imre Deak wrote:
> On Thu, Oct 03, 2024 at 04:13:37PM +0530, Ankit Nautiyal wrote:
>> Use HAS_DSC macro to take into account platforms for which DSC is fused.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index c4fdae5097ec..c47748905506 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -1766,6 +1766,9 @@ intel_dp_compute_link_config_wide(struct intel_dp *intel_dp,
>> static
>> u8 intel_dp_dsc_max_src_input_bpc(struct drm_i915_private *i915)
>> {
>> + if (!HAS_DSC(i915))
> This is checked already earlier via intel_dp_has_dsc(), couldn't we rely
> on that instead of checking it in these lower level functions?
Sorry for replying late to this.
You are right currently we already check this long before calling this
function.
However I am intending to use this in
intel_dp_compute_config_link_bpp_limits which is earlier than the check
for DSC, for that perhaps need to add a check before computing link bpp
limits for DSC.
In any case we can avoid the HAS_DSC() check here and in corresponding
min helper too.
Regards,
Ankit
>
>> + return 0;
>> +
>> /* Max DSC Input BPC for ICL is 10 and for TGL+ is 12 */
>> if (DISPLAY_VER(i915) >= 12)
>> return 12;
>> --
>> 2.45.2
>>
next prev parent reply other threads:[~2024-11-15 8:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 10:43 [PATCH 0/7] DP DSC min/max src bpc fixes Ankit Nautiyal
2024-10-03 10:43 ` [PATCH 1/7] drm/i915/dp: Use HAS_DSC macro in intel_dp_dsc_max_src_input_bpc Ankit Nautiyal
2024-10-03 11:04 ` Kandpal, Suraj
2024-10-17 12:13 ` Imre Deak
2024-11-15 8:10 ` Nautiyal, Ankit K [this message]
2024-10-03 10:43 ` [PATCH 2/7] drm/i915/dp: Return int from dsc_max/min_src_input_bpc helpers Ankit Nautiyal
2024-10-03 10:43 ` [PATCH 3/7] drm/i915/dp_mst: Use helpers to get dsc min/max input bpc Ankit Nautiyal
2024-10-03 10:43 ` [PATCH 4/7] drm/i915/dp: Drop max_requested_bpc for dsc pipe_min/max bpp Ankit Nautiyal
2024-10-13 15:35 ` Kandpal, Suraj
2024-10-03 10:43 ` [PATCH 5/7] drm/i915/dp: Refactor pipe_bpp limits with dsc Ankit Nautiyal
2024-10-13 15:37 ` Kandpal, Suraj
2024-10-17 12:20 ` Imre Deak
2024-11-15 8:13 ` Nautiyal, Ankit K
2024-11-15 8:25 ` Nautiyal, Ankit K
2024-10-03 10:43 ` [PATCH 6/7] drm/i915/dp: Use clamp for pipe_bpp limits with DSC Ankit Nautiyal
2024-10-13 15:39 ` Kandpal, Suraj
2024-10-03 10:43 ` [PATCH 7/7] drm/i915/dp: Set the DSC link limits intel_dp_compute_config_link_bpp_limits Ankit Nautiyal
2024-10-13 15:46 ` Kandpal, Suraj
2024-10-15 6:15 ` Kandpal, Suraj
2024-10-17 12:42 ` Imre Deak
2024-11-15 8:28 ` Nautiyal, Ankit K
2024-10-03 10:49 ` ✓ CI.Patch_applied: success for DP DSC min/max src bpc fixes Patchwork
2024-10-03 10:49 ` ✓ CI.checkpatch: " Patchwork
2024-10-03 10:50 ` ✓ CI.KUnit: " Patchwork
2024-10-03 11:03 ` ✓ CI.Build: " Patchwork
2024-10-03 11:05 ` ✓ CI.Hooks: " Patchwork
2024-10-03 11:07 ` ✗ CI.checksparse: warning " Patchwork
2024-10-03 11:19 ` ✗ Fi.CI.CHECKPATCH: warning for DP DSC min/max src bpc fixes (rev8) Patchwork
2024-10-03 11:27 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-03 11:31 ` ✓ CI.BAT: success for DP DSC min/max src bpc fixes Patchwork
2024-10-03 12:30 ` ✗ CI.FULL: failure " Patchwork
2024-10-07 21:17 ` ✗ Fi.CI.IGT: failure for DP DSC min/max src bpc fixes (rev8) Patchwork
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=6ac692c9-6ef1-42c2-a154-45fe82e07b80@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.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 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.