All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Petri Latvala <petri.latvala@intel.com>,
	Alex Hung <alex.hung@amd.com>,
	Swati Sharma <swati2.sharma@intel.com>
Cc: igt-dev@lists.freedesktop.org, markyacoub@google.com
Subject: Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Check DP connection only before tests
Date: Wed, 26 Oct 2022 16:44:06 +0530	[thread overview]
Message-ID: <79df58ca-1e4e-e86b-af75-799d7e81df73@intel.com> (raw)
In-Reply-To: <Y1jo6avSqRrAU7rY@platvala-desk.ger.corp.intel.com>

On Wed-26-10-2022 01:29 pm, Petri Latvala wrote:
> On Tue, Oct 25, 2022 at 08:16:15PM -0600, Alex Hung wrote:
>> Without DP port connected, kernel reports "Too many retries"
>> that indicates no sink to respond. This is the same across GPUs.
>>
>> amdgpu ... DM aux hw bus 2: Too many retries, giving up. First error: -5
>> i915 ... AUX C/DDI C/PHY C: Too many retries, giving up. First error: -110
>>
>> In addition, the test can result time out such as below:
>>
>> /dev/drm_dp_aux0: Connection timed out
>> /dev/drm_dp_aux1: Connection timed out

These timeouts are already handled in this test: 
https://cgit.freedesktop.org/drm/igt-gpu-tools/tree/tests/kms_dp_aux_dev.c#n88

IMO, It could be fine with existing test, since it'll work as a kind of 
negative scenario.

- Bhanu

>>
>> As a result, checking DP connection alone should be sufficient.
>>
>> Signed-off-by: Alex Hung <alex.hung@amd.com>
>> ---
>>   tests/kms_dp_aux_dev.c | 3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
>> index ed9dd510..7fce74a4 100644
>> --- a/tests/kms_dp_aux_dev.c
>> +++ b/tests/kms_dp_aux_dev.c
>> @@ -53,8 +53,7 @@ static bool test(int drm_fd, uint32_t connector_id)
>>   	drmModeFreeConnector(connector);
>>   	igt_assert(dir_fd >= 0);
>>   
>> -	if (connector->connection != DRM_MODE_CONNECTED &&
>> -	    is_mst_connector(drm_fd, connector_id)) {
>> +	if (connector->connection != DRM_MODE_CONNECTED) {
>>   		close(dir_fd);
>>   		return false;
>>   	}
> 
> 
> Bhanuprakash, Swati, you wrote/reviewed this piece of code, please review
> this patch.
> 
> 

  reply	other threads:[~2022-10-26 11:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  2:16 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Check DP connection only before tests Alex Hung
2022-10-26  3:16 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-10-26  7:59 ` [igt-dev] [PATCH] " Petri Latvala
2022-10-26 11:14   ` Modem, Bhanuprakash [this message]
2022-10-26 15:07     ` Alex Hung
2022-10-27  1:12       ` Modem, Bhanuprakash
2022-10-26 18:14 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=79df58ca-1e4e-e86b-af75-799d7e81df73@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=alex.hung@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=markyacoub@google.com \
    --cc=petri.latvala@intel.com \
    --cc=swati2.sharma@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.