| Message ID | 20181024150525.11552-1-heikki.krogerus@linux.intel.com (mailing list archive) |
|---|---|
| Headers | show
Return-Path: <linux-usb-owner@kernel.org>
Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org
[172.30.200.125])
by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 4A7B614BB
for <patchwork-linux-usb@patchwork.kernel.org>;
Wed, 24 Oct 2018 15:05:32 +0000 (UTC)
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 2EE461FFB1
for <patchwork-linux-usb@patchwork.kernel.org>;
Wed, 24 Oct 2018 15:05:30 +0000 (UTC)
Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486)
id 232D82A343; Wed, 24 Oct 2018 15:05:30 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
pdx-wl-mail.web.codeaurora.org
X-Spam-Level:
X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI,
RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 88E071FFB1
for <patchwork-linux-usb@patchwork.kernel.org>;
Wed, 24 Oct 2018 15:05:29 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S1726505AbeJXXdz (ORCPT
<rfc822;patchwork-linux-usb@patchwork.kernel.org>);
Wed, 24 Oct 2018 19:33:55 -0400
Received: from mga12.intel.com ([192.55.52.136]:34388 "EHLO mga12.intel.com"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1726497AbeJXXdz (ORCPT <rfc822;linux-usb@vger.kernel.org>);
Wed, 24 Oct 2018 19:33:55 -0400
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga001.fm.intel.com ([10.253.24.23])
by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
24 Oct 2018 08:05:28 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.54,420,1534834800";
d="scan'208";a="102104667"
Received: from black.fi.intel.com (HELO black.fi.intel.com.) ([10.237.72.28])
by fmsmga001.fm.intel.com with ESMTP; 24 Oct 2018 08:05:26 -0700
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
Hans de Goede <hdegoede@redhat.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/5] Adding graph handling to device connection API
Date: Wed, 24 Oct 2018 18:05:20 +0300
Message-Id: <20181024150525.11552-1-heikki.krogerus@linux.intel.com>
X-Mailer: git-send-email 2.19.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-usb-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-usb.vger.kernel.org>
X-Mailing-List: linux-usb@vger.kernel.org
X-Virus-Scanned: ClamAV using ClamSMTP
|
| Series |
Adding graph handling to device connection API
|
expand
|
Hi, I'm only presenting my idea with these how I think we should be able to deal with graphs in the API, so these are completely untested, and obviously I can't say for certain if the idea works or not. I will try to test these using custom ACPI tables, but of course these should be tested on DT platform as well, so if somebody can do that, I would much appreciate. Thanks, Heikki Krogerus (5): driver core: 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 drivers core: Find device connections also from device graphs drivers/base/devcon.c | 48 +++++++++++++++++++++++++++++++++++--- drivers/usb/common/roles.c | 16 ++++++++++--- drivers/usb/typec/class.c | 19 ++++++++++++--- drivers/usb/typec/mux.c | 19 +++++++++++---- include/linux/device.h | 6 +++++ 5 files changed, 95 insertions(+), 13 deletions(-)