From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>,
<mitulkumar.ajitkumar.golani@intel.com>,
<lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/i915/display: Maintain alphabetical order for HAS_AS_SDP and HAS_CMRR
Date: Thu, 13 Mar 2025 10:08:30 +0530 [thread overview]
Message-ID: <cdb8af14-e5fe-4718-991b-1b44fcea5d04@intel.com> (raw)
In-Reply-To: <174179922572.12216.11347505165808081803@intel.com>
On 3/12/2025 10:37 PM, Gustavo Sousa wrote:
> Quoting Jani Nikula (2025-03-11 15:08:48-03:00)
>> On Tue, 11 Mar 2025, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
>>> Reorder the macros HAS_AS_SDP and HAS_CMRR as per alphabetical order.
>>>
>>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/display/intel_display_device.h | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
>>> index 717286981687..332647c4ca81 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display_device.h
>>> +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
>>> @@ -142,10 +142,12 @@ struct intel_display_platforms {
>>> func(supports_tv);
>>>
>>> #define HAS_4TILE(__display) ((__display)->platform.dg2 || DISPLAY_VER(__display) >= 14)
>>> +#define HAS_AS_SDP(__display) (DISPLAY_VER(__display) >= 13)
>>> #define HAS_ASYNC_FLIPS(__display) (DISPLAY_VER(__display) >= 5)
>> Y comes before _ in asciibetical order.
> Maybe that's just me, but I feel that's counter-intuitive in a context
> where we use _ to separate words.
I do agree. I was assuming that we sort the words separated by '_' as
delimiter.
For a given hypothetical list, I thought the ordering will result in
similar items grouped together
(please forgive me for making up silly names here)
HAS_HD
HAS_HD_AUDIO
HAS_HD_DISPLAY
HAS_HD_SUPPORT
HAS_HDMI
HAS_HDMI_PCON
HAS_HDR
But with the `sort` command it will be:
HAS_HD
HAS_HDMI
HAS_HDMI_PCON
HAS_HDR
HAS_HD_AUDIO
HAS_HD_DISPLAY
HAS_HD_SUPPORT
However, if majority of folks use editor's sort command it becomes
simpler to have the ASCII ordering for everyone.
Regards,
Ankit
>
> --
> Gustavo Sousa
>
>> BR,
>> Jani.
>>
>>> #define HAS_BIGJOINER(__display) (DISPLAY_VER(__display) >= 11 && HAS_DSC(__display))
>>> #define HAS_CDCLK_CRAWL(__display) (DISPLAY_INFO(__display)->has_cdclk_crawl)
>>> #define HAS_CDCLK_SQUASH(__display) (DISPLAY_INFO(__display)->has_cdclk_squash)
>>> +#define HAS_CMRR(__display) (DISPLAY_VER(__display) >= 20)
>>> #define HAS_CMTG(__display) (!(__display)->platform.dg2 && DISPLAY_VER(__display) >= 13)
>>> #define HAS_CUR_FBC(__display) (!HAS_GMCH(__display) && IS_DISPLAY_VER(__display, 7, 13))
>>> #define HAS_D12_PLANE_MINIMIZATION(__display) ((__display)->platform.rocketlake || (__display)->platform.alderlake_s)
>>> @@ -189,8 +191,6 @@ struct intel_display_platforms {
>>> ((__display)->platform.dgfx && DISPLAY_VER(__display) == 14)) && \
>>> HAS_DSC(__display))
>>> #define HAS_VRR(__display) (DISPLAY_VER(__display) >= 11)
>>> -#define HAS_AS_SDP(__display) (DISPLAY_VER(__display) >= 13)
>>> -#define HAS_CMRR(__display) (DISPLAY_VER(__display) >= 20)
>>> #define INTEL_NUM_PIPES(__display) (hweight8(DISPLAY_RUNTIME_INFO(__display)->pipe_mask))
>>> #define I915_HAS_HOTPLUG(__display) (DISPLAY_INFO(__display)->has_hotplug)
>>> #define OVERLAY_NEEDS_PHYSICAL(__display) (DISPLAY_INFO(__display)->overlay_needs_physical)
>> --
>> Jani Nikula, Intel
next prev parent reply other threads:[~2025-03-13 4:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:59 [PATCH] drm/i915/display: Maintain alphabetical order for HAS_AS_SDP and HAS_CMRR Ankit Nautiyal
2025-03-11 17:01 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-11 17:02 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 17:03 ` ✓ CI.KUnit: " Patchwork
2025-03-11 17:19 ` ✓ CI.Build: " Patchwork
2025-03-11 17:21 ` ✓ CI.Hooks: " Patchwork
2025-03-11 17:23 ` ✓ CI.checksparse: " Patchwork
2025-03-11 17:43 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2025-03-11 17:45 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-11 18:08 ` [PATCH] " Jani Nikula
2025-03-12 4:30 ` Nautiyal, Ankit K
2025-03-12 11:25 ` Jani Nikula
2025-03-12 16:41 ` Lucas De Marchi
2025-03-12 17:07 ` Gustavo Sousa
2025-03-13 4:38 ` Nautiyal, Ankit K [this message]
2025-03-13 4:45 ` Lucas De Marchi
2025-03-13 5:02 ` Nautiyal, Ankit K
2025-03-13 8:44 ` Jani Nikula
2025-03-11 18:10 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-03-12 9:31 ` ✗ Xe.CI.Full: " 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=cdb8af14-e5fe-4718-991b-1b44fcea5d04@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=mitulkumar.ajitkumar.golani@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.