Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1415034
| From | Heikki Krogerus <heikki.krogerus@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCHv2] usb: USB Type-C Connector Class |
| Date | 2016-06-06 15:30 +0200 |
| Message-ID | <rH2Lo-5ut-29@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <rFDvI-87Q-15@gated-at.bofh.it> <rFXkK-3Fl-37@gated-at.bofh.it> <rFXNM-3QL-25@gated-at.bofh.it> <rFZ3c-4VQ-23@gated-at.bofh.it> <rG2kq-6QU-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jun 03, 2016 at 11:39:27AM -0700, Guenter Roeck wrote: > On Fri, Jun 03, 2016 at 06:17:46PM +0300, Heikki Krogerus wrote: > [ ... ] > > > > > > > > > > In my test case, this gives me > > > > > /sys/class/type-c/usbc0/ > > > > > usbc0.svid:18d1 > > > > > usbc0.svid:18d1/mode0 > > > > > usbc0.svid:18d1/mode0/vdo > > > > > usbc0.svid:18d1/mode0/description > > > > > usbc0.svid:18d1/mode0/active > > > > > ... > > > > > usbc0.svid:ff01 > > > > > usbc0.svid:ff01/mode0/vdo > > > > > usbc0.svid:ff01/mode0/description > > > > > usbc0.svid:ff01/mode0/active > > > > > > Side note: I didn't provide a description/name for the modes, because that > > > would result in something like usbc0.DisplayPort/ instead of usbc0.svid:ff01/, > > > and I prefer a consistent ABI. Since this _is_ part of the ABI, would it make > > > sense to standardize on names for modes in sysfs ? For example, how should > > > a "Display Port" mode directory be named ? It doesn't sound good if I > > > use "usbc0.svid:ff01", someone else uses "usbc0.DisplayPort", and yet > > > someone else uses "usbc0.displayport". > > > > Yeah, let's make them standard. > > > Any name preferences ? I would prefer lower case letters. I don't know the SIDs there are at them moment, other then Display Port. Do you know them? I don't think we can ever guarantee that in every case we will be able to provide a human readable name for the alternate modes if they are vendor defined. We will then potentially still have the names in two different forms: "usbc0.displayport" and "usbc0.svid:xxxx". Is that something acceptable to everybody? I guess if it's not, then to only way to go forward would be to always just use the svid in the name. > > > Also, do we at some point need to standardize the ABI for the standard > > > alternate modes such as DisplayPort (if there are any - again I am not > > > there yet) ? > > > > I don't have an answer to that. > > > Ok, I'll look into it as I proceed with my implementation. > > > > > > > Sounds good to me. Many other subsystems do the same, ie create the subsystem > > > device(s) during registration with the subsystem, so this is in line with other > > > kernel code. > > > > > > Should I send you a follow-up patch on top of yours ? > > > > Sure. I'm a little bit stuck with an other tasks, so let's keep this > > thing rolling. > > > See below. Thanks. I pushed it to my work branch for this class: https://github.com/krohei/linux/commits/typec_class There are still a few open questions, but I'm in any case going to start polishing the driver. I think the other attributes are more or less decided, excluding the alternate modes. Cheers, -- heikki
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Oliver Neukum <oneukum@suse.com> - 2016-06-01 11:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Guenter Roeck <linux@roeck-us.net> - 2016-06-02 01:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Oliver Neukum <oneukum@suse.com> - 2016-06-02 08:40 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-02 10:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-02 12:20 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Guenter Roeck <linux@roeck-us.net> - 2016-06-02 18:20 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-03 15:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Guenter Roeck <linux@roeck-us.net> - 2016-06-03 16:00 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-03 17:20 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Guenter Roeck <linux@roeck-us.net> - 2016-06-03 20:50 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-06 15:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Oliver Neukum <oneukum@suse.com> - 2016-06-06 15:40 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-07 10:30 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Guenter Roeck <linux@roeck-us.net> - 2016-06-07 19:00 +0200
Re: [RFC PATCHv2] usb: USB Type-C Connector Class Heikki Krogerus <heikki.krogerus@linux.intel.com> - 2016-06-02 10:10 +0200
csiph-web