From: Rob Herring <robh@kernel.org>
To: Ray Chi <raychi@google.com>
Cc: gregkh@linuxfoundation.org, balbi@kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kyletso@google.com,
badhri@google.com
Subject: Re: [PATCH] dt-bindings: usb: dwc3: Add usb-psy-name string
Date: Tue, 30 Mar 2021 10:11:29 -0500 [thread overview]
Message-ID: <20210330151129.GA314367@robh.at.kernel.org> (raw)
In-Reply-To: <20210327191520.1824466-1-raychi@google.com>
On Sun, Mar 28, 2021 at 03:15:20AM +0800, Ray Chi wrote:
> This commit adds documentation for usb-psy-name string.
> The string will use to find the power supply interface.
> And then, DWC3 can use the interface to control charing
> current with USB state and USB speed.
Why is this DWC3 specific?
Where does it find the power supply interface?
>
> Signed-off-by: Ray Chi <raychi@google.com>
> ---
> Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> index 2247da77eac1..ad62f4552fad 100644
> --- a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
> @@ -301,6 +301,13 @@ properties:
> items:
> enum: [1, 4, 8, 16, 32, 64, 128, 256]
>
> + usb-psy-name:
> + description:
> + Contains the name for power supply interface. To follow
> + BC1.2 specification, DWC3 could use power supply interface
> + to control current with corresponding USB state and USB speed.
> + minItems: 1
> +
> unevaluatedProperties: false
>
> required:
> --
> 2.31.0.291.g576ba9dcdaf-goog
>
prev parent reply other threads:[~2021-03-30 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 19:15 [PATCH] dt-bindings: usb: dwc3: Add usb-psy-name string Ray Chi
2021-03-30 15:11 ` Rob Herring [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=20210330151129.GA314367@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=badhri@google.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=raychi@google.com \
/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).