From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Deak, Imre" <imre.deak@intel.com>
Subject: Re: [PATCH 4/4] drm/xe/display: Reduce and streamline d3cold display sequence
Date: Wed, 4 Sep 2024 11:24:23 -0400 [thread overview]
Message-ID: <Zth7p73SNdnjf-z1@intel.com> (raw)
In-Reply-To: <i6uf4dy4ibedkeeb76lcx6ntwhkcik43vxc6gakdyk6ygfgl7u@3a7wfdac2lqt>
On Wed, Sep 04, 2024 at 11:09:24AM +0530, Anshuman Gupta wrote:
> On 2024-09-04 at 04:08:03 +0530, Rodrigo Vivi wrote:
> > When going to d3cold we surely don't need to flush commits,
> > nor handle fbdev. So, clean this up a bit.
> >
> > Also move the opregion call to make the function more symmetric.
> >
> > Cc: Imre Deak <imre.deak@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/xe/display/xe_display.c | 12 +++---------
> > 1 file changed, 3 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> > index daf9b9baa88a..3fd3e74f1310 100644
> > --- a/drivers/gpu/drm/xe/display/xe_display.c
> > +++ b/drivers/gpu/drm/xe/display/xe_display.c
> > @@ -310,9 +310,6 @@ static void xe_display_to_d3cold(struct xe_device *xe)
> > * properly.
> > */
> > intel_power_domains_disable(xe);
> > - intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_SUSPENDED, true);
> How do we make sure fbconsole doesn't use vram to blink the cursor ?
Good question, but that's not the point.
The point is, if the fbconsole is there blinking the cursor, we are
100% sure that this runtime suspend call here won't ever happen.
If we reach to this point. The fbconsole is not active and doesn't need
to be suspended.
>
> Thanks,
> Anshuman.
> > -
> > - xe_display_flush_cleanup_work(xe);
> >
> > intel_dp_mst_suspend(xe);
> >
> > @@ -329,18 +326,15 @@ static void xe_display_from_d3cold(struct xe_device *xe)
> >
> > intel_dmc_resume(xe);
> >
> > - drm_mode_config_reset(&xe->drm);
> > -
> > intel_display_driver_init_hw(xe);
> > +
> > + intel_opregion_resume(display);
> > +
> > intel_hpd_init(xe);
> >
> > /* MST sideband requires HPD interrupts enabled */
> > intel_dp_mst_resume(xe);
> >
> > - intel_opregion_resume(display);
> > -
> > - intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_RUNNING, false);
> > -
> > intel_power_domains_enable(xe);
> > }
> >
> > --
> > 2.46.0
> >
next prev parent reply other threads:[~2024-09-04 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 22:37 [PATCH 0/4] drm/xe/display: Clean-up PM sequences Rodrigo Vivi
2024-09-03 22:38 ` [PATCH 1/4] drm/xe/display: Spin-off xe_display runtime/d3cold sequences Rodrigo Vivi
2024-09-03 22:38 ` [PATCH 2/4] drm/xe/display: Remove i915_drv.h include Rodrigo Vivi
2024-09-04 7:27 ` Jani Nikula
2024-09-03 22:38 ` [PATCH 3/4] drm/xe/display: Kill useless has_display Rodrigo Vivi
2024-09-04 7:33 ` Jani Nikula
2024-09-04 15:22 ` Rodrigo Vivi
2024-09-04 16:08 ` Jani Nikula
2024-09-03 22:38 ` [PATCH 4/4] drm/xe/display: Reduce and streamline d3cold display sequence Rodrigo Vivi
2024-09-04 5:39 ` Anshuman Gupta
2024-09-04 15:24 ` Rodrigo Vivi [this message]
2024-09-03 22:43 ` ✓ CI.Patch_applied: success for drm/xe/display: Clean-up PM sequences Patchwork
2024-09-03 22:44 ` ✓ CI.checkpatch: " Patchwork
2024-09-03 22:45 ` ✓ CI.KUnit: " Patchwork
2024-09-03 22:57 ` ✓ CI.Build: " Patchwork
2024-09-03 22:59 ` ✓ CI.Hooks: " Patchwork
2024-09-03 23:00 ` ✓ CI.checksparse: " Patchwork
2024-09-03 23:20 ` ✓ CI.BAT: " Patchwork
2024-09-04 3:14 ` ✓ CI.FULL: " Patchwork
2024-09-04 9:02 ` [PATCH 0/4] " Jani Nikula
2024-09-04 15:16 ` Rodrigo Vivi
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=Zth7p73SNdnjf-z1@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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).