From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "Deak, Imre" <imre.deak@intel.com>,
"Hogander, Jouni" <jouni.hogander@intel.com>
Subject: Re: [PATCH v2 3/5] drm/i915/irq: conditional HPD IRQ resets based on PME capability
Date: Fri, 4 Sep 2026 12:12:09 +0000 [thread overview]
Message-ID: <e305f861017d4387e874f28bedc55791af960b79.camel@intel.com> (raw)
In-Reply-To: <37c640934163bd6849303500f4e7662e49b4d784@intel.com>
On Fri, 2026-09-04 at 12:56 +0300, Jani Nikula wrote:
> On Thu, 03 Sep 2026, Vinod Govindapillai
> <vinod.govindapillai@intel.com> wrote:
> > If a device supports generating PME from HPDs, resetting HPD IRQs
> > will be counter productive as HPDs itself will be lost. During
> > suspend routines, all the IRQs are reset. So if the device is
> > capable of generating PME rom HPDs, keep the HPD related IRQs from
> > reset based on the PME capability of the device on a target power
> > state. PME capability will be assessed and updated separately.
> >
> > Bspec: 52979, 52980, 68857, 68867, 68970
> > Assisted-by: GitHub_Copilot:claude-opus-5
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > .../gpu/drm/i915/display/intel_display_irq.c | 20 ++++++++++++---
> > ----
> > 1 file changed, 13 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.c
> > b/drivers/gpu/drm/i915/display/intel_display_irq.c
> > index a59b75830bd1..fc50b19d5ddf 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_irq.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_irq.c
> > @@ -22,6 +22,7 @@
> > #include "intel_fdi_regs.h"
> > #include "intel_fifo_underrun.h"
> > #include "intel_gmbus.h"
> > +#include "intel_hotplug.h"
> > #include "intel_hotplug_irq.h"
> > #include "intel_lpe_audio.h"
> > #include "intel_parent.h"
> > @@ -2217,8 +2218,11 @@ static void gen11_display_irq_reset(struct
> > intel_display *display)
> > enum pipe pipe;
> > u32 trans_mask = BIT(TRANSCODER_A) | BIT(TRANSCODER_B) |
> > BIT(TRANSCODER_C) | BIT(TRANSCODER_D);
> > + /* If HPD can generate PME, we don't want to reset HPD
> > related IRQs */
>
> Please don't add comments in the middle of the declarations. IMO it's
> a
> distraction rather than helpful.
Ack. Forgot to remove that!
>
> To be fair, one comment like this here or there would be fine, but it
> takes only a few to set an example both for humans and the language
> models to start littering the declarations with comments, and I don't
> want that.
>
> > + bool keep_hpd = intel_hpd_can_generate_pme(display);
>
> bool reset_hpd = !intel_hpd_can_generate_pme(display);
>
> IMO this would be more clear.
Okay. Will update.
BR
vinod
>
> > - intel_de_write(display, GEN11_DISPLAY_INT_CTL, 0);
> > + if (!keep_hpd)
> > + intel_de_write(display, GEN11_DISPLAY_INT_CTL, 0);
> >
> > if (DISPLAY_VER(display) >= 12) {
> > enum transcoder trans;
> > @@ -2250,13 +2254,15 @@ static void gen11_display_irq_reset(struct
> > intel_display *display)
> > irq_reset(display, GEN8_DE_PORT_IRQ_REGS);
> > irq_reset(display, GEN8_DE_MISC_IRQ_REGS);
> >
> > - if (DISPLAY_VER(display) >= 14)
> > - irq_reset(display, PICAINTERRUPT_IRQ_REGS);
> > - else
> > - irq_reset(display, GEN11_DE_HPD_IRQ_REGS);
> > + if (!keep_hpd) {
> > + if (DISPLAY_VER(display) >= 14)
> > + irq_reset(display,
> > PICAINTERRUPT_IRQ_REGS);
> > + else
> > + irq_reset(display, GEN11_DE_HPD_IRQ_REGS);
> >
> > - if (INTEL_PCH_TYPE(display) >= PCH_ICP)
> > - irq_reset(display, SDE_IRQ_REGS);
> > + if (INTEL_PCH_TYPE(display) >= PCH_ICP)
> > + irq_reset(display, SDE_IRQ_REGS);
> > + }
> > }
> >
> > void gen8_irq_power_well_post_enable(struct intel_display
> > *display,
>
next prev parent reply other threads:[~2026-09-04 12:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 8:04 [PATCH v2 0/5] PM_PME support on display hotplug Vinod Govindapillai
2026-09-03 8:04 ` [PATCH v2 1/5] drm/xe/pm: initialize the device's system wakeup capabilities Vinod Govindapillai
2026-09-03 8:15 ` sashiko-bot
2026-09-03 8:04 ` [PATCH v2 2/5] drm/i915/hotplug: add helpers to track HPDs can generate PME Vinod Govindapillai
2026-09-03 8:04 ` [PATCH v2 3/5] drm/i915/irq: conditional HPD IRQ resets based on PME capability Vinod Govindapillai
2026-09-03 8:32 ` sashiko-bot
2026-09-04 9:56 ` Jani Nikula
2026-09-04 12:12 ` Govindapillai, Vinod [this message]
2026-09-03 8:04 ` [PATCH v2 4/5] drm/i915/hotplug: avoid HPD polling if the device is PME capable Vinod Govindapillai
2026-09-03 8:04 ` [PATCH v2 5/5] drm/xe/pm: handle the PME capability and runtime pm routines Vinod Govindapillai
2026-09-03 12:36 ` [PATCH v3 " Vinod Govindapillai
2026-09-04 10:03 ` [PATCH v2 " Jani Nikula
2026-09-03 8:13 ` ✓ CI.KUnit: success for pm_pme support on display hotplug (rev3) Patchwork
2026-09-03 8:52 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-03 12:45 ` ✓ CI.KUnit: success for pm_pme support on display hotplug (rev4) Patchwork
2026-09-03 13:46 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-04 0:04 ` ✗ Xe.CI.FULL: 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=e305f861017d4387e874f28bedc55791af960b79.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jouni.hogander@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