From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Vinod Govindapillai <vinod.govindapillai@intel.com>,
Imre Deak <imre.deak@intel.com>
Subject: Re: [PATCH 0/4] drm/xe/display: Clean-up PM sequences
Date: Wed, 04 Sep 2024 12:02:28 +0300 [thread overview]
Message-ID: <87wmjrssez.fsf@intel.com> (raw)
In-Reply-To: <20240903223803.380711-1-rodrigo.vivi@intel.com>
On Tue, 03 Sep 2024, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> This series aim to bring a bit of clarity in the display PM
> sequences and start a clean-up around the runtime_pm ones.
>
> Specially around D3Cold. There are some ongoing discussions
> that we wouldn't need all the sequences that we currently have.
>
> So, let's at least split them up to separate functions so
> we can individually scrutinize.
>
> For now, I removed what I'm sure that we don't need in a
> d3cold scenario where we lose power and that I could
> validate in my DG2. Any other attempt to clean-up further
> at my end failed badly DG2's d3cold.
>
> But again, let's at least bring some clarity on the
> sequences before we go even further.
Taking a step back, I can't help but feel this is stuff that should
really happen at i915 display level.
Yes, i915 calls display all over the place in i915_driver.c. Just look
at the display/ includes there.
xe now duplicates that in xe_display.c. It's kind of better, but really
not.
We should have one clean interface to display probe/cleanup and
(runtime) suspend/resume used by both drivers, instead of adding
slightly different glue layers to both, each directly calling various
parts of display.
I get that this clarifies xe_display.c, but that should also ditch
almost all of the direct display includes.
BR,
Jani.
>
> Cc: Vinod Govindapillai <vinod.govindapillai@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
>
> Rodrigo Vivi (4):
> drm/xe/display: Spin-off xe_display runtime/d3cold sequences
> drm/xe/display: Remove i915_drv.h include
> drm/xe/display: Kill useless has_display
> drm/xe/display: Reduce and streamline d3cold display sequence
>
> drivers/gpu/drm/xe/display/xe_display.c | 109 ++++++++++++++----------
> drivers/gpu/drm/xe/display/xe_display.h | 8 +-
> drivers/gpu/drm/xe/xe_pm.c | 8 +-
> 3 files changed, 74 insertions(+), 51 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-04 9:08 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
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 ` Jani Nikula [this message]
2024-09-04 15:16 ` [PATCH 0/4] " 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=87wmjrssez.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=vinod.govindapillai@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;
as well as URLs for NNTP newsgroup(s).