<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - HDCP compliance sub test cases failure due to hpd timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109671#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - HDCP compliance sub test cases failure due to hpd timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109671">bug 109671</a>
from <span class="vcard"><a class="email" href="mailto:ramalingam.c@intel.com" title="Ramalingam C <ramalingam.c@intel.com>"> <span class="fn">Ramalingam C</span></a>
</span></b>
<pre>From the discussion with compliance execution team here, HPD_Timer is the delay
allowed by the analyzer, to start the HDCP authentication after an HPD
detection. So we need to check the turnaround time in our whole stack KMD &
UMD.
So Khairul and Shiqiang, Could you please measure the time required for below
activities on compliance setup.
1. Time taken to broadcast the hotplug uevent from kernel after the HPD
detection.
2. Time taken to receive the HDCP request from userspace after the hotplug
uevent broadcast from the kernel.
3. Time taken to start the HDCP auth after atomic request.
Basically, at the kernel, capture the time of
1. hpd detection
2. hotplug uevent broadcast
3. atomic request arrival at kernel for HDCP
4. HDCP authentication start at intel_hdcp.c</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>