Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Govindapillai <vinod.govindapillai@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v3 0/2] Handle spurious HPDs
Date: Thu,  9 Mar 2023 10:37:49 +0200	[thread overview]
Message-ID: <20230309083751.347335-1-vinod.govindapillai@intel.com> (raw)

Some panels generate spurious HPDs during CI execution causing
random unexpected failures. There are two parts for handling
this issue - in driver and in IGT. This is for IGT.

IGT will set ignore long HPD debugfs entry to ignore long HPDs
in the driver. And then by force connect the active connectors,
we can avoid the detect hooks being executed from drm and hence
avoid random failures. The behavior is controlled using the
environment variable IGT_KMS_IGNORE_HPD. Set this var in CI
exections where panels that generate spurioud HPDs are used.

Vinod Govindapillai (2):
  lib/igt_debugfs: set provision to ignore long HPDs
  lib/igt_kms: handle spurious HPDs

 lib/igt_debugfs.c | 26 ++++++++++++++++++++++
 lib/igt_debugfs.h |  1 +
 lib/igt_kms.c     | 56 +++++++++++++++++++++++++++++++++++++++++++++--
 3 files changed, 81 insertions(+), 2 deletions(-)

-- 
2.34.1

             reply	other threads:[~2023-03-09  8:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  8:37 Vinod Govindapillai [this message]
2023-03-09  8:37 ` [igt-dev] [PATCH i-g-t v3 1/2] lib/igt_debugfs: set provision to ignore long HPDs Vinod Govindapillai
2023-03-09  8:37 ` [igt-dev] [PATCH i-g-t v3 2/2] lib/igt_kms: handle spurious HPDs Vinod Govindapillai
2023-03-09  9:36 ` [igt-dev] ✓ Fi.CI.BAT: success for Handle " Patchwork
2023-03-11  0:24 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-03-15 16:39 ` [igt-dev] ✓ Fi.CI.BAT: success for Handle spurious HPDs (rev2) Patchwork
2023-03-16  4:34 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-03-16 17:37   ` 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=20230309083751.347335-1-vinod.govindapillai@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=igt-dev@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