Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8458560ybn; Tue, 1 Oct 2019 08:23:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzso3c+8dwaglVQL67CrDeDD3IgGeOBg8Q5q+waYtKSRGW6oTS3WCsA5+RhdkO4IvmWl5K8 X-Received: by 2002:a17:906:4541:: with SMTP id s1mr24873589ejq.210.1569943412587; Tue, 01 Oct 2019 08:23:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569943412; cv=none; d=google.com; s=arc-20160816; b=h2cC/ptsw1QokNVuvANkzu25DJKeXB/LKDh68tnLQ1Z8fWuh/vSQKbX3cdMvjVpG9K w+1d4amARtE8n4Rcwj/5G63+UaNonCaxbiso/2eAKncBI+qOSt4ZbTKmVnlNFadfIDzv paeG9jtZaOTYw42eIIKYDQq74YqCURfeipCq6rBsN5Wki2Ztxd2gEhuqE9E1aaNnCaX6 Rz7ixbDrTR8qVa8LKOrGe3Z+t2mMRMQINlI969yepsig2bfF9DZsAzGHlDPcyVzKvdkY GdoDuBYCpjxGTx1uaz9ywBDcnrMw2VxF4/massVScWdlK8dcNp5ZyepfY5YhNUXLjC6F Ecgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=xJgIc4rCo2Sye0atzOoK0FDArrcwvajjZAnXsH6TgDI=; b=XdDjWDvcK/LE9jhsWr0rrNus4s5TA42rYUVqnvdO5kmhlC7MNnwZ0vHNjmuAQ65+IB h6Cd86aIGx1qFmmaRzAAINNe8vv91V5RGCFtoswGpys3rtlkt8ZG0xqu0YcaVHZOYc3T DriXvZ2dSXy97xFUjy2jPa8DjKWOOcbcqApeIgxf74hRSDLcS1XX47YBgYcy0DQCqTZw Tp2Tm6KGKhu4BQBF6y5btktuNjiyaofDV52Cc1rsTGWSpzyx+cQT3CNug2viD7wsfO0A a9wg4ODMDO+MSWdOpUtvKN2AmgWfgtA1DU5dnSDIMMlalLzSqeFb3HeXBuDyJe0f/u0R ubSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fvEL0jE4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k6si9637173edb.235.2019.10.01.08.23.07; Tue, 01 Oct 2019 08:23:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fvEL0jE4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389388AbfJAPWQ (ORCPT + 99 others); Tue, 1 Oct 2019 11:22:16 -0400 Received: from mail.kernel.org ([198.145.29.99]:52278 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388297AbfJAPWQ (ORCPT ); Tue, 1 Oct 2019 11:22:16 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1C3FE2133F; Tue, 1 Oct 2019 15:22:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569943335; bh=5GP+QSX7Yk2tmYJ4KpVXLNoblO5/2HhaXJ2itK9FcI0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fvEL0jE45Dg2+2ZnHDbEHvYU1T0LP2UVJg/w316B00SmrzCjQcDvB2i03+f8i+b4b of0xBQjT29WTxJRmYKQLA0e/UHShJDTLAckq9YaBTUGaZTXWQk+TLB4l2cTjmTICbt pjuwPAW/hjFE5JW/70wvU4Y0QgEAJ0yoWfnUa0Hg= Date: Tue, 1 Oct 2019 17:22:13 +0200 From: Greg KH To: Mario.Limonciello@dell.com Cc: mika.westerberg@linux.intel.com, linux-usb@vger.kernel.org, andreas.noever@gmail.com, michael.jamet@intel.com, YehezkelShB@gmail.com, rajmohan.mani@intel.com, nicholas.johnson-opensource@outlook.com.au, lukas@wunner.de, stern@rowland.harvard.edu, anthony.wong@canonical.com, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 17/22] thunderbolt: Add initial support for USB4 Message-ID: <20191001152213.GB3450435@kroah.com> References: <20191001113830.13028-1-mika.westerberg@linux.intel.com> <20191001113830.13028-18-mika.westerberg@linux.intel.com> <20191001124748.GH2954373@kroah.com> <20191001130905.GO2714@lahna.fi.intel.com> <20191001145354.GA3366714@kroah.com> <924ce4d5862c4d859e238c0e706a3d5b@AUSX13MPC105.AMER.DELL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <924ce4d5862c4d859e238c0e706a3d5b@AUSX13MPC105.AMER.DELL.COM> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 01, 2019 at 02:59:06PM +0000, Mario.Limonciello@dell.com wrote: > > > > -----Original Message----- > > From: Greg Kroah-Hartman > > Sent: Tuesday, October 1, 2019 9:54 AM > > To: Mika Westerberg > > Cc: linux-usb@vger.kernel.org; Andreas Noever; Michael Jamet; Yehezkel Bernat; > > Rajmohan Mani; Nicholas Johnson; Lukas Wunner; Alan Stern; Limonciello, Mario; > > Anthony Wong; linux-kernel@vger.kernel.org > > Subject: Re: [RFC PATCH 17/22] thunderbolt: Add initial support for USB4 > > > > > > [EXTERNAL EMAIL] > > > > On Tue, Oct 01, 2019 at 04:09:05PM +0300, Mika Westerberg wrote: > > > On Tue, Oct 01, 2019 at 02:47:48PM +0200, Greg Kroah-Hartman wrote: > > > > > - Thunderbolt Controller driver. This driver is required if you > > > > > - want to hotplug Thunderbolt devices on Apple hardware or on PCs > > > > > - with Intel Falcon Ridge or newer. > > > > > + USB4 (Thunderbolt) driver. USB4 is the public spec based on > > > > > + Thunderbolt 3 protocol. This driver is required if you want to > > > > > + hotplug Thunderbolt and USB4 compliant devices on Apple > > > > > + hardware or on PCs with Intel Falcon Ridge or newer. > > > > > > > > Wait, did "old" thunderbolt just get re-branded as USB4? > > > > > > Not but the driver started supporting USB4 as well :) > > > > > > USB4 is pretty much public spec of Thunderbolt 3 but with some > > > differences in register layouts (this is because Thunderbolt uses some > > > vendor specific capabilities which are now moved to more "standard" > > > places). > > > > Ok, then we need to rename the Kconfig option as well, otherwise no one > > will "know" that this changed, so they will not be prompted for it. > > > > > > Because if I have an "old" laptop that needs Thunderbolt support, how am > > > > I going to know it is now called USB4 instead? > > > > > > Well the Kconfig option tries to have both names there: > > > > > > tristate "USB4 (Thunderbolt) support" > > > > > > and then > > > > > > USB4 (Thunderbolt) driver. USB4 is the public spec based on > > > Thunderbolt 3 protocol. This driver is required if you want to hotplug > > > Thunderbolt and USB4 compliant devices on Apple hardware or on PCs > > > with Intel Falcon Ridge or newer. > > > > > > and the Kconfig option is still CONFIG_THUNDERBOLT. I know this is > > > confusing but I don't have better ideas how we can advertise both. I > > > borrowed this "format" from firewire. > > > > CONFIG_USB4 instead? > > How about CONFIG_USB4_PCIE? > > I think that will help align that certain aspects of USB4 can be built optionally. What aspects? We don't have that here at all. I guess the parts of USB4 that are not just this "hook up the PCIe lane" that need to still be developed? thanks, greg k-h