From: Rob Herring <robh@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: phy: Add qcom,usb-hsic-phy bindings
Date: Mon, 20 Jun 2016 11:26:22 -0500 [thread overview]
Message-ID: <20160620162622.GA21783@rob-hp-laptop> (raw)
In-Reply-To: <1466159119-20310-3-git-send-email-narmstrong@baylibre.com>
On Fri, Jun 17, 2016 at 12:25:19PM +0200, Neil Armstrong wrote:
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> .../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 95 ++++++++++++++++++++++
> 1 file changed, 95 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
> new file mode 100644
> index 0000000..79259a4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
> @@ -0,0 +1,95 @@
> +Qualcomm's MDM9615 USB HISC transceiver controller
> +
> +- compatible:
> + Usage: required
> + Value type: <string>
> + Definition: Should contain "qcom,usb-hsic-phy".
SoC specific compatible string please.
> +
> +- reg:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: USB PHY base address and length of the register map
> +
> +- clocks:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: See clock-bindings.txt section "consumers". List of
> + 5 clock specifiers for interface and core controller
> + clocks.
> +
> +- clock-names:
> + Usage: required
> + Value type: <string>
> + Definition: Must contain "core", "alt-core", "phy", "cal" and "iface" strings.
> +
> +- vddcx-supply:
> + Usage: required
> + Value type: <phandle>
> + Definition: phandle to the regulator VDCCX supply node.
> +
> +- resets:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: See reset.txt section "consumers". PHY reset specifier.
> +
> +- reset-names:
> + Usage: required
> + Value type: <string>
> + Definition: Must contain "link" string.
> +
> +- interrupts:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: Interrupt line definition for the PHY
> +
> +- dr_mode:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: Setup the PHY mode, either "host", "gadget" or "dual"
> +
> +- qcom,vdd-levels:
> + Usage: required for MDM9615
> + Value type: <prop-encoded-array>
> + Definition: Setup the valid vdd levers for the vddx-supply
s/levers/levels/
There's not a common regulator property for this?
> +
> +- phy_type:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: Shall be "hisc"
typo
> +
> +- qcom,tlmm:
> + Usage: required for MDM961
s/MDM961/MDM9615/
or drop because this binding is only for MDM9615.
> + Value type: <prop-encoded-array>
> + Definition: TLMM syscon phandle to setup the HSIC lines
> +
> +- qcom,tlmm-cfg:
> + Usage: required for MDM961
s/MDM961/MDM9615/
> + Value type: <prop-encoded-array>
> + Definition: Shall be two entries of offset, data of the HSIC lines setup
This property is somewhat questionable with just magic register address
and value to write...
next prev parent reply other threads:[~2016-06-20 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 10:25 [PATCH 0/2] usb: phy: Add support for the Qualcomm HSIC USB PHY Neil Armstrong
2016-06-17 10:25 ` [PATCH 1/2] usb: phy: Add initial support for Qualcomm HSIC PHY Neil Armstrong
2016-06-18 4:58 ` kbuild test robot
2016-06-17 10:25 ` [PATCH 2/2] dt-bindings: phy: Add qcom,usb-hsic-phy bindings Neil Armstrong
2016-06-20 16:26 ` Rob Herring [this message]
2016-06-17 16:39 ` [PATCH 0/2] usb: phy: Add support for the Qualcomm HSIC USB PHY Stephen Boyd
2016-06-20 9:21 ` Neil Armstrong
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=20160620162622.GA21783@rob-hp-laptop \
--to=robh@kernel.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=narmstrong@baylibre.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
all inboxes | Powered by JetHome®