From: Abhinav Kumar <abhinavk@codeaurora.org>
To: igt-dev@lists.freedesktop.org
Cc: petri.latvala@intel.com, swboyd@chromium.org,
khsieh@codeaurora.org, nganji@codeaurora.org,
seanpaul@chromium.org, tanmay@codeaurora.org,
aravindh@codeaurora.org
Subject: [igt-dev] [PATCH i-g-t v2 0/5] Add support for video pattern DP CTS for MSM chipsets
Date: Tue, 15 Sep 2020 12:56:09 -0700 [thread overview]
Message-ID: <20200915195614.7618-1-abhinavk@codeaurora.org> (raw)
This series adds support for video pattern DP compliance tests for
MSM chipsets. The driver side changes for this have been pushed here [1].
The changes mostly involve cleanup to move useful APIs to common libs so
that other compliance modules can use them and also leveraging the design
of intel_dp_compliance to add support for video pattern tests for MSM
chipsets.
[1] https://patchwork.kernel.org/project/dri-devel/list/?series=347839
Changes in v2:
- add some documentation for the new lib APIs
- fix indentation in the meson file
Abhinav Kumar (5):
tools: rename intel_dp_compliance_hotplug to igt_dp_compliance_hotplug
lib/igt_kms: move some of the useful dump functions to igt_kms
lib/igt_fb: move the CTS fill framebuffer to igt_fb lib
tools: move terminal utility functions to a separate file
tools: add support for msm_dp_compliance to IGT
lib/igt_fb.c | 65 ++
lib/igt_fb.h | 3 +
lib/igt_kms.c | 92 ++
lib/igt_kms.h | 22 +
tools/Makefile.am | 4 +
tools/Makefile.sources | 11 +-
tools/igt_compliance_utils.c | 82 ++
...el_dp_compliance.h => igt_dp_compliance.h} | 13 +-
..._hotplug.c => igt_dp_compliance_hotplug.c} | 9 +-
tools/intel_dp_compliance.c | 216 +----
tools/meson.build | 15 +-
tools/msm_dp_compliance.c | 812 ++++++++++++++++++
12 files changed, 1135 insertions(+), 209 deletions(-)
create mode 100644 tools/igt_compliance_utils.c
rename tools/{intel_dp_compliance.h => igt_dp_compliance.h} (80%)
rename tools/{intel_dp_compliance_hotplug.c => igt_dp_compliance_hotplug.c} (93%)
create mode 100644 tools/msm_dp_compliance.c
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-09-15 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 19:56 Abhinav Kumar [this message]
2020-09-15 19:56 ` [igt-dev] [PATCH i-g-t v2 2/5] lib/igt_kms: move some of the useful dump functions to igt_kms Abhinav Kumar
2020-09-16 8:14 ` Petri Latvala
2020-09-16 8:38 ` Petri Latvala
2020-09-15 19:56 ` [igt-dev] [PATCH i-g-t v2 3/5] lib/igt_fb: move the CTS fill framebuffer to igt_fb lib Abhinav Kumar
2020-09-15 19:56 ` [igt-dev] [PATCH i-g-t v2 4/5] tools: move terminal utility functions to a separate file Abhinav Kumar
2020-09-15 19:56 ` [igt-dev] [PATCH i-g-t v2 5/5] tools: add support for msm_dp_compliance to IGT Abhinav Kumar
2020-09-15 20:46 ` [igt-dev] ✓ Fi.CI.BAT: success for Add support for video pattern DP CTS for MSM chipsets (rev2) Patchwork
2020-09-16 1:00 ` [igt-dev] ✗ Fi.CI.IGT: 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=20200915195614.7618-1-abhinavk@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=aravindh@codeaurora.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=khsieh@codeaurora.org \
--cc=nganji@codeaurora.org \
--cc=petri.latvala@intel.com \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=tanmay@codeaurora.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