public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Radhakrishna Sripada <radhakrishna.sripada@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 01/11] drm/i915: Move display and media IP version to runtime info
Date: Thu, 01 Sep 2022 13:04:35 +0300	[thread overview]
Message-ID: <87zgfjbebw.fsf@intel.com> (raw)
In-Reply-To: <5a5538e3-9a79-2210-3632-483b4ee329db@intel.com>

On Thu, 01 Sep 2022, Michal Wajdeczko <michal.wajdeczko@intel.com> wrote:
> On 01.09.2022 09:45, Jani Nikula wrote:
>> On Wed, 31 Aug 2022, Radhakrishna Sripada <radhakrishna.sripada@intel.com> wrote:
>
> ...
>
>>>  	struct ip_version graphics;
>>> +	struct ip_version media;
>>> +	struct ip_version display;
>> 
>> The runtime display info is now in an unnamed struct under struct
>> intel_runtime_info below, and this belongs there.
>> 
>> There's also some pressure to name it, and "display" would be the name,
>> so this would collide.
>> 
>> Seems like all of the above are overly generic names, including the
>> pre-existing "graphics". Something to consider.
>
> maybe
>
> struct {
> 	struct {
> 		struct ip_version version;
> 		...
> 	} graphics;
>
> 	struct {
> 		struct ip_version version;
> 		...
> 	} media;
>
> 	struct {
> 		struct ip_version version;
> 		...
> 	} display;
> } runtime;
>
> then
>
> drm_printf(p, "display version: %u.%02u\n",
> 	runtime->display.version.ver,
> 	runtime->display.version.rel);

Looks good to me. The other display related stuff can be moved later.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-09-01 10:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 21:49 [Intel-gfx] [PATCH v3 00/11] Initial Meteorlake Support Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 01/11] drm/i915: Move display and media IP version to runtime info Radhakrishna Sripada
2022-09-01  7:45   ` Jani Nikula
2022-09-01  9:14     ` Michal Wajdeczko
2022-09-01 10:04       ` Jani Nikula [this message]
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 02/11] drm/i915: Read graphics/media/display arch version from hw Radhakrishna Sripada
2022-09-01  7:58   ` Jani Nikula
2022-09-01 22:06     ` Sripada, Radhakrishna
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 03/11] drm/i915: Parse and set stepping for platforms with GMD Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 04/11] drm/i915/mtl: Define engine context layouts Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 05/11] drm/i915/mtl: Add gmbus and gpio support Radhakrishna Sripada
2022-09-08 13:03   ` Balasubramani Vivekanandan
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 06/11] drm/i915/mtl: Add display power wells Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 07/11] drm/i915/mtl: Add DP AUX support on TypeC ports Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 08/11] drm/i915/mtl: Obtain SAGV values from MMIO instead of GT pcode mailbox Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 09/11] drm/i915/mtl: Update MBUS_DBOX credits Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 10/11] drm/i915/mtl: Update CHICKEN_TRANS* register addresses Radhakrishna Sripada
2022-08-31 21:49 ` [Intel-gfx] [PATCH v3 11/11] drm/i915/mtl: Do not update GV point, mask value Radhakrishna Sripada
2022-08-31 22:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Initial Meteorlake Support (rev4) Patchwork
2022-08-31 22:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-08-31 23:07 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=87zgfjbebw.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=radhakrishna.sripada@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