From: "C, Ramalingam" <ramalingam.c@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
seanpaul@chromium.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915: Fix GEN9 HDCP1.4 key load process
Date: Tue, 27 Nov 2018 21:57:02 +0530 [thread overview]
Message-ID: <4b7fff81-7b55-34d4-e523-a4089e95b96b@intel.com> (raw)
In-Reply-To: <20181127151545.GZ9144@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2190 bytes --]
On 11/27/2018 8:45 PM, Ville Syrjälä wrote:
> On Tue, Nov 27, 2018 at 07:32:56PM +0530, Ramalingam C wrote:
>> HDCP1.4 key load process varies between Intel platform to platform.
>>
>> For Gen9 platforms except BXT and GLK, HDCP1.4 key is loaded using
>> the GT Driver Mailbox interface. Instead of listing all the platforms
>> for this method, adopted this method for all Gen9 platforms with
>> exceptions. In this way we need not extent check for new GEN9 platforms
>> like CFL.
>>
>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_hdcp.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_hdcp.c b/drivers/gpu/drm/i915/intel_hdcp.c
>> index 1bf487f94254..beacfbb6e5e1 100644
>> --- a/drivers/gpu/drm/i915/intel_hdcp.c
>> +++ b/drivers/gpu/drm/i915/intel_hdcp.c
>> @@ -157,10 +157,12 @@ static int intel_hdcp_load_keys(struct drm_i915_private *dev_priv)
>> /*
>> * Initiate loading the HDCP key from fuses.
>> *
>> - * BXT+ platforms, HDCP key needs to be loaded by SW. Only SKL and KBL
>> - * differ in the key load trigger process from other platforms.
>> + * BXT+ platforms, HDCP key needs to be loaded by SW. Only Gen 9
>> + * platforms except BXT and GLK, differ in the key load trigger process
>> + * from other platforms.
>> */
>> - if (IS_SKYLAKE(dev_priv) || IS_KABYLAKE(dev_priv)) {
>> + if (IS_GEN9(dev_priv) &&
>> + (!IS_BROXTON(dev_priv) && !IS_GEMINILAKE(dev_priv))) {
> IS_GEN9_BC()
Bspec doesn't state anything about BC/LP. They have mentioned GEN9+ with BXT, CNL, ICL excluded.
So I am inferring that this method is only for Gen9 excluding BXT and GLK (verified).
Remaining platforms are SKL, KBL, and CFL.
IS_GEN9_BC() will filter them easily. unless we find otherwise, we can use this. Thanks Ville.
--Ram
>
>> mutex_lock(&dev_priv->pcu_lock);
>> ret = sandybridge_pcode_write(dev_priv,
>> SKL_PCODE_LOAD_HDCP_KEYS, 1);
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[-- Attachment #1.2: Type: text/html, Size: 3172 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-27 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:02 [PATCH 0/4] HDCP1.4 fixes Ramalingam C
2018-11-27 14:02 ` [PATCH 1/4] drm/i915: Fix GEN9 HDCP1.4 key load process Ramalingam C
2018-11-27 15:15 ` Ville Syrjälä
2018-11-27 16:27 ` C, Ramalingam [this message]
2018-11-28 14:00 ` [PATCH v2 " Ramalingam C
2018-12-03 14:23 ` [PATCH " Sean Paul
2018-11-27 14:02 ` [PATCH 2/4] drm/i915: Fix platform coverage for HDCP1.4 Ramalingam C
2018-12-03 14:23 ` Sean Paul
2018-11-27 14:02 ` [PATCH 3/4] drm/i915: debug log for REPLY_ACK missing Ramalingam C
2018-12-03 14:26 ` Sean Paul
2018-11-27 14:02 ` [PATCH 4/4] drm/i915: Increase timeout for Encrypt status change Ramalingam C
2018-12-03 14:27 ` Sean Paul
2018-11-27 14:36 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes (rev8) Patchwork
2018-11-27 17:52 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-28 16:10 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes (rev9) Patchwork
2018-11-29 0:10 ` ✓ Fi.CI.IGT: " Patchwork
2018-12-03 10:08 ` [PATCH 0/4] HDCP1.4 fixes C, Ramalingam
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=4b7fff81-7b55-34d4-e523-a4089e95b96b@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
--cc=ville.syrjala@linux.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