From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Sean Paul <seanpaul@chromium.org>,
Anshuman Gupta <anshuman.gupta@intel.com>,
Ramalingam C <ramalingam.c@intel.com>,
Karthik B S <karthik.b.s@intel.com>
Subject: [Intel-gfx] i915 MST HDCP code looks broken
Date: Mon, 4 Oct 2021 13:51:34 +0300 [thread overview]
Message-ID: <YVrctgdJ8EYdW9i0@intel.com> (raw)
Hi,
I took a quick peek at intel_dp_add_mst_connector() the other day and
noticed that it calls intel_dp_hdcp_init() and passes in the SST
dig_port. And digging in a bit further that seems to clobber all
kinds of things in dig_port->hdcp_port_data. This looks rather
broken to me.
So has anyone actually thought what happens if you first use
MST on the port, and then later switch to SST on the same port?
--
Ville Syrjälä
Intel
next reply other threads:[~2021-10-04 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:51 Ville Syrjälä [this message]
2021-10-04 15:04 ` [Intel-gfx] i915 MST HDCP code looks broken Gupta, Anshuman
2021-10-04 18:38 ` Ville Syrjälä
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=YVrctgdJ8EYdW9i0@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=ramalingam.c@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 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.