From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/display: Print display ip version
Date: Fri, 08 Sep 2023 19:50:45 +0300 [thread overview]
Message-ID: <87wmx0fw2i.fsf@intel.com> (raw)
In-Reply-To: <ru3jqocgwkfmhyfgdvttfwewmoducukeqhrl43shkutsyjrvru@hvyfaxmnnlqu>
On Fri, 08 Sep 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Sep 08, 2023 at 01:11:43PM +0300, Jani Nikula wrote:
>>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
>
> not sure if you are confirming what I said or saying it was wrong...
> A call to intel_display_device_info_print() in xe_display.c seems very
> reasonable.
Just trying to tie two threads of review into one in a rush. :)
Just calling intel_display_device_info_print() from somewhere, anywhere
in xe is an improvement. But perhaps it could be called from i915
display code after it's all been initialized. *shrug*
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-09-08 16:50 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
2023-09-08 13:17 ` Lucas De Marchi
2023-09-08 16:50 ` Jani Nikula [this message]
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=87wmx0fw2i.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