From: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Print display info inside driver display initialization
Date: Thu, 21 Sep 2023 14:11:17 +0530 [thread overview]
Message-ID: <ZQwBre/47G2GtOPt@bvivekan-mobl> (raw)
In-Reply-To: <878r90q8ma.fsf@intel.com>
On 21.09.2023 10:38, Jani Nikula wrote:
> On Thu, 21 Sep 2023, Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com> wrote:
> > Separate the printing of display version and feature flags from the main
> > driver probe to inside the display initialization. This is in alignment
> > with isolating the display code from the main driver and helps Xe driver
> > to resuse it.
> >
> > Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display_driver.c | 5 +++++
> > drivers/gpu/drm/i915/i915_driver.c | 2 --
> > 2 files changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.c b/drivers/gpu/drm/i915/display/intel_display_driver.c
> > index 9d9b034b9bdc..2fbb3c956336 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_driver.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_driver.c
> > @@ -380,6 +380,8 @@ int intel_display_driver_probe(struct drm_i915_private *i915)
> >
> > void intel_display_driver_register(struct drm_i915_private *i915)
> > {
> > + struct drm_printer p = drm_info_printer(i915->drm.dev);
>
> It needs to be a debug printer, not info printer, maybe:
>
> struct drm_printer p = drm_debug_printer("display info:");
>
> Unfortunately, it's not device specific, but that's for another set of
> patches another day.
Yeah, thats' the reason I deliberately used info printer. Anyway I will
resend the patch changing to debug printer.
Regards,
Bala
>
> BR,
> Jani.
>
> > +
> > if (!HAS_DISPLAY(i915))
> > return;
> >
> > @@ -407,6 +409,9 @@ void intel_display_driver_register(struct drm_i915_private *i915)
> > * fbdev->async_cookie.
> > */
> > drm_kms_helper_poll_init(&i915->drm);
> > +
> > + intel_display_device_info_print(DISPLAY_INFO(i915),
> > + DISPLAY_RUNTIME_INFO(i915), &p);
> > }
> >
> > /* part #1: call before irq uninstall */
> > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > index e5d693904123..d50347e5773a 100644
> > --- a/drivers/gpu/drm/i915/i915_driver.c
> > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > @@ -699,8 +699,6 @@ static void i915_welcome_messages(struct drm_i915_private *dev_priv)
> >
> > intel_device_info_print(INTEL_INFO(dev_priv),
> > RUNTIME_INFO(dev_priv), &p);
> > - intel_display_device_info_print(DISPLAY_INFO(dev_priv),
> > - DISPLAY_RUNTIME_INFO(dev_priv), &p);
> > i915_print_iommu_status(dev_priv, &p);
> > for_each_gt(gt, dev_priv, i)
> > intel_gt_info_print(>->info, &p);
>
> --
> Jani Nikula, Intel
prev parent reply other threads:[~2023-09-21 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:18 [Intel-gfx] [PATCH] drm/i915/display: Print display info inside driver display initialization Balasubramani Vivekanandan
2023-09-21 7:38 ` Jani Nikula
2023-09-21 8:41 ` Balasubramani Vivekanandan [this message]
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=ZQwBre/47G2GtOPt@bvivekan-mobl \
--to=balasubramani.vivekanandan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=lucas.demarchi@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