intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	lucas.demarchi@intel.com
Subject: Re: [PATCH v2 0/9] drm/i915/display: platform identification with display->is.<PLATFORM>
Date: Thu, 29 Aug 2024 19:03:51 +0300	[thread overview]
Message-ID: <ZtCb5yc6KCy1S6bo@intel.com> (raw)
In-Reply-To: <Zs-LdJYx_lVDt9PC@intel.com>

On Wed, Aug 28, 2024 at 04:41:24PM -0400, Rodrigo Vivi wrote:
> On Mon, Aug 19, 2024 at 09:44:27PM +0300, Jani Nikula wrote:
> > v2 of [1]. Please read the cover letter there.
> > 
> > This addresses review comments and adds a few more commits on top, in particular
> > the last one showcasing the approach.
> > 
> > The main question remains, is this what we want?
> 
> I don't know why, but the 'is' thing is still strange.
> 
> I know I know... I'm bad with naming myself.
> 
> I think about 'platform' but that get too big
> 
> if (display->platform.BROADWELL)
> 
> I think about 'gen' but then it is overloaded....
> 
> then I think about 'ip' is worse...
> 
> 'version'?
> 
> 'name'?
> 
> if (display->name.HASWELL)...
> 
> ....
> 
> But well, I like the overall simplification here in general.
> Without a better name to suggest, I guess let's just move ahead...

One slight concern with the is.foo is whether it complicates finding
things with eg. cscope. But I suppose for platforms that doesn't matter
all that much. For the has_foo stuff it'd be much more relevant.

Anyways, can't think of anything particularly elegant myself either,
so go ahead I guess.

> 
> > 
> > BR,
> > Jani.
> > 
> > [1] https://lore.kernel.org/r/cover.1718719962.git.jani.nikula@intel.com
> > 
> > 
> > Jani Nikula (9):
> >   drm/i915/display: use a macro to initialize subplatforms
> >   drm/i915/display: use a macro to define platform enumerations
> >   drm/i915/display: join the platform and subplatform enums
> >   drm/i915/display: add display platforms structure with platform
> >     members
> >   drm/i915/display: add platforms "is" member to struct intel_display
> >   drm/i915/display: remove the display platform enum as unnecessary
> >   drm/i915/display: consider HSW/BDW ULX to also be ULT
> >   drm/i915/display: keep subplatforms next to their platforms
> >   drm/i915/bios: use display->is.PLATFORM instead of IS_PLATFORM()
> > 
> >  drivers/gpu/drm/i915/display/intel_bios.c     |  36 ++--
> >  .../gpu/drm/i915/display/intel_display_core.h |   3 +
> >  .../drm/i915/display/intel_display_device.c   |  89 ++++++---
> >  .../drm/i915/display/intel_display_device.h   | 180 ++++++++++--------
> >  4 files changed, 174 insertions(+), 134 deletions(-)
> > 
> > -- 
> > 2.39.2
> > 

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-08-29 16:05 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ä [this message]
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
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=ZtCb5yc6KCy1S6bo@intel.com \
    --to=ville.syrjala@linux.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=rodrigo.vivi@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).