From: robh@kernel.org (Rob Herring)
To: linus-amlogic@lists.infradead.org
Subject: [RFC usb-next v8 1/3] dt-bindings: usb: add the documentation for USB HCDs
Date: Tue, 30 Jan 2018 11:12:49 -0600 [thread overview]
Message-ID: <20180130171249.d2svzedtnxc4pxyp@rob-hp-laptop> (raw)
In-Reply-To: <20180125000053.9387-2-martin.blumenstingl@googlemail.com>
On Thu, Jan 25, 2018 at 01:00:51AM +0100, Martin Blumenstingl wrote:
> A USB HCD may have several PHYs which need to be configured before the
> the HCD starts working.
> This adds the documentation for such a USB HCD as well as a reference to
> the new "usb-hcd.txt" from all bindings that implement a USB HCD which
> support one USB PHY per port.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt | 5 ++++-
> Documentation/devicetree/bindings/usb/mediatek,mtu3.txt | 5 ++++-
> Documentation/devicetree/bindings/usb/usb-ehci.txt | 6 ++++--
> Documentation/devicetree/bindings/usb/usb-hcd.txt | 9 +++++++++
> Documentation/devicetree/bindings/usb/usb-ohci.txt | 6 ++++--
> Documentation/devicetree/bindings/usb/usb-uhci.txt | 3 +++
> Documentation/devicetree/bindings/usb/usb-xhci.txt | 5 +++++
> 7 files changed, 33 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/usb/usb-hcd.txt
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-01-30 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 0:00 [RFC usb-next v8 0/3] initialize (multiple) PHYs for a HCD Martin Blumenstingl
2018-01-25 0:00 ` [RFC usb-next v8 1/3] dt-bindings: usb: add the documentation for USB HCDs Martin Blumenstingl
2018-01-30 17:12 ` Rob Herring [this message]
2018-01-25 0:00 ` [RFC usb-next v8 2/3] usb: core: add a wrapper for the USB PHYs on the HCD Martin Blumenstingl
2018-01-25 0:00 ` [RFC usb-next v8 3/3] usb: core: hcd: integrate the PHY wrapper into the HCD core Martin Blumenstingl
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=20180130171249.d2svzedtnxc4pxyp@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linus-amlogic@lists.infradead.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®