From: Anshuman Gupta <anshuman.gupta@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/4] lib/igt_aux: Let's use the official mem_sleep names
Date: Mon, 18 Jul 2022 11:24:46 +0530 [thread overview]
Message-ID: <20220718055445.GA32110@intel.com> (raw)
In-Reply-To: <20220713155233.1155128-1-rodrigo.vivi@intel.com>
On 2022-07-13 at 11:52:30 -0400, Rodrigo Vivi wrote:
> Mixing the names with the state names can cause confusion.
> Let's stick with the official names.
>
> Cc: Riana Tauro <riana.tauro@intel.com>
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> lib/igt_aux.c | 8 ++++----
> lib/igt_aux.h | 6 +++---
> tests/i915/i915_suspend.c | 2 +-
> 3 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/lib/igt_aux.c b/lib/igt_aux.c
> index 35c67f10..5129d9f0 100644
> --- a/lib/igt_aux.c
> +++ b/lib/igt_aux.c
> @@ -712,9 +712,9 @@ static const char *suspend_test_name[] = {
> };
>
> static const char *mem_sleep_name[] = {
> - [MEM_SLEEP_FREEZE] = "s2idle",
> - [MEM_SLEEP_STANDBY] = "shallow",
> - [MEM_SLEEP_MEM] = "deep"
> + [MEM_SLEEP_S2IDLE] = "s2idle",
> + [MEM_SLEEP_SHALLOW] = "shallow",
> + [MEM_SLEEP_DEEP] = "deep"
> };
>
> static enum igt_suspend_test get_suspend_test(int power_dir)
> @@ -993,7 +993,7 @@ int igt_get_memsleep_state(void)
> return MEM_SLEEP_NONE;
> }
>
> - for (mem_sleep = MEM_SLEEP_FREEZE; mem_sleep < MEM_SLEEP_NUM; mem_sleep++) {
> + for (mem_sleep = MEM_SLEEP_S2IDLE; mem_sleep < MEM_SLEEP_NUM; mem_sleep++) {
> if (strcmp(mem_sleep_name[mem_sleep], mem_sleep_state) == 0)
> break;
> }
> diff --git a/lib/igt_aux.h b/lib/igt_aux.h
> index af663d2c..9d5b7bd2 100644
> --- a/lib/igt_aux.h
> +++ b/lib/igt_aux.h
> @@ -196,9 +196,9 @@ enum igt_suspend_test {
> */
> enum igt_mem_sleep {
> MEM_SLEEP_NONE,
> - MEM_SLEEP_FREEZE,
> - MEM_SLEEP_STANDBY,
> - MEM_SLEEP_MEM,
> + MEM_SLEEP_S2IDLE,
> + MEM_SLEEP_SHALLOW,
> + MEM_SLEEP_DEEP,
>
> /*<private>*/
> MEM_SLEEP_NUM,
> diff --git a/tests/i915/i915_suspend.c b/tests/i915/i915_suspend.c
> index 23e451d3..f992d447 100644
> --- a/tests/i915/i915_suspend.c
> +++ b/tests/i915/i915_suspend.c
> @@ -209,7 +209,7 @@ test_suspend_without_i915(int state)
> igt_kmsg(KMSG_INFO "Unloading i915\n");
> igt_assert_eq(igt_i915_driver_unload(),0);
>
> - igt_skip_on_f(igt_get_memsleep_state() == MEM_SLEEP_FREEZE && state > SUSPEND_STATE_FREEZE,
> + igt_skip_on_f(igt_get_memsleep_state() == MEM_SLEEP_S2IDLE && state > SUSPEND_STATE_FREEZE,
> "Platform default mem_sleep state is s2idle\n");
> igt_system_suspend_autoresume(state, SUSPEND_TEST_NONE);
Looks good to me.
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
>
> --
> 2.35.3
>
next prev parent reply other threads:[~2022-07-18 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 15:52 [igt-dev] [PATCH i-g-t 1/4] lib/igt_aux: Let's use the official mem_sleep names Rodrigo Vivi
2022-07-13 15:52 ` [igt-dev] [PATCH i-g-t 2/4] tests/i915/i915_suspend: Be more specific on the S3 mem_sleep requirement Rodrigo Vivi
2022-07-18 6:24 ` Anshuman Gupta
2022-07-13 15:52 ` [igt-dev] [PATCH i-g-t 3/4] lib/igt_aux: Introduce the ability to force S3 suspend state Rodrigo Vivi
2022-07-18 6:47 ` Anshuman Gupta
2022-07-18 21:42 ` Rodrigo Vivi
2022-07-19 5:20 ` Gupta, Anshuman
2022-07-13 15:52 ` [igt-dev] [PATCH i-g-t 4/4] test/i915/i915_suspend: Use SUSPEND_STATE_S3 to enforce S3 Rodrigo Vivi
2022-07-18 7:09 ` Anshuman Gupta
2022-07-13 18:58 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/4] lib/igt_aux: Let's use the official mem_sleep names Patchwork
2022-07-18 5:54 ` Anshuman Gupta [this message]
2022-07-19 13:17 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/4] lib/igt_aux: Let's use the official mem_sleep names (rev2) Patchwork
2022-07-21 10:26 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/4] lib/igt_aux: Let's use the official mem_sleep names (rev3) 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=20220718055445.GA32110@intel.com \
--to=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@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