From: Imre Deak <imre.deak@intel.com>
To: Kunal Joshi <kunal1.joshi@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 02/14] lib/igt_kms: add helper to get current link rate/ lane count for connector
Date: Tue, 3 Sep 2024 16:08:36 +0300 [thread overview]
Message-ID: <ZtcKVEMveXWJVCO9@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20240825200612.4036178-3-kunal1.joshi@intel.com>
On Mon, Aug 26, 2024 at 01:36:00AM +0530, Kunal Joshi wrote:
> i915_dp_force_(lane_count/link_rate) debugfs files expoose
> current link rate/lane count for connector.add helper to get
> current link rate/ lane count for connector
>
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
> lib/igt_kms.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++
> lib/igt_kms.h | 2 ++
> 2 files changed, 60 insertions(+)
>
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index dd530dbab..4ef7f4d7f 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -6705,3 +6705,61 @@ int get_num_scalers(igt_display_t *display, enum pipe pipe)
>
> return num_scalers;
> }
> +
> +/**
> + * igt_get_dp_link_rate_set_for_output:
> + * @drm_fd: A drm file descriptor
> + * @output: Target output
> + *
> + * Returns: Link rate set for the output.
> + */
> +enum dp_link_rate igt_get_dp_link_rate_set_for_output(int drm_fd, igt_output_t *output)
> +{
> + char buf[512];
> + int dir, res;
> + int link_rate;
> +
> + igt_require_f(output->name, "Invalid output");
It's strange to check this in these library functions. I'd think the
caller should make sure already that it's a valid output, how can it
become invalid in the test this patchset adds?
> + dir = igt_debugfs_connector_dir(drm_fd, output->name, O_RDONLY);
> + igt_assert_f(dir >= 0, "Failed to open debugfs dir for connector %s\n",
> + igt_output_name(output));
> + res = igt_debugfs_simple_read(dir, "i915_dp_force_link_rate", buf, sizeof(buf));
> + close(dir);
> + igt_require(res > 0);
res == 0 is also valid.
> +
> + if (strstr(buf, "[auto]"))
> + igt_assert(sscanf(strstr(buf, "*") - 6, "%d", &link_rate) == 1);
> + else
> + igt_assert(sscanf(strstr(buf, "[") + 1, "%d", &link_rate) == 1);
I suppose this should return the rate used for an active output. It
should be the one with the '*' marker, regardless if the rate is getting
selected automatically or forced. In case it's forced the selected rate
could be different than the target with the '[]' markers (if the sink
doesn't support the target rate). So I think this should return the one
marked with '*' or an error if such is not found (when the output is
disabled).
> +
> + return link_rate;
> +}
> +
> +/**
> + * igt_get_dp_lane_count_set_for_output:
> + * @drm_fd: A drm file descriptor
> + * @output: Target output
> + *
> + * Returns: Lane count set for the output.
> + */
> +enum dp_lane_count igt_get_dp_lane_count_set_for_output(int drm_fd, igt_output_t *output)
> +{
> + char buf[512];
> + int dir, res;
> + int lane_count;
> +
> + igt_require_f(output->name, "Invalid output");
> + dir = igt_debugfs_connector_dir(drm_fd, output->name, O_RDONLY);
> + igt_assert_f(dir >= 0, "Failed to open debugfs dir for connector %s\n",
> + igt_output_name(output));
> + res = igt_debugfs_simple_read(dir, "i915_dp_force_lane_count", buf, sizeof(buf));
> + close(dir);
> + igt_require(res > 0);
> +
> + if (strstr(buf, "[auto]"))
> + igt_assert(sscanf(strstr(buf, "*") - 2, "%d", &lane_count) == 1);
> + else
> + igt_assert(sscanf(strstr(buf, "[") + 1, "%d", &lane_count) == 1);
The same as above apply in this function too.
> +
> + return lane_count;
> +}
> diff --git a/lib/igt_kms.h b/lib/igt_kms.h
> index 999921f9f..9d42a2b35 100644
> --- a/lib/igt_kms.h
> +++ b/lib/igt_kms.h
> @@ -1247,5 +1247,7 @@ bool intel_pipe_output_combo_valid(igt_display_t *display);
> bool igt_check_output_is_dp_mst(igt_output_t *output);
> int igt_get_dp_mst_connector_id(igt_output_t *output);
> int get_num_scalers(igt_display_t *display, enum pipe pipe);
> +enum dp_link_rate igt_get_dp_link_rate_set_for_output(int drm_fd, igt_output_t *output);
> +enum dp_lane_count igt_get_dp_lane_count_set_for_output(int drm_fd, igt_output_t *output);
>
> #endif /* __IGT_KMS_H__ */
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-09-03 13:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240825200612.4036178-1-kunal1.joshi@intel.com>
2024-08-25 20:05 ` [PATCH i-g-t 01/14] lib/igt_kms: add enum for link rate and lane count Kunal Joshi
2024-08-27 5:40 ` B, Jeevan
2024-09-03 12:52 ` Imre Deak
2024-09-12 5:52 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 02/14] lib/igt_kms: add helper to get current link rate/ lane count for connector Kunal Joshi
2024-08-27 5:38 ` B, Jeevan
2024-09-03 13:08 ` Imre Deak [this message]
2024-09-12 5:57 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 03/14] lib/igt_kms: add function to get max link rate/lane count Kunal Joshi
2024-08-27 5:45 ` B, Jeevan
2024-09-03 13:11 ` Imre Deak
2024-09-12 5:58 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 04/14] lib/igt_kms: add function to force link retrain Kunal Joshi
2024-08-25 20:06 ` [PATCH i-g-t 05/14] lib/igt_kms: add function to force link training failure Kunal Joshi
2024-08-25 20:06 ` [PATCH i-g-t 06/14] lib/igt_kms: add function to check if retrain disabled Kunal Joshi
2024-08-25 20:06 ` [PATCH i-g-t 07/14] lib/igt_kms: add function to check force link training failure support Kunal Joshi
2024-09-03 8:01 ` Samala, Pranay
2024-08-25 20:06 ` [PATCH i-g-t 08/14] lib/igt_kms: add helper to get pending lt failures Kunal Joshi
2024-08-25 20:06 ` [PATCH i-g-t 09/14] lib/igt_kms: add helper to get pending retrain count Kunal Joshi
2024-08-25 20:06 ` [PATCH i-g-t 10/14] lib/igt_kms: add helper to set connector link status Kunal Joshi
2024-09-03 13:56 ` Imre Deak
2024-09-12 5:59 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 11/14] lib/igt_kms: add function to reset link params Kunal Joshi
2024-09-03 14:26 ` Imre Deak
2024-09-12 6:01 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 12/14] lib/igt_kms: allow set and reset value to be same Kunal Joshi
2024-09-03 14:29 ` Imre Deak
2024-09-12 6:03 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 13/14] tests/intel/kms_dp_fallback: add test for validating fallback Kunal Joshi
2024-09-03 7:58 ` Samala, Pranay
2024-09-03 14:55 ` Imre Deak
2024-09-12 6:10 ` Joshi, Kunal1
2024-08-25 20:06 ` [PATCH i-g-t 14/14] HAX: Do not merge Kunal Joshi
2024-08-25 20:23 ` ✗ CI.xeBAT: failure for series starting with [i-g-t,01/14] lib/igt_kms: add enum for link rate and lane count Patchwork
2024-08-25 20:35 ` ✗ Fi.CI.BAT: " Patchwork
2024-08-25 21:21 ` ✗ CI.xeFULL: " Patchwork
2024-08-25 18:14 [PATCH i-g-t 00/14] add test to validate fallback Kunal Joshi
2024-08-25 18:14 ` [PATCH i-g-t 02/14] lib/igt_kms: add helper to get current link rate/ lane count for connector Kunal Joshi
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=ZtcKVEMveXWJVCO9@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@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