From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v3 1/2] usb: typec: Consolidate syfs ABI documentation
Date: Tue, 10 Nov 2020 12:52:25 +0200 [thread overview]
Message-ID: <20201110105225.GH1224435@kuha.fi.intel.com> (raw)
In-Reply-To: <20201023214328.1262883-1-pmalani@chromium.org>
On Fri, Oct 23, 2020 at 02:43:26PM -0700, Prashant Malani wrote:
> Both partner and cable have identity VDOs. These are listed separately
> in the Documentation/ABI/testing/sysfs-class-typec. Factor these out
> into a common location to avoid the duplication.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
I don't have a problem with this change. FWIW:
Acked-by: Heikki Krogerus <heikki.krogeurus@linux.intel.com>
> ---
>
> Patch first introduced in v3.
>
> Documentation/ABI/testing/sysfs-class-typec | 59 ++++++---------------
> 1 file changed, 17 insertions(+), 42 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-typec b/Documentation/ABI/testing/sysfs-class-typec
> index b834671522d6..0f839fd022f1 100644
> --- a/Documentation/ABI/testing/sysfs-class-typec
> +++ b/Documentation/ABI/testing/sysfs-class-typec
> @@ -134,42 +134,6 @@ Description:
> Shows if the partner supports USB Power Delivery communication:
> Valid values: yes, no
>
> -What: /sys/class/typec/<port>-partner>/identity/
> -Date: April 2017
> -Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> -Description:
> - This directory appears only if the port device driver is capable
> - of showing the result of Discover Identity USB power delivery
> - command. That will not always be possible even when USB power
> - delivery is supported, for example when USB power delivery
> - communication for the port is mostly handled in firmware. If the
> - directory exists, it will have an attribute file for every VDO
> - in Discover Identity command result.
> -
> -What: /sys/class/typec/<port>-partner/identity/id_header
> -Date: April 2017
> -Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> -Description:
> - ID Header VDO part of Discover Identity command result. The
> - value will show 0 until Discover Identity command result becomes
> - available. The value can be polled.
> -
> -What: /sys/class/typec/<port>-partner/identity/cert_stat
> -Date: April 2017
> -Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> -Description:
> - Cert Stat VDO part of Discover Identity command result. The
> - value will show 0 until Discover Identity command result becomes
> - available. The value can be polled.
> -
> -What: /sys/class/typec/<port>-partner/identity/product
> -Date: April 2017
> -Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> -Description:
> - Product VDO part of Discover Identity command result. The value
> - will show 0 until Discover Identity command result becomes
> - available. The value can be polled.
> -
>
> USB Type-C cable devices (eg. /sys/class/typec/port0-cable/)
>
> @@ -196,17 +160,28 @@ Description:
> - type-c
> - captive
>
> -What: /sys/class/typec/<port>-cable/identity/
> +
> +USB Type-C partner/cable Power Delivery Identity objects
> +
> +NOTE: The following attributes will be applicable to both
> +partner (e.g /sys/class/typec/port0-partner/) and
> +cable (e.g /sys/class/typec/port0-cable/) devices. Consequently, the example file
> +paths below are prefixed with "/sys/class/typec/<port>-{partner|cable}/" to
> +reflect this.
> +
> +What: /sys/class/typec/<port>-{partner|cable}/identity/
> Date: April 2017
> Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Description:
> This directory appears only if the port device driver is capable
> of showing the result of Discover Identity USB power delivery
> command. That will not always be possible even when USB power
> - delivery is supported. If the directory exists, it will have an
> - attribute for every VDO returned by Discover Identity command.
> + delivery is supported, for example when USB power delivery
> + communication for the port is mostly handled in firmware. If the
> + directory exists, it will have an attribute file for every VDO
> + in Discover Identity command result.
>
> -What: /sys/class/typec/<port>-cable/identity/id_header
> +What: /sys/class/typec/<port>-{partner|cable}/identity/id_header
> Date: April 2017
> Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Description:
> @@ -214,7 +189,7 @@ Description:
> value will show 0 until Discover Identity command result becomes
> available. The value can be polled.
>
> -What: /sys/class/typec/<port>-cable/identity/cert_stat
> +What: /sys/class/typec/<port>-{partner|cable}/identity/cert_stat
> Date: April 2017
> Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Description:
> @@ -222,7 +197,7 @@ Description:
> value will show 0 until Discover Identity command result becomes
> available. The value can be polled.
>
> -What: /sys/class/typec/<port>-cable/identity/product
> +What: /sys/class/typec/<port>-{partner|cable}/identity/product
> Date: April 2017
> Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Description:
> --
> 2.29.0.rc1.297.gfa9743e501-goog
thanks,
--
heikki
next prev parent reply other threads:[~2020-11-10 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 21:43 [PATCH v3 1/2] usb: typec: Consolidate syfs ABI documentation Prashant Malani
2020-10-23 21:43 ` [PATCH v3 2/2] usb: typec: Expose Product Type VDOs via sysfs Prashant Malani
2020-11-04 17:49 ` Prashant Malani
2020-11-06 7:36 ` Heikki Krogerus
2020-11-10 11:54 ` Heikki Krogerus
2020-11-10 12:22 ` Greg KH
2020-11-11 9:21 ` Heikki Krogerus
2020-11-12 2:40 ` Prashant Malani
2020-11-12 12:43 ` Heikki Krogerus
2020-11-12 16:50 ` Prashant Malani
2020-11-13 14:34 ` Heikki Krogerus
2020-11-24 13:28 ` Heikki Krogerus
2020-11-10 10:52 ` Heikki Krogerus [this message]
2020-11-24 13:23 ` [PATCH v3 1/2] usb: typec: Consolidate syfs ABI documentation Heikki Krogerus
2020-11-24 20:13 ` Prashant Malani
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=20201110105225.GH1224435@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).