On 6 August 2014 09:59, Dave Airlie wrote:
> On 6 August 2014 08:07, Daniel Vetter wrote:
>> On Tue, Aug 5, 2014 at 2:40 AM, Dave Airlie wrote:
>>> @@ -3502,10 +3505,13 @@ go_again:
>>> void
>>> intel_dp_check_link_status(struct intel_dp *intel_dp)
>>> {
>>> + struct drm_device *dev = i
On 6 August 2014 08:07, Daniel Vetter wrote:
> On Tue, Aug 5, 2014 at 2:40 AM, Dave Airlie wrote:
>> @@ -3502,10 +3505,13 @@ go_again:
>> void
>> intel_dp_check_link_status(struct intel_dp *intel_dp)
>> {
>> + struct drm_device *dev = intel_dp_to_dev(intel_dp);
>> struct intel_en
On Tue, Aug 5, 2014 at 2:40 AM, Dave Airlie wrote:
> @@ -3502,10 +3505,13 @@ go_again:
> void
> intel_dp_check_link_status(struct intel_dp *intel_dp)
> {
> + struct drm_device *dev = intel_dp_to_dev(intel_dp);
> struct intel_encoder *intel_encoder = &dp_to_dig_port(intel_dp)->base
From: Dave Airlie
We need to take the connection mutex around the link status
check for non-MST case, but also around the MST link training
on short HPDs.
I suspect we actually should have a dpcd lock in the future as
well, that just lock the local copies of dpcd and flags stored
from that.
Sig
