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 0/5] drm/dp: Fix link training interrupted by HPD pulse
Date: Wed, 26 Feb 2025 14:55:32 +0200 [thread overview]
Message-ID: <87jz9c50hn.fsf@intel.com> (raw)
In-Reply-To: <20250224193115.2058512-1-imre.deak@intel.com>
On Mon, 24 Feb 2025, Imre Deak <imre.deak@intel.com> wrote:
> This patchset fixes a problem during Display Port link training, where
> the link training is interrupted by a short HPD pulse generated by the
> sink. Generally the sink signals a bad link state via such short pulses,
> but the sink should prevent such signaling during link training.
>
> Some sinks do generate a short pulse as above during link training, or a
> pulse generated before the link training started may be handled from a
> scheduled work during link training. Such a handling may interfere with
> the link training (see patch 3 for the reason), so this patchset
> prevents the handling of pulses during link training.
I'm wondering if this series is made unnecessarily complicated by
blocking the hotplug handling at the hpd pin level, while what is
actually needed is blocking at the encoder level. I believe that would
be simpler too.
Thoughts?
BR,
Jani.
>
> Imre Deak (5):
> drm/i915/hpd: Let an HPD pin be in the disabled state when handling
> missed IRQs
> drm/i915/hpd: Add support for suspending the IRQ handling on an HPD
> pin
> drm/i915/dp: Fix link training interrupted by a short HPD pulse
> drm/i915/dp: Queue a link check after link training is complete
> drm/i915/crt: Use intel_hpd_suspend/resume() instead of
> intel_hpd_disable/enable()
>
> drivers/gpu/drm/i915/display/intel_crt.c | 7 +-
> .../gpu/drm/i915/display/intel_display_core.h | 2 +
> .../drm/i915/display/intel_dp_link_training.c | 23 +-
> drivers/gpu/drm/i915/display/intel_hotplug.c | 264 ++++++++++++++----
> drivers/gpu/drm/i915/display/intel_hotplug.h | 5 +-
> 5 files changed, 237 insertions(+), 64 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-26 12:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 19:31 [PATCH 0/5] drm/dp: Fix link training interrupted by HPD pulse Imre Deak
2025-02-24 19:31 ` [PATCH 1/5] drm/i915/hpd: Let an HPD pin be in the disabled state when handling missed IRQs Imre Deak
2025-02-24 19:31 ` [PATCH 2/5] drm/i915/hpd: Add support for suspending the IRQ handling on an HPD pin Imre Deak
2025-02-25 12:15 ` [PATCH v2 " Imre Deak
2025-02-25 16:25 ` Jani Nikula
2025-02-25 17:15 ` Imre Deak
2025-02-24 19:31 ` [PATCH 3/5] drm/i915/dp: Fix link training interrupted by a short HPD pulse Imre Deak
2025-02-24 19:31 ` [PATCH 4/5] drm/i915/dp: Queue a link check after link training is complete Imre Deak
2025-02-24 19:31 ` [PATCH 5/5] drm/i915/crt: Use intel_hpd_suspend/resume() instead of intel_hpd_disable/enable() Imre Deak
2025-02-25 12:15 ` [PATCH v2 " Imre Deak
2025-02-25 1:54 ` ✓ CI.Patch_applied: success for drm/dp: Fix link training interrupted by HPD pulse Patchwork
2025-02-25 1:54 ` ✓ CI.checkpatch: " Patchwork
2025-02-25 1:56 ` ✓ CI.KUnit: " Patchwork
2025-02-25 2:12 ` ✓ CI.Build: " Patchwork
2025-02-25 2:14 ` ✓ CI.Hooks: " Patchwork
2025-02-25 2:16 ` ✗ CI.checksparse: warning " Patchwork
2025-02-25 2:35 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-25 6:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-25 12:20 ` ✓ CI.Patch_applied: success for drm/dp: Fix link training interrupted by HPD pulse (rev3) Patchwork
2025-02-25 12:20 ` ✓ CI.checkpatch: " Patchwork
2025-02-25 12:21 ` ✓ CI.KUnit: " Patchwork
2025-02-25 12:38 ` ✓ CI.Build: " Patchwork
2025-02-25 12:40 ` ✓ CI.Hooks: " Patchwork
2025-02-25 12:42 ` ✗ CI.checksparse: warning " Patchwork
2025-02-25 12:59 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-25 19:15 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-26 12:55 ` Jani Nikula [this message]
2025-02-26 13:17 ` [PATCH 0/5] drm/dp: Fix link training interrupted by HPD pulse Imre Deak
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=87jz9c50hn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox