Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2050676imm; Sun, 9 Sep 2018 14:46:50 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZvh+6nH/ICHZGyHMYWc0OxtlOcXjI61AjMsllrmkVXZpiDcZf9JNO7tv/WiDqBsSoiMI+q X-Received: by 2002:a63:fd06:: with SMTP id d6-v6mr19036021pgh.348.1536529610203; Sun, 09 Sep 2018 14:46:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536529610; cv=none; d=google.com; s=arc-20160816; b=KHjBnKA1C7YJKaYm7DqYBTaRzt/9cirM5ck83vLueO5siLh+XtnQ/VPx+ciMnTH66l lHLQPQjbB+/gWDTRTvRFVNCHXeAQmaKY/4qm8Y7ehBVY6Lrhx1K5Pe7Mo8NaL4axA4zh +4TqoMw3p3zwaG5bkjCoGxzT3Rvy2dTdqZdz9Tr6W6n+BsBq2ImefxW/Jumsz39UutcY pxZ0FSemKCHh2WkS02RGl3Pc65WmXHBBceAAiojFlmeb6LJs5zFX66KfwVIrGJVWRKZh 9qQEJcMwwQ7hCjo7qYVKP/PDisEcGy1JtWDbYIMv0UWUkKW5L+/rmEus2uCbDoFQtG1l /0dA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:date:from:message-id; bh=PTFJwF8rH+Yg33Pb6b4btuRjzd8AJ+8DgBtz3AoRf6E=; b=ZRx9mgjP/LmNLDwUGzYiTB9jI37XGlKOpTo3PQcIT0TpJ2nhVy4QShpyZved0QCtKF ZOvLgFlAwg4fOBTcHjYOZV2WoQLt3H22xyr2RiU153omTXrWWklRDdFFfgBGC4yeyCDd R4H1HcPRNp/DZaFFm4qMqpxG9b9BsFBltrwULHQOXJ7SDnTmVm20ydjWkykDKnO6Anlv k0kyBBpdT13phAt7sGyzCMP8F0SR9Suc2xf6rKzPW9UP/h4f5aZkJbP4EHFS2Ju6k+OR S/RIl3A9dTyB54kRl5C8YetPcvr7A9jZjR/ALDDh1LCP/UNiEUvsHV5AHSEEnkGB1JtQ 8kZQ== 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 r59-v6si14187844plb.39.2018.09.09.14.46.04; Sun, 09 Sep 2018 14:46:50 -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 S1726736AbeIJCdq (ORCPT + 99 others); Sun, 9 Sep 2018 22:33:46 -0400 Received: from bmailout2.hostsharing.net ([83.223.90.240]:42549 "EHLO bmailout2.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726658AbeIJCdp (ORCPT ); Sun, 9 Sep 2018 22:33:45 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout2.hostsharing.net (Postfix) with ESMTPS id D311C2800B3CC; Sun, 9 Sep 2018 23:42:40 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 5443EE542; Sun, 9 Sep 2018 23:42:40 +0200 (CEST) Message-Id: From: Lukas Wunner Date: Sun, 9 Sep 2018 23:42:01 +0200 Subject: [PATCH 0/5] Thunderbolt material for v4.20 To: Andreas Noever , Mika Westerberg , Michael Jamet , Yehezkel Bernat Cc: Stephen Hemminger , linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thunderbolt material for v4.20, comprising: * A fix to skip disabled ports on tunnel establishment. I am not aware that this has caused breakage in the real world so far, so no need to apply to v4.19 or backport to stable. * Obtain PCI slot number from DROM and use it to correlate PCI devices with Thunderbolt ports. * I am nominating myself as co-maintainer, see commit message for the reasons. Regarding the driver's verbosity which Stephen Hemminger and Mika Westerberg have taken exception to: * Patch [2/5] logs the PCI slot number as well as data whose purpose is unknown at KERN_INFO severity. I am not opposed to log the former at KERN_DEBUG severity, but the latter must stay at KERN_INFO to allow us to collect the data of various Thunderbolt devices in the wild and reverse-engineer its meaning. If Intel divulges the data's meaning then it need no longer be dumped. This would be ideal for everyone involved. * Patch [4/5] logs a message at KERN_INFO severity whenever a PCI device correlates or no longer correlates with a Thunderbolt port. I am not opposed to toning this down to KERN_DEBUG, subject to the introduction of tb_port_dbg(). Thanks, Lukas Lukas Wunner (5): thunderbolt: Skip disabled ports on tunnel establishment thunderbolt: Obtain PCI slot number from DROM thunderbolt: Move upstream_port to struct tb thunderbolt: Correlate PCI devices with Thunderbolt ports MAINTAINERS: Add Lukas Wunner as co-maintainer of thunderbolt MAINTAINERS | 1 + drivers/thunderbolt/Makefile | 2 +- drivers/thunderbolt/adapter_pci.c | 166 ++++++++++++++++++++++++++++++ drivers/thunderbolt/adapter_pci.h | 19 ++++ drivers/thunderbolt/domain.c | 12 +++ drivers/thunderbolt/eeprom.c | 21 ++++ drivers/thunderbolt/icm.c | 65 +++--------- drivers/thunderbolt/switch.c | 14 ++- drivers/thunderbolt/tb.c | 23 ++--- drivers/thunderbolt/tb.h | 45 ++++++++ include/linux/thunderbolt.h | 2 + 11 files changed, 305 insertions(+), 65 deletions(-) create mode 100644 drivers/thunderbolt/adapter_pci.c create mode 100644 drivers/thunderbolt/adapter_pci.h -- 2.18.0