From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/display: Print display ip version
Date: Fri, 08 Sep 2023 13:11:43 +0300 [thread overview]
Message-ID: <871qf9gejk.fsf@intel.com> (raw)
In-Reply-To: <26hcp33tuu24jtl2tyo7iyqaucnkbww3sd4na4k5boa577eof4@axnzegfuxdya>
On Wed, 06 Sep 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Wed, Sep 06, 2023 at 11:04:57AM -0700, Matt Roper wrote:
>>On Wed, Sep 06, 2023 at 11:34:00AM +0530, Balasubramani Vivekanandan wrote:
>>> Print display ip version during module load
>>>
>>> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
>>> ---
>>> drivers/gpu/drm/xe/xe_pci.c | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
>>> index 60f3474844e2..fc01544346d5 100644
>>> --- a/drivers/gpu/drm/xe/xe_pci.c
>>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>>> @@ -844,6 +844,11 @@ 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 (xe->info.enable_display)
>>> + drm_dbg(&xe->drm, "Display: %d.%02d\n",
>>> + xe->info.display_runtime.ip.ver,
>>> + xe->info.display_runtime.ip.rel);
>>> +
>>
>>Rather than printing the display version here, it might be better to
>>call intel_display_device_info_print() somewhere appropriate which will
>
> Somewhere appropriate would be xe_display.c, so it only gets printed if
> there is display.... or if it's moved to a shared function in i915
> itself that we already call.
https://lore.kernel.org/r/87r0nbheil.fsf@intel.com
>
> Lucas De Marchi
>
>>dump not only the IP version, but also the relevant feature flags.
>>
>>
>>Matt
>>
>>> 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),
>>> --
>>> 2.25.1
>>>
>>
>>--
>>Matt Roper
>>Graphics Software Engineer
>>Linux GPU Platform Enablement
>>Intel Corporation
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-09-08 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 6:04 [Intel-xe] [PATCH] drm/xe/display: Print display ip version Balasubramani Vivekanandan
2023-09-06 6:02 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-06 6:02 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-06 6:03 ` [Intel-xe] ✗ CI.KUnit: failure " Patchwork
2023-09-06 18:04 ` [Intel-xe] [PATCH] " Matt Roper
2023-09-06 18:49 ` Lucas De Marchi
2023-09-08 10:11 ` Jani Nikula [this message]
2023-09-08 13:17 ` Lucas De Marchi
2023-09-08 16:50 ` Jani Nikula
2023-09-08 17:11 ` Lucas De Marchi
2023-09-06 18:39 ` Rodrigo Vivi
2023-09-08 10:11 ` Jani Nikula
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=871qf9gejk.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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