From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Chen Yu <chenyu56@huawei.com>, Jun Li <jun.li@nxp.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] device connection: Add support for device graphs
Date: Fri, 25 Jan 2019 16:15:11 +0300 [thread overview]
Message-ID: <20190125131519.88416-1-heikki.krogerus@linux.intel.com> (raw)
Hi,
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 (8):
platform/x86: intel_cht_int33fe: Remove connection for the alt mode
mux
usb: typec: Rationalize the API for the muxes
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 | 63 ++++++++++++++++-
drivers/platform/x86/intel_cht_int33fe.c | 11 ++-
drivers/usb/roles/class.c | 21 +++++-
drivers/usb/typec/class.c | 31 ++++++---
drivers/usb/typec/mux.c | 86 +++++++++++++++++++-----
include/linux/device.h | 6 ++
include/linux/usb/role.h | 1 +
include/linux/usb/typec_mux.h | 3 +-
8 files changed, 185 insertions(+), 37 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-25 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 13:15 Heikki Krogerus [this message]
2019-01-25 13:15 ` [PATCH 1/8] platform/x86: intel_cht_int33fe: Remove connection for the alt mode mux Heikki Krogerus
2019-01-28 9:45 ` Andy Shevchenko
2019-01-28 10:44 ` Hans de Goede
2019-01-28 15:27 ` Heikki Krogerus
2019-01-31 10:04 ` Hans de Goede
2019-01-25 13:15 ` [PATCH 2/8] usb: typec: Rationalize the API for the muxes Heikki Krogerus
2019-01-28 9:50 ` Andy Shevchenko
2019-01-28 15:28 ` Heikki Krogerus
2019-01-25 13:15 ` [PATCH 3/8] device connection: Add fwnode member to struct device_connection Heikki Krogerus
2019-01-25 13:15 ` [PATCH 4/8] usb: typec: mux: Find the muxes by also matching against the device node Heikki Krogerus
2019-01-28 9:53 ` Andy Shevchenko
2019-01-28 15:46 ` Heikki Krogerus
2019-01-28 16:17 ` Andy Shevchenko
2019-01-25 13:15 ` [PATCH 5/8] usb: roles: " Heikki Krogerus
2019-01-25 13:15 ` [PATCH 6/8] usb: typec: Find the ports " Heikki Krogerus
2019-01-25 13:15 ` [PATCH 7/8] device connection: Prepare support for firmware described connections Heikki Krogerus
2019-01-25 13:15 ` [PATCH 8/8] device connection: Find device connections also from device graphs Heikki Krogerus
2019-01-28 9:58 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190125131519.88416-1-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=chenyu56@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome