From: Ramalingam C <ramalingam.c@intel.com>
To: Juston Li <juston.li@intel.com>
Cc: intel-gfx@lists.freedesktop.org, seanpaul@chromium.org,
nathan.d.ciobanu@intel.com
Subject: Re: [intel-gfx] [PATCH] drm/i915: coffeelake supports hdcp2.2
Date: Mon, 14 Oct 2019 11:34:54 +0530 [thread overview]
Message-ID: <20191014060453.GA25849@intel.com> (raw)
In-Reply-To: <20191011181918.29618-1-juston.li@intel.com>
On 2019-10-11 at 11:19:18 -0700, Juston Li wrote:
> This includes other platforms that utilize the same gen graphics as
> CFL: AML, WHL and CML.
>
> Signed-off-by: Juston Li <juston.li@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index e69fa34528df..f7db61eaeb7f 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -1887,7 +1887,7 @@ static bool is_hdcp2_supported(struct drm_i915_private *dev_priv)
> return false;
>
> return (INTEL_GEN(dev_priv) >= 10 || IS_GEMINILAKE(dev_priv) ||
> - IS_KABYLAKE(dev_priv));
> + IS_KABYLAKE(dev_priv) || IS_COFFEELAKE(dev_priv));
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> }
>
> void intel_hdcp_component_init(struct drm_i915_private *dev_priv)
> --
> 2.21.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-10-14 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 18:19 [intel-gfx] [PATCH] drm/i915: coffeelake supports hdcp2.2 Juston Li
2019-10-11 20:04 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-12 4:56 ` ✓ Fi.CI.IGT: " Patchwork
2019-10-14 6:04 ` Ramalingam C [this message]
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=20191014060453.GA25849@intel.com \
--to=ramalingam.c@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=juston.li@intel.com \
--cc=nathan.d.ciobanu@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