Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp65026ybn; Thu, 3 Oct 2019 01:29:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqyeuEJnh5XYLRSdkAXYP2SiPt3C4aJgRNIz22CcEPkU7zuEVGopvHd5IffXsYjE+57S7Sr/ X-Received: by 2002:a17:906:244a:: with SMTP id a10mr6649936ejb.137.1570091363328; Thu, 03 Oct 2019 01:29:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570091363; cv=none; d=google.com; s=arc-20160816; b=uPh6Wx+Mn7p2u2kixHyVM7GBY0FNS94HfbfG23vqhmx8LkWOLw4+D4iokyy/qjoKFP AfgBNKkWIg/tr54nsm8pJRmb3wTN4Y9AT618oFFOd0c/Trs2KIIl+0RH3JWGdKuGIm97 5WuETSxTlgKrF9MDFKgx//DUb6R/SvTkjdQVL5YrKxSy9YhZmO+xs6fxi2Z+Km8oHbto SjeRof8TuzO5/kd9vqKD3BsXaLVFWA2ptxYworm/3xHyWBH9OzgvTXOV/XY2c4JB2nyV kFx4FlrhalY5VgeSeSSD3j9FcbL/7PYM5MA2TP5K0q6QytyspVS+Cxz2UFitBYdjAt/Y Hi/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=pwW4V19YYxbp36LNTXOWgJ5QzTU3Jaj8irMyul1wzwU=; b=gA88yu5kXiVQGfOKiG2z8Yizq3YN4XxXbdZ4lD/lH7mhu3j30gAdfBqfHxza3rFO8p 8fKOtOt9uMgkirunInG4gePFheuhn/CkOYsQhVXkuZZnPA3red7INaBTacnAGisXzzhZ jgOdV3PdknmvoN5odA1TrsNC7DJV2NWX57B4iC0H0SZveVQxqJ7jB/0n+yShLigp0TkI a9SVH4ZYqWAtKUZ7Zho+QWunmrOgHMewKZlm5fevjhasHNqK0QG/y+skfySTpc3mOHQc MIaAhpYbEv5cee/x3kJa8U13/X/nzKRZ9Kxzk8xds4YNvCjXrkT6osEWDwkil4nIYRA8 LCew== ARC-Authentication-Results: i=1; mx.google.com; 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 z11si1025087edl.1.2019.10.03.01.28.55; Thu, 03 Oct 2019 01:29:23 -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; 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 S1728264AbfJCIZj (ORCPT + 99 others); Thu, 3 Oct 2019 04:25:39 -0400 Received: from mx2.suse.de ([195.135.220.15]:58292 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727357AbfJCIZj (ORCPT ); Thu, 3 Oct 2019 04:25:39 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id B38BEADAB; Thu, 3 Oct 2019 08:25:35 +0000 (UTC) Message-ID: <1570091132.18913.3.camel@suse.com> Subject: Re: [RFC PATCH 06/22] thunderbolt: Add support for lane bonding From: Oliver Neukum To: Mika Westerberg Cc: Anthony Wong , Mario.Limonciello@dell.com, Andreas Noever , Yehezkel Bernat , Michael Jamet , Rajmohan Mani , Greg Kroah-Hartman , Nicholas Johnson , Alan Stern , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, Lukas Wunner Date: Thu, 03 Oct 2019 10:25:32 +0200 In-Reply-To: <20191002143020.GG2819@lahna.fi.intel.com> References: <20191001113830.13028-1-mika.westerberg@linux.intel.com> <20191001113830.13028-7-mika.westerberg@linux.intel.com> <20191001123808.GA2954373@kroah.com> <20191001125320.GN2714@lahna.fi.intel.com> <1570026066.2472.15.camel@suse.com> <20191002143020.GG2819@lahna.fi.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, den 02.10.2019, 17:30 +0300 schrieb Mika Westerberg: > On Wed, Oct 02, 2019 at 04:21:06PM +0200, Oliver Neukum wrote: > > Am Dienstag, den 01.10.2019, 15:53 +0300 schrieb Mika Westerberg: > > > > > > > > Are we only going to be allowed to "bond" two links together? Or will > > > > we be doing more than 2 in the future? If more, then we might want to > > > > think of a different way to specify these... > > > > > > AFAICT only two lanes are available in USB4. This goes over USB type-C > > > using the two lanes there. > > > > > > Of course I don't know if in future there will be USB4 1.1 or something > > > that adds more lanes so if you think there is a better way to specify > > > these, I'm happy to implement that instead :) > > > > If this ever can become asymmetric this interface is going to turn > > around and bite. > > Don't think it can be asymmetric but I'm open to all ideas how to make > it more flexible :-) Split the the attributes into link_speed_rx and link_speed_tx. For link_width likewise. We had the same issue with USB. Regards Oliver