From: Kunal Joshi <kunal1.joshi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: [PATCH i-g-t 7/9] lib/igt_kms: add function to check force link training failure support
Date: Mon, 10 Jun 2024 02:55:33 +0530 [thread overview]
Message-ID: <20240609212535.868832-8-kunal1.joshi@intel.com> (raw)
In-Reply-To: <20240609212535.868832-1-kunal1.joshi@intel.com>
add function to check if output supports forcing link training failures
Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
---
lib/igt_kms.c | 23 +++++++++++++++++++++++
lib/igt_kms.h | 1 +
2 files changed, 24 insertions(+)
diff --git a/lib/igt_kms.c b/lib/igt_kms.c
index 4b354826d..be5d7d4fa 100644
--- a/lib/igt_kms.c
+++ b/lib/igt_kms.c
@@ -6933,3 +6933,26 @@ void igt_read_link_training_info(int drm_fd, igt_output_t *output,
&link_training_info->seq_train_failures) == 5);
link_training_info->retrain_disabled = strcmp(retrain_disabled_buf, "yes") == 0;
}
+
+/**
+ * Checks if the force link training failure debugfs
+ * is available for a specific output.
+ *
+ * @drmfd: file descriptor of the DRM device.
+ * @output: output to check.
+ * Returns:
+ * true if the debugfs is available, false otherwise.
+ */
+bool igt_has_force_link_training_failure_debugfs(int drmfd, igt_output_t *output)
+{
+ int debugfs_fd, ret;
+ char buf[512];
+
+ igt_assert_f(output->name, "Invalid output\n");
+ debugfs_fd = igt_debugfs_connector_dir(drmfd, output->name, O_RDONLY);
+ if (debugfs_fd < 0)
+ return false;
+ ret = igt_debugfs_simple_read(debugfs_fd, "i915_dp_force_link_training_failure", buf, sizeof(buf));
+ close(debugfs_fd);
+ return ret >= 0;
+}
diff --git a/lib/igt_kms.h b/lib/igt_kms.h
index 9301df1e2..58dd90b85 100644
--- a/lib/igt_kms.h
+++ b/lib/igt_kms.h
@@ -1268,5 +1268,6 @@ enum dp_link_rate igt_get_dp_max_link_rate(int drm_fd, igt_output_t *output);
enum dp_lane_count igt_get_dp_max_lane_count(int drm_fd, igt_output_t *output);
void igt_read_link_training_info(int drm_fd, igt_output_t *output,
struct dp_link_training_info *link_training_info);
+bool igt_has_force_link_training_failure_debugfs(int drmfd, igt_output_t *output);
#endif /* __IGT_KMS_H__ */
--
2.43.0
next prev parent reply other threads:[~2024-06-09 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 21:25 [PATCH i-g-t 0/9] add test to validate fallback Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 1/9] lib/igt_kms: add data structures for link rate, lane count and training info Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 2/9] lib/igt_kms: add function to get/set a target link rate/lane count Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 3/9] lib/igt_kms: add function to get max " Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 4/9] lib/igt_kms: add function to force link training failure Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 5/9] lib/igt_kms: add function to force link retrain Kunal Joshi
2024-06-09 21:25 ` [PATCH i-g-t 6/9] lib/igt_kms: add function to get link training info Kunal Joshi
2024-06-09 21:25 ` Kunal Joshi [this message]
2024-06-09 21:25 ` [PATCH i-g-t 8/9] tests/intel/kms_dp_fallback: add test for validating fallback Kunal Joshi
2024-08-20 3:23 ` Reddy Guddati, Santhosh
2024-06-09 21:25 ` [PATCH i-g-t 9/9] HAX: do not merge Kunal Joshi
2024-06-09 21:54 ` ✓ Fi.CI.BAT: success for add test to validate fallback Patchwork
2024-06-09 22:02 ` ✓ CI.xeBAT: " Patchwork
2024-06-09 22:55 ` ✗ CI.xeFULL: failure " Patchwork
2024-06-09 23:04 ` ✗ Fi.CI.IGT: " 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=20240609212535.868832-8-kunal1.joshi@intel.com \
--to=kunal1.joshi@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