From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Lakha, Bhawanpreet" <Bhawanpreet.Lakha@amd.com>,
Ramalingam C <ramalingam.c@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Subject: Re: HDCP Content Type Interface
Date: Tue, 10 Sep 2019 10:45:49 +0300 [thread overview]
Message-ID: <8736h4387m.fsf@intel.com> (raw)
In-Reply-To: <10cb9f86-9d46-6654-ad9d-dcb77d6ef624@amd.com>
On Mon, 09 Sep 2019, "Lakha, Bhawanpreet" <Bhawanpreet.Lakha@amd.com> wrote:
> Hi all,
>
> This is regarding the recent hdcp content type patch that was merged
> into
> drm-misc. (https://patchwork.freedesktop.org/patch/320958/?series=57233&rev=11)
>
> There are displays on the market that advertise HDCP 2.2 support and
> will pass authentication and encryption but will then show a
> corrupted/blue/black screen (the driver cannot detect this). These
> displays work with HDCP 1.4 without any issues. Due to the large
> number of HDCP-supporting devices on the market we might not be able
> to catch them with a blacklist.
Has this been confirmed with some other HDCP source than the recently
merged HDCP 2.2 support? I.e. has it been confirmed the issue is really
in the sinks rather than in the source support?
BR,
Jani.
>
> From the user modes perspective, HDCP1.4 and HDCP2.2 Type0 are the
> same thing. Meaning that this interface doesn't allow us to force the
> hdcp version. Due to the problems mentioned above we might want to
> expose the ability for a user to force an HDCP downgrade to a certain
> level (e.g. 1.4) in case they experience problems.
>
> What are your thoughts? and what would be a good way to deal with it?
>
>
> Thanks,
>
> Bhawan
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-10 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 15:54 HDCP Content Type Interface Lakha, Bhawanpreet
2019-09-10 7:45 ` Jani Nikula [this message]
2019-09-12 7:47 ` Ramalingam C
2019-09-12 14:23 ` Harry Wentland
2019-09-12 14:49 ` Ramalingam C
2019-09-12 19:19 ` Harry Wentland
2019-09-12 14:57 ` Jani Nikula
2019-09-12 19:21 ` Harry Wentland
2019-09-13 8:14 ` Daniel Vetter
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=8736h4387m.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ramalingam.c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.