Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/5] drm/i915/display: Move display runtime info to display structure
Date: Mon, 22 May 2023 09:41:49 -0700	[thread overview]
Message-ID: <20230522164149.GI10045@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <f1808a5d-ebb7-552a-0d0a-b08862861f92@intel.com>

On Thu, May 18, 2023 at 09:56:07AM +0200, Andrzej Hajda wrote:
> On 18.05.2023 05:18, Matt Roper wrote:
> > Move the runtime info specific to display into display-specific
> > structures as has already been done with the constant display info.
> > 
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> > ---
...
> > --- a/drivers/gpu/drm/i915/display/intel_display_device.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
> > @@ -29,7 +29,30 @@
> >   	func(overlay_needs_physical); \
> >   	func(supports_tv);
> > +struct intel_display_runtime_info {
> > +	struct {
> > +		u16 ver;
> > +		u16 rel;
> > +		u16 step;
> > +	} ip;
> 
> Why not intel_ip_version? Maybe upgrdaded to 16bit.

intel_ip_version is an i915-specific structure.  Part of the goal of
this series is to minimize the use of i915 types (aside from those that
are specific to display) so that the code can be more easily re-used in
Xe with a smaller compatibility layer.


Matt

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  reply	other threads:[~2023-05-22 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  3:17 [Intel-gfx] [PATCH 0/5] i915: Move display identification/probing under display/ Matt Roper
2023-05-18  3:18 ` [Intel-gfx] [PATCH 1/5] drm/i915/display: Move display device info to header " Matt Roper
2023-05-18  5:19   ` [Intel-gfx] [Intel-xe] " Lucas De Marchi
2023-05-18  6:18   ` [Intel-gfx] " Andrzej Hajda
2023-05-18  3:18 ` [Intel-gfx] [PATCH 2/5] drm/i915: Convert INTEL_INFO()->display to a pointer Matt Roper
2023-05-18  5:24   ` [Intel-gfx] [Intel-xe] " Lucas De Marchi
2023-05-18  6:44   ` [Intel-gfx] " Andrzej Hajda
2023-05-18  3:18 ` [Intel-gfx] [PATCH 3/5] drm/i915/display: Move display runtime info to display structure Matt Roper
2023-05-18  7:56   ` Andrzej Hajda
2023-05-22 16:41     ` Matt Roper [this message]
2023-05-18  3:18 ` [Intel-gfx] [PATCH 4/5] drm/i915/display: Make display responsible for probing its own IP Matt Roper
2023-05-18 10:01   ` Andrzej Hajda
2023-05-18  3:18 ` [Intel-gfx] [PATCH 5/5] drm/i915/display: Handle GMD_ID identification in display code Matt Roper
2023-05-18  7:53   ` kernel test robot
2023-05-18  9:28   ` kernel test robot
2023-05-18 10:44   ` Andrzej Hajda
2023-05-22 19:10     ` Matt Roper
2023-05-18  4:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Move display identification/probing under display/ Patchwork
2023-05-18  4:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-05-18  4:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-18 15:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230522164149.GI10045@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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