[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181024150525.11552-1-heikki.krogerus@linux.intel.com>
Date: Wed, 24 Oct 2018 18:05:20 +0300
From: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To: Heiko Stuebner <heiko@...ech.de>
Cc: Guenter Roeck <linux@...ck-us.net>,
Hans de Goede <hdegoede@...hat.com>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/5] Adding graph handling to device connection API
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(-)
--
2.19.1
Powered by blists - more mailing lists