From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: <suraj.kandpal@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm/i915/display: Add macro for checking 3 DSC engines
Date: Tue, 15 Apr 2025 13:13:57 +0530 [thread overview]
Message-ID: <6f700d4c-eebe-4e48-8a7d-f71f01f281fe@intel.com> (raw)
In-Reply-To: <87y0w1sxlb.fsf@intel.com>
On 4/15/2025 12:47 PM, Jani Nikula wrote:
> On Mon, 14 Apr 2025, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
>> 3 DSC engines per pipe is currently supported only for BMG.
>> Add a macro to check whether a platform supports 3 DSC engines per pipe.
> Nitpick, feels like a macro returning the number of DSC engines per pipe
> would be more generic. Like, would you also add HAS_DSC_2ENGINES() and
> HAS_DSC_4ENGINES() if you needed to know that? But I guess we can go
> with what you have for the immediate fix.
Yeah NUM_DSC_ENGINES seem better. I was under an impression that newer
platforms would have 3 DSC engines, which was incorrect, so specific
case for 3 engines made sense at that time.
If there is any further change, I guess returning number of DSC engines
as you have suggested is the way to go.
>
> However, adding the tiniest macro and its only user in separate patches,
> for something that needs to be backported to stable, seems like erring
> on the side of splitting up patches too much.
Noted. I agree it could have been just one fix with the macro and the
usage in same patch.
I have already pushed to drm-intel-next :(. But will keep that in mind.
Thanks Jani for the guidance, thanks Suraj for reviews.
Regards,
Ankit
>
> BR,
> Jani.
>
>
>> v2:Fix Typo in macro argument. (Suraj).
>> Added fixes tag.
>>
>> Bspec: 50175
>> Fixes: be7f5fcdf4a0 ("drm/i915/dp: Enable 3 DSC engines for 12 slices")
>> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> Cc: Suraj Kandpal <suraj.kandpal@intel.com>
>> Cc: <stable@vger.kernel.org> # v6.14+
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display_device.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
>> index 368b0d3417c2..87c666792c0d 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_device.h
>> +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
>> @@ -163,6 +163,7 @@ struct intel_display_platforms {
>> #define HAS_DP_MST(__display) (DISPLAY_INFO(__display)->has_dp_mst)
>> #define HAS_DSB(__display) (DISPLAY_INFO(__display)->has_dsb)
>> #define HAS_DSC(__display) (DISPLAY_RUNTIME_INFO(__display)->has_dsc)
>> +#define HAS_DSC_3ENGINES(__display) (DISPLAY_VERx100(__display) == 1401 && HAS_DSC(__display))
>> #define HAS_DSC_MST(__display) (DISPLAY_VER(__display) >= 12 && HAS_DSC(__display))
>> #define HAS_FBC(__display) (DISPLAY_RUNTIME_INFO(__display)->fbc_mask != 0)
>> #define HAS_FBC_DIRTY_RECT(__display) (DISPLAY_VER(__display) >= 30)
next prev parent reply other threads:[~2025-04-15 7:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 2:42 [PATCH 0/2] Macro for 3 DSC engines per pipe Ankit Nautiyal
2025-04-14 2:42 ` [PATCH 1/2] drm/i915/display: Add macro for checking 3 DSC engines Ankit Nautiyal
2025-04-14 3:27 ` kernel test robot
2025-04-14 3:48 ` Kandpal, Suraj
2025-04-14 4:05 ` Nautiyal, Ankit K
2025-04-14 4:06 ` Kandpal, Suraj
2025-04-14 8:57 ` Ankit Nautiyal
2025-04-14 9:12 ` Kandpal, Suraj
2025-04-15 7:17 ` Jani Nikula
2025-04-15 7:43 ` Nautiyal, Ankit K [this message]
2025-04-14 2:42 ` [PATCH 2/2] drm/i915/dp: Check for HAS_DSC_3ENGINES while configuring DSC slices Ankit Nautiyal
2025-04-14 4:07 ` Kandpal, Suraj
2025-04-14 3:10 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 3:11 ` ✓ CI.checkpatch: " Patchwork
2025-04-14 3:12 ` ✓ CI.KUnit: " Patchwork
2025-04-14 3:20 ` ✓ CI.Build: " Patchwork
2025-04-14 3:23 ` ✓ CI.Hooks: " Patchwork
2025-04-14 3:24 ` ✗ CI.checksparse: warning " Patchwork
2025-04-14 3:56 ` ✗ Fi.CI.SPARSE: warning for Macro for 3 DSC engines per pipe Patchwork
2025-04-14 4:09 ` ✓ Xe.CI.BAT: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 5:23 ` ✓ i915.CI.BAT: success for Macro for 3 DSC engines per pipe Patchwork
2025-04-14 5:34 ` ✗ Xe.CI.Full: failure for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 9:17 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines (rev2) Patchwork
2025-04-14 9:22 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-14 9:29 ` ✓ CI.KUnit: success " Patchwork
2025-04-14 9:34 ` ✓ CI.Build: " Patchwork
2025-04-14 9:36 ` ✓ CI.Hooks: " Patchwork
2025-04-14 9:37 ` ✗ CI.checksparse: warning " Patchwork
2025-04-14 10:19 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-14 10:24 ` ✗ Fi.CI.CHECKPATCH: warning for Macro for 3 DSC engines per pipe (rev2) Patchwork
2025-04-14 10:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-14 10:46 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-14 11:50 ` ✗ Xe.CI.Full: failure for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines (rev2) Patchwork
2025-04-14 13:16 ` ✗ i915.CI.Full: failure for Macro for 3 DSC engines per pipe (rev2) Patchwork
2025-04-15 4:42 ` ✓ i915.CI.Full: success " 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=6f700d4c-eebe-4e48-8a7d-f71f01f281fe@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=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.