Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 1 Feb 2021 23:04:15 -0800
From:   Benson Leung <bleung@google.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Benson Leung <bleung@chromium.org>,
        heikki.krogerus@linux.intel.com, enric.balletbo@collabora.com,
        pmalani@chromium.org, linux-usb@vger.kernel.org,
        linux-kernel@vger.kernel.org, groeck@chromium.org
Subject: Re: [PATCH 0/6] usb: typec: and platform/chrome: Add PD revision
 numbers
Message-ID: <YBj5b7O60c6fh/nX@google.com>
References: <20210129061406.2680146-1-bleung@chromium.org>
 <YBgRDwszRs3ULl5J@kroah.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="1IvyEnSOqD3CMctJ"
Content-Disposition: inline
In-Reply-To: <YBgRDwszRs3ULl5J@kroah.com>
Precedence: bulk


--1IvyEnSOqD3CMctJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
> >=20
> > This series adds individual version numbers for the partner and the cab=
le,
> > and exposes them in the appropriate sysfs in /sys/class/typec.
> >=20
> > I provide as a first implementation of this, platform/chrome's cros_ec_=
typec
> > driver, whose underlying status messages convey the SOP and SOP' revisi=
ons
> > already.
>=20
> 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.
>=20

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?

Thanks,
Benson

> thanks,
>=20
> greg k-h

--=20
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

--1IvyEnSOqD3CMctJ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQCtZK6p/AktxXfkOlzbaomhzOwwgUCYBj5bwAKCRBzbaomhzOw
wmOeAP9tpkaoJbsMmmBb8CaB4fT4OlvcvCI222T6Xwxilxga3AEAmnf9GyFgKA9l
KJx1cTrAZkAO+qGYZ1WTes/3ZVDYbAQ=
=y8Hq
-----END PGP SIGNATURE-----

--1IvyEnSOqD3CMctJ--