From: Ramalingam C <ramalingam.c@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] HDCP1.4 fixes
Date: Tue, 27 Feb 2018 16:41:54 +0530 [thread overview]
Message-ID: <a5135a36-2a6e-1ef0-658d-f67e009c8378@intel.com> (raw)
In-Reply-To: <20180226232416.GE2294@intel.com>
On Tuesday 27 February 2018 04:54 AM, Rodrigo Vivi wrote:
> On Mon, Feb 26, 2018 at 10:42:34PM +0530, Ramalingam C wrote:
>> This series addresses the requriement of below HDCP compliance tests
>> DP: 1A-06 and 1B-05
>> HDMI: 1A-04 and 1A-07a
>>
>> One of the patch uses the I915 power infra-structure for checking
>> the power state of PW#1. Which enables the init path for all legacy
>> platforms.
>>
>> And encoder specific msg availability detection is moved into hdcp_shim.
>> This will help to sync with DP hdcp data availability in the best
>> possible way by fielding the CP_IRQ.
> Do we want any of these on 4.16 or backported?
Rodrigo,
The changes are for addressing the compliance gaps.
So IMHO at present there is no need for back porting them.
> Please consider the use of "Fixes:" on whatever makes sense.
Sure thanks.
--Ram.
>
> Thanks,
> Rodrigo.
>
>>
>> Ramalingam C (5):
>> 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: Poll hdcp register on sudden NACK
>> drm/i915: Move hdcp msg detection into shim
>>
>> drivers/gpu/drm/i915/intel_dp.c | 70 ++++++++++++++--
>> drivers/gpu/drm/i915/intel_drv.h | 6 +-
>> drivers/gpu/drm/i915/intel_hdcp.c | 166 +++++++++++++++++++++++++++-----------
>> drivers/gpu/drm/i915/intel_hdmi.c | 28 ++++++-
>> 4 files changed, 214 insertions(+), 56 deletions(-)
>>
>> --
>> 2.7.4
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-27 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 17:12 [PATCH 0/5] HDCP1.4 fixes Ramalingam C
2018-02-26 17:12 ` [PATCH 1/5] drm/i915: Read HDCP R0 thrice in case of mismatch Ramalingam C
2018-02-26 17:37 ` Sean Paul
2018-02-27 11:38 ` Ramalingam C
2018-02-26 17:12 ` [PATCH 2/5] drm/i915: read Vprime thrice incase " Ramalingam C
2018-02-26 17:40 ` Sean Paul
2018-02-27 12:32 ` [PATCH v2] " Ramalingam C
2018-02-26 17:12 ` [PATCH 3/5] drm/i915: Check hdcp key loadability Ramalingam C
2018-02-26 17:45 ` Sean Paul
2018-02-26 17:12 ` [PATCH 4/5] drm/i915: Poll hdcp register on sudden NACK Ramalingam C
2018-02-26 17:52 ` Sean Paul
2018-02-27 14:36 ` Ramalingam C
2018-02-26 17:12 ` [PATCH 5/5] drm/i915: Move hdcp msg detection into shim Ramalingam C
2018-02-26 18:01 ` Sean Paul
2018-02-27 11:20 ` Ramalingam C
2018-02-26 22:50 ` [Intel-gfx] " Chris Wilson
2018-03-08 6:29 ` Ramalingam C
2018-02-26 17:44 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes Patchwork
2018-02-26 22:21 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-26 23:24 ` [PATCH 0/5] " Rodrigo Vivi
2018-02-27 11:11 ` Ramalingam C [this message]
2018-02-27 13:28 ` ✗ Fi.CI.BAT: failure for HDCP1.4 fixes (rev2) 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=a5135a36-2a6e-1ef0-658d-f67e009c8378@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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