From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [i-g-t] tests/kms: s/i915_frequency_info/i915_display_clock_info/
Date: Wed, 12 Apr 2023 14:35:57 +0530 [thread overview]
Message-ID: <20230412090557.810996-1-bhanuprakash.modem@intel.com> (raw)
Read display specific clocks from i915_display_clock_info as
i915_frequency_info is no longer holding display specific stuff.
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
tests/i915/kms_cdclk.c | 2 +-
tests/kms_invalid_mode.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/i915/kms_cdclk.c b/tests/i915/kms_cdclk.c
index 23d9d3b02e2..778f5116f70 100644
--- a/tests/i915/kms_cdclk.c
+++ b/tests/i915/kms_cdclk.c
@@ -61,7 +61,7 @@ static int get_current_cdclk_freq(int debugfs_fd)
char *start_loc;
int res;
- res = igt_debugfs_simple_read(debugfs_fd, "i915_frequency_info",
+ res = igt_debugfs_simple_read(debugfs_fd, "i915_display_clock_info",
buf, sizeof(buf));
igt_require(res > 0);
diff --git a/tests/kms_invalid_mode.c b/tests/kms_invalid_mode.c
index 86f529e88b1..6989150c210 100644
--- a/tests/kms_invalid_mode.c
+++ b/tests/kms_invalid_mode.c
@@ -222,7 +222,7 @@ static int i915_max_dotclock(data_t *data)
if (!is_i915_device(data->drm_fd))
return 0;
- igt_debugfs_read(data->drm_fd, "i915_frequency_info", buf);
+ igt_debugfs_read(data->drm_fd, "i915_display_clock_info", buf);
s = strstr(buf, "Max pixel clock frequency:");
igt_assert(s);
igt_assert_eq(sscanf(s, "Max pixel clock frequency: %d kHz", &max_dotclock), 1);
--
2.40.0
next reply other threads:[~2023-04-12 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:05 Bhanuprakash Modem [this message]
2023-04-12 10:16 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms: s/i915_frequency_info/i915_display_clock_info/ Patchwork
2023-04-12 17:41 ` [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=20230412090557.810996-1-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@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