linux-kernel - Re: [PATCH 0/6] usb: typec: and platform/chrome: Add PD revision numbers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YBgRDwszRs3ULl5J@kroah.com>
Date:   Mon, 1 Feb 2021 15:32:47 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Benson Leung <bleung@...omium.org>
Cc:     heikki.krogerus@...ux.intel.com, enric.balletbo@...labora.com,
        pmalani@...omium.org, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org, groeck@...omium.org,
        bleung@...gle.com
Subject: Re: [PATCH 0/6] usb: typec: and platform/chrome: Add PD revision
 numbers

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.

thanks,

greg k-h