From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Lucas De Marchi" <lucas.demarchi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 0/9] drm/i915/display: platform identification with display->is.<PLATFORM>
Date: Fri, 27 Sep 2024 12:13:20 -0400 [thread overview]
Message-ID: <ZvbZoIyzcg-EZ9ic@intel.com> (raw)
In-Reply-To: <87bk09xhqx.fsf@intel.com>
On Fri, Sep 27, 2024 at 06:01:58PM +0300, Jani Nikula wrote:
> On Fri, 27 Sep 2024, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > On Fri, Sep 27, 2024 at 03:16:23PM +0300, Jani Nikula wrote:
> >> For example, RPL-S:
> >>
> >>
> >> if (display->platform.alderlake_s_raptorlake_s)
> >>
> >> But the main platform also matches its subplatforms:
> >>
> >> if (display->platform.alderlake_s)
> >>
> >> This is the same as with the patches at hand. Except for the
> >> uppercase/lowercase difference, and s/is/platform/.
> >
> > Yeap, let's go with that then!
>
> Double-checking: do you want both s/is/platform *and* lowercase?
>
> if (display->platform.alderlake_s_raptorlake_s)
>
> Mulling over this I've ended up preferring lowercase. (Maybe need to do
> something to pretty print them to logs.)
I believe that I like the lowercase more too.
We could have a map for the debug prints, but I would delay this, because
that could end up in discussions with marketing brand strings... :/
>
> And just the platform without "is_" prefix, i.e. *not*:
>
> if (display->platform.is_alderlake_s_raptorlake_s)
I like the version without 'is' better...
>
>
> BR,
> Jani.
>
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-27 16:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 18:44 [PATCH v2 0/9] drm/i915/display: platform identification with display->is.<PLATFORM> Jani Nikula
2024-08-19 18:44 ` [PATCH v2 1/9] drm/i915/display: use a macro to initialize subplatforms Jani Nikula
2024-08-19 18:44 ` [PATCH v2 2/9] drm/i915/display: use a macro to define platform enumerations Jani Nikula
2024-08-19 18:44 ` [PATCH v2 3/9] drm/i915/display: join the platform and subplatform enums Jani Nikula
2024-08-19 18:44 ` [PATCH v2 4/9] drm/i915/display: add display platforms structure with platform members Jani Nikula
2024-08-28 20:46 ` Rodrigo Vivi
2024-08-19 18:44 ` [PATCH v2 5/9] drm/i915/display: add platforms "is" member to struct intel_display Jani Nikula
2024-08-19 18:48 ` [PATCH v3] " Jani Nikula
2024-08-28 20:48 ` Rodrigo Vivi
2024-08-28 20:47 ` [PATCH v2 5/9] " Rodrigo Vivi
2024-08-19 18:44 ` [PATCH v2 6/9] drm/i915/display: remove the display platform enum as unnecessary Jani Nikula
2024-08-28 20:49 ` Rodrigo Vivi
2024-08-19 18:44 ` [PATCH v2 7/9] drm/i915/display: consider HSW/BDW ULX to also be ULT Jani Nikula
2024-08-28 20:50 ` Rodrigo Vivi
2024-08-19 18:44 ` [PATCH v2 8/9] drm/i915/display: keep subplatforms next to their platforms Jani Nikula
2024-08-28 20:52 ` Rodrigo Vivi
2024-08-19 18:44 ` [PATCH v2 9/9] drm/i915/bios: use display->is.PLATFORM instead of IS_PLATFORM() Jani Nikula
2024-08-28 20:52 ` Rodrigo Vivi
2024-08-19 19:13 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: platform identification with display->is.<PLATFORM> (rev3) Patchwork
2024-08-19 19:13 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-19 19:15 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-20 9:51 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-28 20:41 ` [PATCH v2 0/9] drm/i915/display: platform identification with display->is.<PLATFORM> Rodrigo Vivi
2024-08-29 16:03 ` Ville Syrjälä
2024-09-24 9:49 ` Jani Nikula
2024-09-24 13:14 ` Lucas De Marchi
2024-09-24 13:37 ` Jani Nikula
2024-09-24 13:43 ` Ville Syrjälä
2024-09-26 14:58 ` Rodrigo Vivi
2024-09-27 12:16 ` Jani Nikula
2024-09-27 14:49 ` Rodrigo Vivi
2024-09-27 15:01 ` Jani Nikula
2024-09-27 16:13 ` Rodrigo Vivi [this message]
2024-09-27 18:12 ` Lucas De Marchi
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=ZvbZoIyzcg-EZ9ic@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).