From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Jun Li <jun.li@nxp.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Chen Yu <chenyu56@huawei.com>,
Hans de Goede <hdegoede@redhat.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/9] device connection: Add support for device graphs
Date: Tue, 12 Feb 2019 13:31:16 +0200 [thread overview]
Message-ID: <20190212113116.GD32070@kuha.fi.intel.com> (raw)
In-Reply-To: <VI1PR04MB4558A1B67430533C843EA47D89650@VI1PR04MB4558.eurprd04.prod.outlook.com>
On Tue, Feb 12, 2019 at 10:44:35AM +0000, Jun Li wrote:
> Hi
> > -----Original Message-----
> > From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > Sent: 2019年1月31日 0:03
> > To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Andy Shevchenko <andy.shevchenko@gmail.com>; 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 v2 0/9] device connection: Add support for device graphs
> >
> > 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://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%
> > 2Flkml%2F2018%2F10%2F24%2F619&data=02%7C01%7Cjun.li%40nxp.co
> > m%7C2fd7c8c28d67434354be08d686cc6b55%7C686ea1d3bc2b4c6fa92cd99c5c
> > 301635%7C0%7C0%7C636844609858846167&sdata=AWDD9WaO%2BXxM
> > Izlli6GUNEq%2FqUpa5hSyLbBsjICdLIo%3D&reserved=0
> >
> > 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
>
> I tested this series on dwc3+typec, for usb role switch and typec switch common part
> Reviewed-by: Jun Li <jun.li@nxp.com>
> Tested-by: Jun Li <jun.li@nxp.com>
Thanks Jun.
I'm going to send one more version, and fix the description of the
struct usb_role_switch_desc like you proposed.
Since the fix will only add one comment line to the code, I'm going to
take the liberty to add your Reviewed-by and Tested-by tags this
time (I don't usually like to carry them to new versions of patches).
I'll do the same with the others.
thanks,
--
heikki
next prev parent reply other threads:[~2019-02-12 11:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:02 [PATCH v2 0/9] device connection: Add support for device graphs Heikki Krogerus
2019-01-31 10:06 ` Hans de Goede
2019-01-31 13:36 ` Heikki Krogerus
2019-02-12 10:44 ` Jun Li
2019-02-12 11:31 ` Heikki Krogerus [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 16:02 [v2,1/9] platform/x86: intel_cht_int33fe: Prepare for better mux naming scheme Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 1/9] " Heikki Krogerus
2019-01-30 16:02 [v2,2/9] usb: typec: Rationalize the API for the muxes Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 2/9] " Heikki Krogerus
2019-01-30 16:02 [v2,3/9] platform/x86: intel_cht_int33fe: Remove old style mux connections Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 3/9] " Heikki Krogerus
2019-01-30 16:02 [v2,4/9] device connection: Add fwnode member to struct device_connection Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 4/9] " Heikki Krogerus
2019-01-30 16:02 [v2,5/9] usb: typec: mux: Find the muxes by also matching against the device node Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 5/9] " Heikki Krogerus
2019-01-30 16:02 [v2,6/9] usb: roles: " Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 6/9] " Heikki Krogerus
2019-01-30 16:02 [v2,7/9] usb: typec: Find the ports " Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 7/9] " Heikki Krogerus
2019-01-30 16:02 [v2,8/9] device connection: Prepare support for firmware described connections Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 8/9] " Heikki Krogerus
2019-01-30 16:02 [v2,9/9] device connection: Find device connections also from device graphs Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 9/9] " Heikki Krogerus
2019-01-30 16:51 [v2,7/9] usb: typec: Find the ports by also matching against the device node Andy Shevchenko
2019-01-30 16:51 ` [PATCH v2 7/9] " Andy Shevchenko
2019-01-31 13:35 [v2,7/9] " Heikki Krogerus
2019-01-31 13:35 ` [PATCH v2 7/9] " Heikki Krogerus
2019-02-11 8:39 [v2,7/9] " Heikki Krogerus
2019-02-11 8:39 ` [PATCH v2 7/9] " Heikki Krogerus
2019-02-11 9:58 [v2,6/9] usb: roles: Find the muxes " Jun Li
2019-02-11 9:58 ` [PATCH v2 6/9] " Jun Li
2019-02-11 10:46 [v2,6/9] " Heikki Krogerus
2019-02-11 10:46 ` [PATCH v2 6/9] " Heikki Krogerus
2019-02-11 11:52 [v2,7/9] usb: typec: Find the ports " Andy Shevchenko
2019-02-11 11:52 ` [PATCH v2 7/9] " Andy Shevchenko
2019-02-11 12:40 [v2,6/9] usb: roles: Find the muxes " Heikki Krogerus
2019-02-11 12:40 ` [PATCH v2 6/9] " Heikki Krogerus
2019-02-12 6:03 [v2,6/9] " Jun Li
2019-02-12 6:03 ` [PATCH v2 6/9] " Jun Li
2019-02-12 8:50 [v2,6/9] " Heikki Krogerus
2019-02-12 8:50 ` [PATCH v2 6/9] " Heikki Krogerus
2019-02-12 10:41 [v2,6/9] " Jun Li
2019-02-12 10:41 ` [PATCH v2 6/9] " Jun Li
2019-02-12 11:24 [v2,6/9] " Heikki Krogerus
2019-02-12 11:24 ` [PATCH v2 6/9] " Heikki Krogerus
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=20190212113116.GD32070@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.shevchenko@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.