From: Jani Nikula <jani.nikula@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v5 2/6] drm/i915/hpd: Let an HPD pin be in the disabled state when handling missed IRQs
Date: Tue, 04 Mar 2025 18:08:54 +0200 [thread overview]
Message-ID: <871pvczskp.fsf@intel.com> (raw)
In-Reply-To: <20250304152917.3407080-3-imre.deak@intel.com>
On Tue, 04 Mar 2025, Imre Deak <imre.deak@intel.com> wrote:
> After suspending and resuming the detection on connectors, HPD IRQs that
> arrived while the detection was suspended, are handled by scheduling the
> intel_hotplug::hotplug work for them. All HPD pins must be at this point
> in either the HPD_ENABLED (set for all pins during driver loading/system
> resuming) or HPD_MARK_DISABLED (set by IRQ storm detection) state: the
> HPD_DISABLED state for a pin can be set only from the HPD_MARK_DISABLED
> state by the hotplug work after a storm detection (enabling polling on
> the given pin/connector), however the hotplug work won't be scheduled
> while the detection is suspended.
>
> A follow-up change will add support for blocking the HPD IRQ handling
> on a given HPD pin (without disabling the IRQ generation on it), after
> which it becomes possible to see a pin in the HPD_DISABLED state when
> unblocking the IRQ handling (since the blocking could've happened for an
> already disabled pin). Adjust queue_work_for_missed_irqs() accordingly,
> so that this function can be reused for unblocking the IRQ handling.
>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hotplug.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hotplug.c b/drivers/gpu/drm/i915/display/intel_hotplug.c
> index 9692b5c01aea9..3fb5feeefa144 100644
> --- a/drivers/gpu/drm/i915/display/intel_hotplug.c
> +++ b/drivers/gpu/drm/i915/display/intel_hotplug.c
> @@ -980,6 +980,7 @@ static void queue_work_for_missed_irqs(struct drm_i915_private *i915)
> case HPD_MARK_DISABLED:
> queue_work = true;
> break;
> + case HPD_DISABLED:
> case HPD_ENABLED:
> break;
> default:
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-03-04 16:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 15:29 [PATCH v5 0/6] drm/i915/dp: Fix link training interrupted by HPD pulse Imre Deak
2025-03-04 15:29 ` [PATCH v5 1/6] drm/i915/hpd: Track HPD pins instead of ports for HPD pulse events Imre Deak
2025-03-04 16:08 ` Jani Nikula
2025-03-04 15:29 ` [PATCH v5 2/6] drm/i915/hpd: Let an HPD pin be in the disabled state when handling missed IRQs Imre Deak
2025-03-04 16:08 ` Jani Nikula [this message]
2025-03-04 15:29 ` [PATCH v5 3/6] drm/i915/hpd: Add support for blocking the IRQ handling on an HPD pin Imre Deak
2025-03-04 17:02 ` Jani Nikula
2025-03-04 19:50 ` Imre Deak
2025-03-05 11:48 ` [PATCH v6 " Imre Deak
2025-03-07 12:32 ` Jani Nikula
2025-03-04 15:29 ` [PATCH v5 4/6] drm/i915/dp: Fix link training interrupted by a short HPD pulse Imre Deak
2025-03-04 17:03 ` Jani Nikula
2025-03-04 15:29 ` [PATCH v5 5/6] drm/i915/dp: Queue a link check after link training is complete Imre Deak
2025-03-04 17:56 ` Jani Nikula
2025-03-04 19:59 ` Imre Deak
2025-03-05 11:48 ` [PATCH v6 " Imre Deak
2025-03-04 15:29 ` [PATCH v5 6/6] drm/i915/crt: Use intel_hpd_block/unblock() instead of intel_hpd_disable/enable() Imre Deak
2025-03-07 12:34 ` Jani Nikula
2025-03-04 16:22 ` ✓ CI.Patch_applied: success for drm/i915/dp: Fix link training interrupted by HPD pulse Patchwork
2025-03-04 16:23 ` ✓ CI.checkpatch: " Patchwork
2025-03-04 16:24 ` ✓ CI.KUnit: " Patchwork
2025-03-04 16:40 ` ✓ CI.Build: " Patchwork
2025-03-04 16:43 ` ✓ CI.Hooks: " Patchwork
2025-03-04 16:46 ` ✗ CI.checksparse: warning " Patchwork
2025-03-04 17:04 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-04 18:05 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-04 18:20 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2025-03-04 18:42 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-05 18:13 ` ✗ Fi.CI.SPARSE: warning for drm/i915/dp: Fix link training interrupted by HPD pulse (rev3) Patchwork
2025-03-05 18:18 ` ✓ CI.Build: success " Patchwork
2025-03-05 18:20 ` ✓ CI.Hooks: " Patchwork
2025-03-05 18:22 ` ✗ CI.checksparse: warning " Patchwork
2025-03-05 18:40 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-05 18:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-05 19:59 ` ✗ Xe.CI.Full: failure for drm/i915/dp: Fix link training interrupted by HPD pulse (rev2) Patchwork
2025-03-05 21:11 ` ✗ i915.CI.Full: failure for drm/i915/dp: Fix link training interrupted by HPD pulse (rev3) Patchwork
2025-03-11 14:37 ` Imre Deak
2025-03-05 21:27 ` ✗ Xe.CI.Full: " 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=871pvczskp.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.