Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6054749imu; Wed, 30 Jan 2019 08:04:02 -0800 (PST) X-Google-Smtp-Source: ALg8bN7t5RglD8nptWGW+jXB3+Tf/3S2qsaZNvbIxHgKpp+qKD6RhBlonFW45SBHuqbki2PshIW9 X-Received: by 2002:a17:902:8f97:: with SMTP id z23mr31245067plo.283.1548864242545; Wed, 30 Jan 2019 08:04:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548864242; cv=none; d=google.com; s=arc-20160816; b=fIacgfgAIVoXq9uC47aDz5AnyBg2TZqvrHJAImviJBOM5WTR2RCRaBQWaImW34DiOL XD5w6r6bPyYfJn8/Jbm/7n1oYwG+WKDCSyTasXG+rxHgCPIQJFBSxsS/QIQzcjuJHewE evKorvldxQuTVdQQf1uNLBYuTjdGhaGnQqq2yuCdIKzhtKQmmfxFeRrAPw2zu4ud2Arc zgSpCsBPyBGXI2z68mO7htAMUeXAhmldf1s8pyL3Ycgeyh6Vt3mMzxd//UvZWkt29jPA h+3v2ChQfk95MbksKblTT8AmASC3hvNOlVNR2yQUG0Z824aTdLBeANbQuHnI0z7wzpnp MGNA== 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 :message-id:date:subject:cc:to:from; bh=4AbisqtOuUrnMTnzenEaUQvjJcaShwoCpyzomQgysUk=; b=HoV9BAnqziI0aYt41bqgMJs4BZeIbkJclt+J/3/hR5xvkoDD7ascCvYaU3zWJwx/u9 Epm1FoHgf5e0jrg22BMzIeS1Tgxkd8krTqsVU0sq6YYYMd+PXLUj45t8Xcf1PIBynTTG S8EmO2TjIbh/6Htojm+VChLoszfpzm84LeICh5X5mbod7y/x/7YA+CyvfsXdhsm/no36 2F8XuF4dcGal67nt4VbLKK74nVWt8StyoBGim/GE1Sm1dRmvB26n8n9wxpuE1ZqDpp2u HmG1wQ3685FqzTFCUk7mkEmBbRzXN+6B32+RWqZIiRrjRGlQe2OJdceNEhAW6hNSitjx qqXg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i63si1619689pge.515.2019.01.30.08.03.34; Wed, 30 Jan 2019 08:04:02 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731822AbfA3QDD (ORCPT + 99 others); Wed, 30 Jan 2019 11:03:03 -0500 Received: from mga02.intel.com ([134.134.136.20]:60152 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728943AbfA3QDD (ORCPT ); Wed, 30 Jan 2019 11:03:03 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2019 08:03:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,541,1539673200"; d="scan'208";a="142760833" Received: from black.fi.intel.com (HELO black.fi.intel.com.) ([10.237.72.28]) by fmsmga001.fm.intel.com with ESMTP; 30 Jan 2019 08:03:00 -0800 From: Heikki Krogerus To: Greg Kroah-Hartman Cc: Andy Shevchenko , Chen Yu , Jun Li , Hans de Goede , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/9] device connection: Add support for device graphs Date: Wed, 30 Jan 2019 19:02:50 +0300 Message-Id: <20190130160259.46919-1-heikki.krogerus@linux.intel.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This is the second version of this series. On top the two code style improvements requested by Andy, I also renamed the connection identifiers used with the USB Type-C muxes for something that I felt are better, especially after we start using them to name reference device properties in fwnodes. That's why the first patch is now split in two, 1/9 and 3/9. Hans! Please note that there is no functional change. The alt mode device is still getting a handle to the mux, just like before. That was actually happening also in the first version of the series. The commit message from v1: This series adds support for OF and ACPI device graph parsing to the device connection API. Handling the graph is straightforward, but because I'm adding that fwnode member to struct device_connection, I had to make sure all the existing users consider it. The plan is to only support matching with fwnode in the future, so no more device name matching. The software fwnodes that we now have in kernel should make that possible, once we add support for references to them. The original RFC: https://lkml.org/lkml/2018/10/24/619 thanks, Heikki Krogerus (9): platform/x86: intel_cht_int33fe: Prepare for better mux naming scheme usb: typec: Rationalize the API for the muxes platform/x86: intel_cht_int33fe: Remove old style mux connections device connection: Add fwnode member to struct device_connection usb: typec: mux: Find the muxes by also matching against the device node usb: roles: Find the muxes by also matching against the device node usb: typec: Find the ports by also matching against the device node device connection: Prepare support for firmware described connections device connection: Find device connections also from device graphs drivers/base/devcon.c | 62 ++++++++++++++- drivers/platform/x86/intel_cht_int33fe.c | 15 ++-- drivers/usb/roles/class.c | 21 +++++- drivers/usb/typec/class.c | 31 ++++++-- drivers/usb/typec/mux.c | 96 ++++++++++++++++++++---- include/linux/device.h | 6 ++ include/linux/usb/role.h | 1 + include/linux/usb/typec_mux.h | 3 +- 8 files changed, 195 insertions(+), 40 deletions(-) -- 2.20.1