Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 12 Aug 2022 12:35:55 +0300
From:   Mika Westerberg <mika.westerberg@linux.intel.com>
To:     Brad Campbell <lists2009@fnarfbargle.com>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: Apple Thunderbolt Display chaining
Message-ID: <YvYe+5AyI3aD6Q5V@black.fi.intel.com>
References: <YvI1lQh+C0SJiG73@lahna>
 <bcebdeb9-4f6a-e931-46f5-b9be899db9a4@fnarfbargle.com>
 <YvI9Cbin4OKQwZ05@lahna>
 <86bec398-7a5b-6d4e-bc02-5941fe6c2e73@fnarfbargle.com>
 <YvJyZ51H+YkceKJP@lahna>
 <39268cc6-4e05-b83c-ff73-3056925eeb76@fnarfbargle.com>
 <YvKCRPtoN6m2rMr2@lahna>
 <2c4420ac-d988-9dd8-c223-4243b9a6881e@fnarfbargle.com>
 <YvTQ0N2Py4rc4k3Z@lahna>
 <baf0f38a-27ac-ec2c-129d-c9430fc40dd0@fnarfbargle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <baf0f38a-27ac-ec2c-129d-c9430fc40dd0@fnarfbargle.com>
Precedence: bulk

Hi Brad,

On Thu, Aug 11, 2022 at 10:17:02PM +0800, Brad Campbell wrote:
> G'day Mika,
> > Okay, do you see in the dmesg whether the DP tunnels are actually
> > created when you see the issue?
> > 
> 
> Yes, the DP tunnels appear to be created. Xorg sees them and believes they are there :
> 
> brad@bkd:~$ grep -A1 EDID  /var/log/Xorg.0.log.old 
> [    29.377] (II) AMDGPU(0): EDID for output HDMI-A-0
> [    29.377] (II) AMDGPU(0): Manufacturer: DEL  Model: a19d  Serial#: 810240841
> --
> [    29.377] (II) AMDGPU(0): EDID Version: 1.3
> [    29.377] (II) AMDGPU(0): Digital Display Input
> --
> [    29.377] (II) AMDGPU(0): Number of EDID sections to follow: 1
> [    29.377] (II) AMDGPU(0): EDID (in hex):
> [    29.377] (II) AMDGPU(0): 	00ffffffffffff0010ac9da1494b4b30
> --
> [    29.377] (II) AMDGPU(0): EDID for output DisplayPort-0
> [    29.377] (II) AMDGPU(0): Manufacturer: APP  Model: 9227  Serial#: 354616281
> --
> [    29.377] (II) AMDGPU(0): EDID Version: 1.4
> [    29.377] (II) AMDGPU(0): Digital Display Input
> --
> [    29.378] (II) AMDGPU(0): Number of EDID sections to follow: 1
> [    29.378] (II) AMDGPU(0): EDID (in hex):
> [    29.378] (II) AMDGPU(0): 	00ffffffffffff0006102792d9032315
> --
> [    29.378] (II) AMDGPU(0): EDID for output DisplayPort-1
> [    29.378] (II) AMDGPU(0): Manufacturer: APP  Model: 9227  Serial#: 437126968
> --
> [    29.378] (II) AMDGPU(0): EDID Version: 1.4
> [    29.378] (II) AMDGPU(0): Digital Display Input
> --
> [    29.378] (II) AMDGPU(0): Number of EDID sections to follow: 1
> [    29.378] (II) AMDGPU(0): EDID (in hex):
> [    29.378] (II) AMDGPU(0): 	00ffffffffffff000610279238070e1a
> 
> This test was done with thunderbolt compiled in just to demonstrate,
> but any load sequence or combination
> winds up with the same issue.

I went through your log but could not find anything out of ordinary from
TBT perspective. The tunnels get cleaned up by the discovery code and
then re-created after the reset completes and they seem to be fine. You
may try to add some sort of delay like 100ms or so after the DPR reset
but I doubt it changes anything.