On Mon, Feb 01, 2021 at 11:04:15PM -0800, Benson Leung wrote: > Hi Greg, > > On Mon, Feb 01, 2021 at 03:32:47PM +0100, Greg KH wrote: > > On Thu, Jan 28, 2021 at 10:14:00PM -0800, Benson Leung wrote: > > > USB Power Delivery has a 3 entity handshake (port, cable, partner), and as > > > of USB PD R3.0, each entity may independently support either Revision 2 or > > > Revision 3 signaling and protocol. In order for userspace and the kernel > > > to properly process the data objects received from a particular SOP*, we > > > must know to which revision of the spec each conforms. > > > > > > This series adds individual version numbers for the partner and the cable, > > > and exposes them in the appropriate sysfs in /sys/class/typec. > > > > > > I provide as a first implementation of this, platform/chrome's cros_ec_typec > > > driver, whose underlying status messages convey the SOP and SOP' revisions > > > already. > > > > I've taken the first 3 patches in my tree now, but the last 3 (for the > > chrome_ec_typec.c driver), they do not apply at all. > > > > Ah, that's because we have some other changes for the cros_ec_typec.c driver > already in platform/chrome for our 5.12 branch. > > For 5.12, the changes for cros_ec_typec driver is pretty well contained, > although there is some dependence on typec subsystem changes now. > > If I send you a pull request containing all of the changes for this driver we > have already merged, plus these last three that depend on both of our trees > would you merge it through usb for 5.12? If the subsystem maintainer says it is ok, yes, I will be glad to take a stable git tag to pull from into my usb-next branch. thanks, greg k-h