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:   Tue, 9 Aug 2022 13:23:17 +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: <YvI1lQh+C0SJiG73@lahna>
References: <d484d7e5-f1aa-1096-e6fb-bbf16ce28699@fnarfbargle.com>
 <Yu0nWro4xXURbSX6@lahna>
 <87c1a001-ef79-6390-dfe2-06d2850f6e84@fnarfbargle.com>
 <Yu4Gmkous7asng6h@lahna>
 <42e81a8e-e393-7a69-7339-a020ebb57935@fnarfbargle.com>
 <YvDcudE5BRtZAtfM@lahna>
 <a1db1454-63b6-7c39-bbf6-53e53bbd36e6@fnarfbargle.com>
 <5474e599-057a-ec0f-b469-560644155907@fnarfbargle.com>
 <YvEFtPF7SBIwNG/o@lahna>
 <d234ea9b-9303-6088-0a9b-4de887a77bf4@fnarfbargle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d234ea9b-9303-6088-0a9b-4de887a77bf4@fnarfbargle.com>
Precedence: bulk

Hi,

On Mon, Aug 08, 2022 at 09:27:24PM +0800, Brad Campbell wrote:
> If I don't authorize the PCIe tunnels and just leave the DP enabled it
> works fine also.

But you say that it fails on boot when the driver discovers the tunnels,
right? So there is really nothing to authorize (they should be already
"authorized" by the boot firmware).

If I understand correctly this is how it reproduces (the simplest):

  1. Connect a single Apple TB1 display to the system
  2. Boot it up
  3. Wait a while and it hangs

If this is the case, then the driver certainly is not creating any
PCIe tunnels itself unless there is a bug somewhere.

An additional question, does it reproduce with either TB1 display
connected or just with specific TB1 display?