From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
seanpaul@chromium.org
Cc: rodrigo.vivi@intel.com
Subject: Re: [PATCH v2 0/4] HDCP1.4 fixes
Date: Thu, 29 Mar 2018 19:42:28 +0530 [thread overview]
Message-ID: <0f869ba3-8fbd-5389-9491-dc616dcc8595@intel.com> (raw)
In-Reply-To: <1522332548-15370-1-git-send-email-ramalingam.c@intel.com>
On Thursday 29 March 2018 07:39 PM, Ramalingam C wrote:
> First two patches needed for below DP HDCP compliance tests
> 1A-06 and 1B-05
>
> Third patch fixes the HDCP1.4 Key loadability check. where as fourth
> one fixes the downstream device count read.
>
> Fix for HDMI HDCP1.4 CTS tests: 1A-04 and 1A-07a are functional.
> But the change from v2, as thinking to put through more regressive
The change is removed from v2*
All other changes are well tested on KBL.
--Ram
> testing before upstreaming.
>
> Ramalingam C (4):
> drm/i915: Read HDCP R0 thrice in case of mismatch
> drm/i915: Read Vprime thrice incase of mismatch
> drm/i915: Check hdcp key loadability
> drm/i915: Fix downstream dev count read
>
> drivers/gpu/drm/i915/intel_hdcp.c | 184 ++++++++++++++++++++++++++------------
> include/drm/drm_hdcp.h | 2 +-
> 2 files changed, 129 insertions(+), 57 deletions(-)
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-29 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 14:09 [PATCH v2 0/4] HDCP1.4 fixes Ramalingam C
2018-03-29 14:09 ` [PATCH v2 1/4] drm/i915: Read HDCP R0 thrice in case of mismatch Ramalingam C
2018-03-29 14:35 ` Sean Paul
2018-04-02 9:08 ` Ramalingam C
2018-03-29 14:09 ` [PATCH v2 2/4] drm/i915: Read Vprime thrice incase " Ramalingam C
2018-03-29 14:38 ` Sean Paul
2018-04-02 9:16 ` Ramalingam C
2018-03-29 14:09 ` [PATCH v2 3/4] drm/i915: Check hdcp key loadability Ramalingam C
2018-03-29 14:24 ` Ville Syrjälä
2018-04-02 9:05 ` Ramalingam C
2018-04-06 16:02 ` Ville Syrjälä
2018-04-09 8:28 ` Daniel Vetter
2018-04-11 8:27 ` Ramalingam C
2018-04-13 15:49 ` Daniel Vetter
2018-03-29 14:09 ` [PATCH v2 4/4] drm/i915: Fix downstream dev count read Ramalingam C
2018-03-29 14:39 ` Sean Paul
2018-03-29 14:12 ` Ramalingam C [this message]
2018-03-29 14:45 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes (rev3) Patchwork
2018-03-29 17:53 ` ✗ Fi.CI.IGT: failure " 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=0f869ba3-8fbd-5389-9491-dc616dcc8595@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=seanpaul@chromium.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