From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 41EB23D091B for ; Wed, 20 May 2026 09:56:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.21 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779270965; cv=none; b=atDwO6qU+LVmL3B4k9ZdBOYtHudakXhg+A4uJZD0whzgomRgbR14x5rh2pqdeAXicmlWbhSw2z3TZBDVEtExgbrNvFZwqhwuNabtcXqbxAVwzpQ2AnmUZ6/mzVlrQYb30XxMMhuoFAcA2sXb4XDX6t+wNChRXwtq1ccg3t2ywog= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779270965; c=relaxed/simple; bh=L+UFOsAszlV+duz1urRSW6QFal0eGvHWNO6OglS4mU0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=fQR39fHXZDZ/L9oYcC79YP9PyB3DPOZ+i+x6JaO6xJB/x3Yh91P04uBaWLlNmYpeu2JR+ugz38vUi1C2zPpt3piePOWZO3YmB0B9h1n0EJjQMTXn9dPpF3aHEoGX9kbkSOIHy18lXsjqaafU9haMi+rFCh2ZZT20xo3Dug/qmow= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=V3cue/r4; arc=none smtp.client-ip=198.175.65.21 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="V3cue/r4" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1779270963; x=1810806963; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=L+UFOsAszlV+duz1urRSW6QFal0eGvHWNO6OglS4mU0=; b=V3cue/r4z9w6CeoFmT135dP78P9Zir4dMxsA0BuBg0NSurAWJ5TwLMmi nZdevkFoLa9laT9/bOzk4CEcPmgKEKQFJOIofAOfC548Ow4QuLmuzxUcx 8FWakSTvtPJFG6WA9B+5Lxjuns3yY2abqugO3XrYbfx5GqN1rTDqSWplT nD2dtyvOweqNaIpgX21GlV5JZ+GkpgwmSvRKU5yH4KoMLxodAO3qysxja M1DeEl0cz/PjiqlJPgAw+Z/woujjppFMySr4Ma8XuFIOdb7R0ZKkjKzdK dypkahgPxDwCCPVJdDuYesIry2HfqecfCGRHvDVx53qhT9M4UHW547Zbh g==; X-CSE-ConnectionGUID: oVT2aOpXR62x7QGcjSPtaQ== X-CSE-MsgGUID: pGQDKdnSSBC9FgmrvtPHUw== X-IronPort-AV: E=McAfee;i="6800,10657,11791"; a="80067281" X-IronPort-AV: E=Sophos;i="6.23,244,1770624000"; d="scan'208";a="80067281" Received: from orviesa006.jf.intel.com ([10.64.159.146]) by orvoesa113.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 May 2026 02:56:03 -0700 X-CSE-ConnectionGUID: 99ruAICXTqW2v2z4i6Wm2Q== X-CSE-MsgGUID: BUrg6QU5RnOtkxDiLCv1vQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,244,1770624000"; d="scan'208";a="239120721" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa006.jf.intel.com with ESMTP; 20 May 2026 02:56:01 -0700 Received: by black.igk.intel.com (Postfix, from userid 1001) id DC52295; Wed, 20 May 2026 11:55:59 +0200 (CEST) Date: Wed, 20 May 2026 11:55:59 +0200 From: Mika Westerberg To: linux-usb@vger.kernel.org Cc: Yehezkel Bernat , Lukas Wunner , Andreas Noever , Alan Borzeszkowski , Pooja Katiyar , Rene Sapiens , Gil Fine Subject: Re: [PATCH 0/8] thunderbolt: Make the driver follow CM guide more closely Message-ID: <20260520095559.GD8580@black.igk.intel.com> References: <20260512122955.271688-1-mika.westerberg@linux.intel.com> Precedence: bulk X-Mailing-List: linux-usb@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260512122955.271688-1-mika.westerberg@linux.intel.com> On Tue, May 12, 2026 at 02:29:47PM +0200, Mika Westerberg wrote: > Hi all, > > This series includes various improvements to make the Thunderbolt/USB4 > driver follow the USB4 Connection Manager guide more closely (and hopefully > work better with wider range of USB4 devices). There is also one > improvement for DisplayPort tunneling with more than 2 tunnels when > bandwidth allocation mode is enabled. > > Alan Borzeszkowski (1): > thunderbolt: Improve multi-display DisplayPort tunnel allocation > > Gil Fine (6): > thunderbolt: Fix lane bonding log when bonding not possible > thunderbolt: Activate path hops from source to destination > thunderbolt: Verify PCIe adapter in detect state before tunnel setup > thunderbolt: Verify Router Ready bit is set after router enumeration > thunderbolt: Increase timeout for Configuration Ready bit > thunderbolt: Increase Notification Timeout to 255 ms for USB4 routers > > Pooja Katiyar (1): > thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() All applied to thunderbolt.git/next.