From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41F65C433F5 for ; Mon, 30 May 2022 09:54:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234964AbiE3JyZ (ORCPT ); Mon, 30 May 2022 05:54:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43494 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234966AbiE3JyY (ORCPT ); Mon, 30 May 2022 05:54:24 -0400 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0B4D7090E for ; Mon, 30 May 2022 02:54:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1653904464; x=1685440464; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=mjQI1ILLkD9O9INRQaMPN3XvJLDS56jiGLSE3WFK+y4=; b=I0b/0RYngvHPK39AMCCsY0iIRespWmKuf7vTwQZscvmP75thnToG8uCc QWr+WkcAhhXW3oQM5VFvUeE012WiueU0Y/RzhXPrsrP2a1Z07Nlx1q8Zn j1Zcnryu6DmRfg+F+YEDcX3CXWHCDbsDXZ8PXIZYcS/3/bJRczh9UjwFL 1cpQ1ms2oyeHTsoaSgTqQ6ZGsmN1I9yf/iyAswwuVXm5P7/7Bo23Ij3CE p3a7HJZUZ06SW3zj+PFgdbavJKRZrdkr0Ns6tT5QHqxPEwY1W4PuputiH S4sNueKIdMLjLOURERLT1+n957cke7ORWjJQthbqWOP/qMnuj+fGVCNkt w==; X-IronPort-AV: E=McAfee;i="6400,9594,10362"; a="274957423" X-IronPort-AV: E=Sophos;i="5.91,262,1647327600"; d="scan'208";a="274957423" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 May 2022 02:54:23 -0700 X-IronPort-AV: E=Sophos;i="5.91,262,1647327600"; d="scan'208";a="666451853" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.162]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 May 2022 02:54:21 -0700 Received: by lahna (sSMTP sendmail emulation); Mon, 30 May 2022 12:54:18 +0300 Date: Mon, 30 May 2022 12:54:18 +0300 From: Mika Westerberg To: Tomasz =?utf-8?Q?Mo=C5=84?= Cc: Stefan Hoffmeister , Heikki Krogerus , linux-usb@vger.kernel.org Subject: Re: Thunderbolt: One missing DisplayPort? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Mon, May 30, 2022 at 10:33:06AM +0200, Tomasz Moń wrote: > On Sun, 2022-05-29 at 21:51 +0200, Stefan Hoffmeister wrote: > > I have managed to wedge the system into a state where it does not > > know about Thunderbolt, and now, on what I presume to be USB-C only > > ("usb_typec_revision" == 1.2? Seems ... low?), both DisplayPort > > outputs on the docking station are now active, and I do get > > meaningful entries from the DRM subsystem (and hence X). I am half- > > way happy: I want exactly that over Thunderbolt for the bandwidth ;) > > Could you please tell how did you wedge the system into a state where > it does not know about Thunderbolt? > > > Now, when I unwedge the system to enable Thunderbolt again > > I am curious about the wedge/unwedge procedure. Probably just connecting the dock using non-Thunderbolt Type-C cable. That will enter USB (+DP altmode) or so instead of Thunderbolt altmode. @Stefan, Can you paste contents of /sys/kernel/debug/thunderbolt/0-0/port5/regs and port6/regs here? Once you have conneted the dock with Thunderbolt cable. That should show if the both DP IN adapters are connected and hence if both DP tunnels are up. I'm guessing they are but better to check.