intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2] drm/xe/display: Print display ip version
Date: Wed, 06 Sep 2023 11:50:10 +0300	[thread overview]
Message-ID: <87r0nbheil.fsf@intel.com> (raw)
In-Reply-To: <20230906061449.4147094-1-balasubramani.vivekanandan@intel.com>

On Wed, 06 Sep 2023, Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com> wrote:
> Print display ip version during module load
>
> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pci.c | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 60f3474844e2..60927ad7fa27 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -844,6 +844,13 @@ static int xe_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>  		str_yes_no(xe->info.enable_display),
>  		xe->info.dma_mask_size, xe->info.tile_count);
>  
> +#if IS_ENABLED(CONFIG_DRM_XE_DISPLAY)
> +	if (xe->info.enable_display)
> +		drm_dbg(&xe->drm, "Display: %d.%02d\n",
> +			xe->info.display_runtime.ip.ver,
> +			xe->info.display_runtime.ip.rel);
> +#endif

Please don't mix non-display and display code.

Absolutely *nothing* in xe top level should touch any display
structures. (xe_display.c is the obvious exception, but that should be
moved under display/ too.)

The display code has intel_display_device_info_print(), i915 uses that
to dump the relevant information, so should xe.

Side note, I also don't think a high level function like xe_pci_probe()
should do any debug printing like it currently does. It should all be
abstracted away.


BR,
Jani.

> +
>  	drm_dbg(&xe->drm, "Stepping = (G:%s, M:%s, D:%s, B:%s)\n",
>  		xe_step_name(xe->info.step.graphics),
>  		xe_step_name(xe->info.step.media),

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2023-09-06  8:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  6:14 [Intel-xe] [PATCH v2] drm/xe/display: Print display ip version Balasubramani Vivekanandan
2023-09-06  6:12 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/display: Print display ip version (rev2) Patchwork
2023-09-06  6:12 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-06  6:13 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-06  6:20 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-06  6:20 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-06  6:22 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-09-06  8:50 ` Jani Nikula [this message]
2023-09-06  8:51 ` [Intel-xe] [PATCH v2] drm/xe/display: Print display ip version Jani Nikula
2023-09-07 18:03 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/display: Print display ip version (rev3) Patchwork
2023-09-07 18:03 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-07 18:04 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-07 18:11 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-07 18:12 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-07 18:13 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-07 18:45 ` [Intel-xe] ✓ CI.BAT: " 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=87r0nbheil.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).