Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <ramanaidu.naladala@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/intel/kms_psr2_sf: Add eDP check for Early Transport
Date: Thu, 19 Sep 2024 23:05:31 +0530	[thread overview]
Message-ID: <c46d382b-094a-455d-b186-30d3e56b40ef@intel.com> (raw)
In-Reply-To: <20240919172425.1154937-1-jeevan.b@intel.com>

Hi Jeeavn,


On 9/19/2024 10:54 PM, Jeevan B wrote:
> On current platforms early transport is supported on eDP only
> so avoiding assert for other connector.
> 
> v2: Add checks to handle crashes and fix typo.
> 
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
>   tests/intel/kms_psr2_sf.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/intel/kms_psr2_sf.c b/tests/intel/kms_psr2_sf.c
> index a9be1a1ec..ca729d558 100644
> --- a/tests/intel/kms_psr2_sf.c
> +++ b/tests/intel/kms_psr2_sf.c
> @@ -935,7 +935,9 @@ static void run(data_t *data)
>   							  data->pipe),
>   							  "FBC still disabled\n");
>   
> -	if (data->et_flag)
> +	/* TODO: Enable this check if other connectors support Early Transport */
> +	if (data->et_flag && data->output != NULL &&
> +	    data->output->config.connector->connector_type == DRM_MODE_CONNECTOR_eDP)
>   		igt_assert_f(early_transport_check(data->debugfs_fd),
>   			     "Early Trasport Disbaled\n");
> 

LGTM,
Reviewed-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>



  reply	other threads:[~2024-09-19 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 17:24 [PATCH i-g-t] tests/intel/kms_psr2_sf: Add eDP check for Early Transport Jeevan B
2024-09-19 17:35 ` Naladala, Ramanaidu [this message]
2024-09-20  2:04 ` ✓ CI.xeBAT: success for " Patchwork
2024-09-20  2:11 ` ✓ Fi.CI.BAT: " Patchwork
2024-09-20  7:03 ` ✗ CI.xeFULL: failure " Patchwork
2024-09-20  8:32   ` B, Jeevan
2024-09-20 21: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=c46d382b-094a-455d-b186-30d3e56b40ef@intel.com \
    --to=ramanaidu.naladala@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