From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/xe: Add missing HPD interrupt enabling during non-d3cold RPM resume
Date: Mon, 7 Oct 2024 14:52:22 -0400 [thread overview]
Message-ID: <ZwQt5t9iR9mYLsWR@intel.com> (raw)
In-Reply-To: <ZwQsnaXxhGOPLO9T@ideak-desk.fi.intel.com>
On Mon, Oct 07, 2024 at 09:46:53PM +0300, Imre Deak wrote:
> On Mon, Oct 07, 2024 at 09:29:46PM +0300, Cavitt, Jonathan wrote:
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Imre Deak
> > Sent: Monday, October 7, 2024 7:06 AM
> > To: intel-xe@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> > Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Subject: [PATCH 2/2] drm/xe: Add missing HPD interrupt enabling during non-d3cold RPM resume
> > >
> > > Atm the display HPD interrupts that got disabled during runtime
> > > suspend, are re-enabled only if d3cold is enabled. Fix things by
> > > also re-enabling the interrupts if d3cold is disabled.
> > >
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Signed-off-by: Imre Deak <imre.deak@intel.com>
> >
> > Is there a reason this ended up as a separate patch?
>
> On the principle of doing one thing in one patch: the first is
> refactoring, this one is a fix.
We do need this, but we need a lot more.
Please help on the review of the consolidation and the true split:
https://lore.kernel.org/intel-xe/20240924204222.246862-1-rodrigo.vivi@intel.com/T/#m482df5716f81e6f6a3b5f459f57f193a4292ab52
>
> > Not blocking, just curious.
> > Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> > -Jonathan Cavitt
> >
> > > ---
> > > drivers/gpu/drm/xe/display/xe_display.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> > > index cb2449b7921ac..695c27ac6b0f8 100644
> > > --- a/drivers/gpu/drm/xe/display/xe_display.c
> > > +++ b/drivers/gpu/drm/xe/display/xe_display.c
> > > @@ -486,6 +486,7 @@ void xe_display_pm_runtime_resume(struct xe_device *xe)
> > > return;
> > > }
> > >
> > > + intel_hpd_init(xe);
> > > intel_hpd_poll_disable(xe);
> > > }
> > >
> > > --
> > > 2.44.2
> > >
> > >
next prev parent reply other threads:[~2024-10-07 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:05 [PATCH 1/2] drm/xe: Separate the d3cold and non-d3cold runtime PM handling Imre Deak
2024-10-07 14:05 ` [PATCH 2/2] drm/xe: Add missing HPD interrupt enabling during non-d3cold RPM resume Imre Deak
2024-10-07 18:29 ` Cavitt, Jonathan
2024-10-07 18:46 ` Imre Deak
2024-10-07 18:52 ` Rodrigo Vivi [this message]
2024-10-08 15:33 ` Imre Deak
2024-10-08 20:21 ` Rodrigo Vivi
2024-10-07 18:28 ` [PATCH 1/2] drm/xe: Separate the d3cold and non-d3cold runtime PM handling Cavitt, Jonathan
2024-10-07 18:45 ` Imre Deak
2024-10-08 4:18 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2024-10-09 5:29 ` ✗ Fi.CI.IGT: failure " Patchwork
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=ZwQt5t9iR9mYLsWR@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@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