From: Guenter Roeck <linux@roeck-us.net>
To: Kyle Tso <kyletso@google.com>
Cc: robh+dt@kernel.org, heikki.krogerus@linux.intel.com,
gregkh@linuxfoundation.org, badhri@google.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] Documentation: connector: Update the description of sink-vdos
Date: Fri, 12 Feb 2021 07:21:14 -0800 [thread overview]
Message-ID: <20210212152114.GC57042@roeck-us.net> (raw)
In-Reply-To: <20210212073743.665038-1-kyletso@google.com>
On Fri, Feb 12, 2021 at 03:37:43PM +0800, Kyle Tso wrote:
> Remove the acronym "VDM" and replace it with the full name "Vendor
> Defined Message".
>
> Signed-off-by: Kyle Tso <kyletso@google.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> .../devicetree/bindings/connector/usb-connector.yaml | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> index d385026944ec..ce11b2027199 100644
> --- a/Documentation/devicetree/bindings/connector/usb-connector.yaml
> +++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> @@ -138,9 +138,10 @@ properties:
> $ref: /schemas/types.yaml#/definitions/uint32-array
>
> sink-vdos:
> - description: An array of u32 with each entry (VDM Objects) providing additional information
> - corresponding to the product, the detailed bit definitions and the order of each VDO can be
> - found in "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
> + description: An array of u32 with each entry, a Vendor Defined Message Object (VDO),
> + providing additional information corresponding to the product, the detailed bit
> + definitions and the order of each VDO can be found in
> + "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
> chapter 6.4.4.3.1 Discover Identity. User can specify the VDO array via
> VDO_IDH/_CERT/_PRODUCT/_UFP/_DFP/_PCABLE/_ACABLE(1/2)/_VPD() defined in
> dt-bindings/usb/pd.h.
> --
> 2.30.0.478.g8a0d178c01-goog
>
prev parent reply other threads:[~2021-02-12 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 7:37 Kyle Tso
2021-02-12 15:21 ` Guenter Roeck [this message]
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=20210212152114.GC57042@roeck-us.net \
--to=linux@roeck-us.net \
--cc=badhri@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®