It requires to check streams type1 capability in mst topology
by checking Rxinfo instead connector HDCP2.x capability in
order to enforce type0 stream encryption in a mix of
HDCP {1.x,2.x} mst topology.
Rxcaps always shows HDCP 2.x capability of immediate downstream
connector. Let's use Rxinfo
Sorry my mistake, I did not take into account the endianness.
Patch looks good to me.
Reviewed-by: Ankit Nautiyal
On 3/16/2021 6:20 PM, Nautiyal, Ankit K wrote:
Hi Anshuman,
I agree with the patch. Overall looks good.
There is a correction suggested below:
On 1/27/2021 3:30 PM, Anshuman
Hi Anshuman,
I agree with the patch. Overall looks good.
There is a correction suggested below:
On 1/27/2021 3:30 PM, Anshuman Gupta wrote:
It requires to check streams type1 capability in mst topology
by checking Rxinfo instead connector HDCP2.x capability in
order to enforce type0 stream
It requires to check streams type1 capability in mst topology
by checking Rxinfo instead connector HDCP2.x capability in
order to enforce type0 stream encryption in a mix of
HDCP {1.x,2.x} mst topology.
Rxcaps always shows HDCP 2.x capability of immediate downstream
connector. Let's use Rxinfo
