From: Guenter Roeck <linux@roeck-us.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Oliver Neukum <oneukum@suse.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Roger Quadros <rogerq@ti.com>,
Rajaram R <rajaram.officemail@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCHv4 0/2] USB Type-C Connector class
Date: Tue, 9 Aug 2016 09:23:36 -0700 [thread overview]
Message-ID: <20160809162336.GB9105@roeck-us.net> (raw)
In-Reply-To: <20160809140153.GA9104@kroah.com>
On Tue, Aug 09, 2016 at 04:01:53PM +0200, Greg KH wrote:
> On Wed, Jun 29, 2016 at 04:38:36PM +0300, Heikki Krogerus wrote:
> > Hi,
> >
> > The USB Type-C class is meant to provide unified interface to the
> > userspace to present the USB Type-C ports in a system.
> >
> > Changes since v3:
> > - Documentation cleanup as proposed by Roger Quadros
> > - Setting partner altmodes member to NULL on removal and fixing a
> > warning, as proposed by Guenter Roeck
> > - Added the following attributes for partners and cables:
> > * supports_usb_power_delivery
> > * id_header_vdo
> > - "id_header_vdo" is visible only when the partner or cable supports
> > USB Power Delivery communication.
> > - Partner attribute "accessory" is hidden when the partner type is not
> > "Accessory".
> >
> > Changes since v2:
> > - Notification on role and alternate mode changes
> > - cleanups
> >
> > Changes since v1:
> > - Completely rewrote alternate mode support
> > - Patners, cables and cable plugs presented as devices.
>
> I'm not going to take this series until everyone agrees on it, sorry.
> I'll wait for you and Guenter and Oliver to all come up with a solution
> that works for everyone.
>
I have not heard from Heikko for a while. There have been some follow-up
patches in
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/log/?h=bxt-typec-pd-fixes
but I am not really sure where this is going. I've been wondering if I
can/should get more actively involved and start driving the series if
Heikki is busy. Thoughts, anyone ?
Guenter
next prev parent reply other threads:[~2016-08-09 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 13:38 Heikki Krogerus
2016-06-29 13:38 ` [PATCHv4 1/2] usb: USB Type-C connector class Heikki Krogerus
2016-06-30 17:10 ` Guenter Roeck
2016-07-01 7:38 ` Heikki Krogerus
2016-07-01 14:41 ` Guenter Roeck
2016-06-30 22:02 ` Guenter Roeck
2016-07-01 7:13 ` Heikki Krogerus
2016-07-01 12:05 ` Heikki Krogerus
2016-07-01 14:33 ` Guenter Roeck
2016-07-03 19:38 ` Heikki Krogerus
2016-07-03 21:28 ` Guenter Roeck
2016-07-04 17:11 ` Heikki Krogerus
2016-07-04 17:45 ` Guenter Roeck
2016-07-05 18:47 ` Heikki Krogerus
2016-06-29 13:38 ` [PATCHv4 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2016-08-09 14:01 ` [PATCHv4 0/2] USB Type-C Connector class Greg KH
2016-08-09 16:23 ` Guenter Roeck [this message]
2016-08-10 8:19 ` Oliver Neukum
2016-08-16 7:38 ` Heikki Krogerus
2016-08-16 16:40 ` Guenter Roeck
2016-08-17 7:44 ` Heikki Krogerus
2016-08-10 9:20 ` Felipe Balbi
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=20160809162336.GB9105@roeck-us.net \
--to=linux@roeck-us.net \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=rajaram.officemail@gmail.com \
--cc=rogerq@ti.com \
/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
all inboxes | Powered by JetHome®