All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Joshi, Kunal1" <kunal1.joshi@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/igt_psr: added enum for PR mode
Date: Mon, 9 Oct 2023 09:32:15 +0000	[thread overview]
Message-ID: <6ff0734040b27b0e4df1a02ae443e46f66be9223.camel@intel.com> (raw)
In-Reply-To: <20231003051959.461527-2-kunal1.joshi@intel.com>

On Tue, 2023-10-03 at 10:49 +0530, Kunal Joshi wrote:
> Added enum PR_MODE_1 and PR_MODE_1_SEL_FETCH,
> PR_MODE_1 is expected to behave like PSR and 
> PR_MODE_1_SEL_FETCH like PSR2 with selective fetch
> 
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Cc: Animesh Manna <animesh.manna@intel.com>
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
>  lib/igt_psr.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/igt_psr.h b/lib/igt_psr.h
> index 12ffc9d6c..fff673f6b 100644
> --- a/lib/igt_psr.h
> +++ b/lib/igt_psr.h
> @@ -34,6 +34,8 @@ enum psr_mode {
>         PSR_MODE_1,
>         PSR_MODE_2,
>         PSR_MODE_2_SEL_FETCH,
> +       PR_MODE_1,
> +       PR_MODE_1_SEL_FETCH,

I think you can drop "1_".

>         PSR_DISABLED,
>  };
>  


  reply	other threads:[~2023-10-09  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03  5:19 [igt-dev] [PATCH i-g-t 0/2] PR related lib changes Kunal Joshi
2023-10-03  5:19 ` [igt-dev] [PATCH i-g-t 1/2] lib/igt_psr: added enum for PR mode Kunal Joshi
2023-10-09  9:32   ` Hogander, Jouni [this message]
2023-10-03  5:19 ` [igt-dev] [PATCH i-g-t 2/2] lib/igt_psr: updated functions to check PR support Kunal Joshi
2023-10-03  6:15 ` [igt-dev] ✓ Fi.CI.BAT: success for PR related lib changes Patchwork
2023-10-03  6:19 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-10-03  7:26 ` [igt-dev] ✗ 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=6ff0734040b27b0e4df1a02ae443e46f66be9223.camel@intel.com \
    --to=jouni.hogander@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.