From: "Reddy Guddati, Santhosh" <santhosh.reddy.guddati@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "B S, Karthik" <karthik.b.s@intel.com>,
"Thasleem, Mohammed" <mohammed.thasleem@intel.com>,
"S, Sowmiya" <sowmiya.s@intel.com>
Subject: Re: [PATCH i-g-t v5 2/2] tests/kms_content_protection: Handle EDID lookup failures
Date: Mon, 23 Mar 2026 08:27:57 +0530 [thread overview]
Message-ID: <61f8c098-ebe6-4c3f-a1d3-e2f2389c1415@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8DAC222A0188D2D82DE353E34FA@DM3PPF208195D8D.namprd11.prod.outlook.com>
Hi Suraj,
On 19-03-2026 16:20, Kandpal, Suraj wrote:
>> Subject: [PATCH i-g-t v5 2/2] tests/kms_content_protection: Handle EDID
>> lookup failures
>>
>> During output selection, connectors may disconnect or AUX reads may
>> timeout. In that cases, EDID blob read fails instead of assert log the failure so
>> test dont asserts.
>
> Does not make sense to have sudden connectors disconnection when you are just reading EDID.
> The only time this happens is you are trying to ready when Connector does not have a CRTC.
> Needs to be investigated more.
> I suggest you do not add this to the current patch otherwise this will hold up the previous patch
>
Thanks for the feedback. Agreed, I will drop this from the current patch
and will create a new patch for the EDID lookup failures upon
disconnection with example scenarios after investigation.
Regards,
Santhosh
> Regards,
> Suraj Kandpal
>>
>> Signed-off-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
>> ---
>> tests/kms_content_protection.c | 24 +++++++++++++++++-------
>> 1 file changed, 17 insertions(+), 7 deletions(-)
>>
>> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
>> index caf3d7a56..006aeb510 100644
>> --- a/tests/kms_content_protection.c
>> +++ b/tests/kms_content_protection.c
>> @@ -683,13 +683,24 @@ static bool
>> is_output_hdcp_test_exempt(igt_output_t *output)
>> const struct edid *edid;
>> char edid_vendor[4];
>> char sink_name[20];
>> + bool ok;
>> +
>> + ok = kmstest_get_property(data.drm_fd,
>> + output->config.connector->connector_id,
>> + DRM_MODE_OBJECT_CONNECTOR, "EDID",
>> NULL,
>> + &edid_blob_id, NULL);
>> + if (!ok || !edid_blob_id) {
>> + igt_debug("Unable to get EDID blob id for %s\n",
>> + output->name);
>> + return false;
>> + }
>>
>> - igt_assert(kmstest_get_property(data.drm_fd,
>> - output->config.connector-
>>> connector_id,
>> - DRM_MODE_OBJECT_CONNECTOR,
>> "EDID", NULL,
>> - &edid_blob_id, NULL));
>> -
>> - igt_assert(edid_blob = drmModeGetPropertyBlob(data.drm_fd,
>> edid_blob_id));
>> + edid_blob = drmModeGetPropertyBlob(data.drm_fd, edid_blob_id);
>> + if (!edid_blob) {
>> + igt_debug("Unable to fetch EDID blob for %s (blob id=%"
>> PRIu64 ")\n",
>> + output->name, edid_blob_id);
>> + return false;
>> + }
>>
>> edid = (const struct edid *)edid_blob->data;
>> edid_get_mfg(edid, edid_vendor);
>> @@ -724,7 +735,6 @@ static int get_hdcp_outputs(igt_display_t *display, int
>> content_type,
>> continue;
>> }
>>
>> -
>> if (count < MAX_HDCP_OUTPUTS)
>> hdcp_outputs[count++] = output;
>> }
>> --
>> 2.34.1
>
next prev parent reply other threads:[~2026-03-23 2:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:47 [PATCH i-g-t v1] tests/kms_content_protection: check sink capability after modeset Santhosh Reddy Guddati
2026-02-27 0:23 ` ✓ i915.CI.BAT: success for " Patchwork
2026-02-27 1:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-27 7:39 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-02 2:54 ` [PATCH i-g-t v1] " Kandpal, Suraj
2026-03-09 6:07 ` Reddy Guddati, Santhosh
2026-03-16 4:04 ` [PATCH i-g-t v2] tests/kms_content_protection: Get hdcp capable outputs before modeset Santhosh Reddy Guddati
2026-03-16 4:26 ` Kandpal, Suraj
2026-03-16 5:13 ` [PATCH i-g-t v3] tests/kms_content_protection: Get HDCP " Santhosh Reddy Guddati
2026-03-16 14:24 ` S, Sowmiya
2026-03-16 5:43 ` ✓ Xe.CI.BAT: success for tests/kms_content_protection: check sink capability after modeset (rev2) Patchwork
2026-03-16 5:56 ` ✓ i915.CI.BAT: " Patchwork
2026-03-16 6:42 ` ✓ Xe.CI.BAT: success for tests/kms_content_protection: check sink capability after modeset (rev3) Patchwork
2026-03-16 6:45 ` ✓ i915.CI.BAT: " Patchwork
2026-03-16 8:59 ` ✗ Xe.CI.FULL: failure for tests/kms_content_protection: check sink capability after modeset (rev2) Patchwork
2026-03-16 12:31 ` ✗ i915.CI.Full: " Patchwork
2026-03-17 3:42 ` [PATCH i-g-t v4] tests/kms_content_protection: Get HDCP capable outputs before modeset Santhosh Reddy Guddati
2026-03-17 3:54 ` S, Sowmiya
2026-03-17 13:53 ` ✓ Xe.CI.BAT: success for tests/kms_content_protection: check sink capability after modeset (rev4) Patchwork
2026-03-17 15:05 ` ✓ i915.CI.BAT: " Patchwork
2026-03-18 16:56 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-18 22:13 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-19 6:41 ` [PATCH i-g-t v5 0/2] Get HDCP capable outputs before modeset Santhosh Reddy Guddati
2026-03-19 6:41 ` [PATCH i-g-t v5 1/2] tests/kms_content_protection: " Santhosh Reddy Guddati
2026-03-19 6:41 ` [PATCH i-g-t v5 2/2] tests/kms_content_protection: Handle EDID lookup failures Santhosh Reddy Guddati
2026-03-19 10:50 ` Kandpal, Suraj
2026-03-23 2:57 ` Reddy Guddati, Santhosh [this message]
2026-03-19 8:55 ` ✓ Xe.CI.BAT: success for tests/kms_content_protection: check sink capability after modeset (rev5) Patchwork
2026-03-19 9:13 ` ✓ i915.CI.BAT: " Patchwork
2026-03-20 2:01 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-20 10:01 ` ✗ Xe.CI.FULL: " 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=61f8c098-ebe6-4c3f-a1d3-e2f2389c1415@intel.com \
--to=santhosh.reddy.guddati@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=mohammed.thasleem@intel.com \
--cc=sowmiya.s@intel.com \
--cc=suraj.kandpal@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