From: Kunal Joshi <kunal1.joshi@intel.com>
To: arkadiusz.hiler@intel.com, igt-dev@lists.freedesktop.org,
imre.deak@intel.com
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: [igt-dev] [PATCH v3 0/2] tests/kms_chamelium: Capture on type-c
Date: Thu, 23 Apr 2020 04:31:49 +0530 [thread overview]
Message-ID: <20200422230151.29558-1-kunal1.joshi@intel.com> (raw)
Chamelium uses HPD pulses to signal the need for a receiver reset
using DPMS cycle.Some connectors (e.g. DP over TypeC) have limitations
and will receive just a single such pulse and discard the rest.
This lasts until we disable the mode completetly and only then reenable it.
Receiver reset is always required after we set a new mode, so let's disable
the mode (reset_state() does that) before we switch to a new mode.
With this we will get the HPD pulses reliably for each iteration over
all the supoprted modes.
v2: Correction in code flow (Arek)
v3: Modified commit message. (Arek)
Kunal Joshi (2):
tests/kms_chamelium: Capture on type-c
HAX: Run in BAT
tests/intel-ci/fast-feedback.testlist | 45 ++++++++++-
tests/kms_chamelium.c | 110 +++++++++++++++++---------
2 files changed, 118 insertions(+), 37 deletions(-)
--
2.25.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-04-23 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 23:01 Kunal Joshi [this message]
2020-04-22 23:01 ` [igt-dev] [PATCH v3 1/2] tests/kms_chamelium: Capture on type-c Kunal Joshi
2020-04-22 23:01 ` [igt-dev] [PATCH v3 2/2] HAX: Run in BAT Kunal Joshi
2020-04-23 6:58 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_chamelium: Capture on type-c (rev3) Patchwork
2020-04-27 0:37 ` Kunal Joshi
2020-04-23 10:27 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_chamelium: Capture on type-c (rev4) 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=20200422230151.29558-1-kunal1.joshi@intel.com \
--to=kunal1.joshi@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=imre.deak@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