From: abrestic@chromium.org (Andrew Bresticker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 06/12] of: Update Tegra XUSB pad controller binding for USB
Date: Mon, 17 Nov 2014 14:41:36 -0800 [thread overview]
Message-ID: <1416264102-1323-7-git-send-email-abrestic@chromium.org> (raw)
In-Reply-To: <1416264102-1323-1-git-send-email-abrestic@chromium.org>
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
---
Changes from v4:
- nvidia,usb2-port-num -> nvidia,usb2-port
- Made usb3-port a pinconfig property
- Adjusted property descriptions as suggested by Thierry.
No changes from v3.
Changes from v2:
- Added nvidia,otg-hs-curr-level-offset property.
- Dropped "-otg" from VBUS supplies.
- Added mbox-names property.
- Removed extra whitespace.
Changes from v1:
- Updated to use common mailbox bindings.
- Made USB3 port-to-lane mappins a top-level binding rather than a pinconfig
binding.
- Add #defines for the padctl lanes.
---
.../pinctrl/nvidia,tegra124-xusb-padctl.txt | 63 +++++++++++++++++++---
include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h | 7 +++
2 files changed, 64 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt
index 2f9c0bd..80895d1 100644
--- a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt
+++ b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt
@@ -21,6 +21,15 @@ Required properties:
- padctl
- #phy-cells: Should be 1. The specifier is the index of the PHY to reference.
See <dt-bindings/pinctrl/pinctrl-tegra-xusb.h> for the list of valid values.
+- mboxes: Must contain an entry for the XUSB mailbox channel.
+ See ../mailbox/mailbox.txt for details.
+- mbox-names: Must include the following entries:
+ - xusb
+
+Optional properties:
+-------------------
+- vbus-{0,1,2}-supply: VBUS regulator for the corresponding UTMI pad.
+- vddio-hsic-supply: VDDIO regulator for the HSIC pads.
Lane muxing:
------------
@@ -50,26 +59,46 @@ Optional properties:
pin or group should be assigned to. Valid values for function names are
listed below.
- nvidia,iddq: Enables IDDQ mode of the lane. (0: no, 1: yes)
+- nvidia,usb2-port: USB2 port (0, 1, or 2) to which the lane is mapped.
+- nvidia,usb3-port: USB3 port (0 or 1) to which the lane is mapped.
+- nvidia,hsic-strobe-trim: HSIC strobe trimmer value.
+- nvidia,hsic-rx-strobe-trim: HSIC RX strobe trimmer value. (0 - 7)
+- nvidia,hsic-rx-data-trim: HSIC RX data trimmer value. (0 - 7)
+- nvidia,hsic-tx-rtune-n: HSIC TX RTUNEN value. (0 - 7)
+- nvidia,hsic-tx-rtune-p: HSIC TX RTUNEP value. (0 - 7)
+- nvidia,hsic-tx-slew-n: HSIC TX SLEWN value. (0 - 7)
+- nvidia,hsic-tx-slew-p: HSIC TX SLEWP value. (0 - 7)
+- nvidia,hsic-auto-term: Enables HSIC AUTO_TERM. (0: no, 1: yes)
+- nvidia,otg-hs-curr-level-offset: Offset to be applied to the pad's fused
+ HS_CURR_LEVEL value. (0 - 63)
Note that not all of these properties are valid for all lanes. Lanes can be
-divided into three groups:
+divided into four groups:
- otg-0, otg-1, otg-2:
Valid functions for this group are: "snps", "xusb", "uart", "rsvd".
- The nvidia,iddq property does not apply to this group.
+ Only the nvidia,otg-hs-curr-level-offset property applies.
+
+ - ulpi-0:
- - ulpi-0, hsic-0, hsic-1:
+ Valid functions for this group are: "snps", "xusb".
+
+ - hsic-0, hsic-1:
Valid functions for this group are: "snps", "xusb".
- The nvidia,iddq property does not apply to this group.
+ Only the nvidia,hsic-* properties apply, and only when the function is
+ xusb.
- pcie-0, pcie-1, pcie-2, pcie-3, pcie-4, sata-0:
Valid functions for this group are: "pcie", "usb3", "sata", "rsvd".
+ Only the nvidia,iddq, nvidia,usb2-port, and nvidia,usb3-port properties
+ apply. The nvidia,usb2-port and nvidia,usb3-port properties are required
+ when the function is usb3.
Example:
========
@@ -82,6 +111,8 @@ SoC file extract:
reg = <0x0 0x7009f000 0x0 0x1000>;
resets = <&tegra_car 142>;
reset-names = "padctl";
+ mboxes = <&xusb_mbox>;
+ mbox-names = "xusb";
#phy-cells = <1>;
};
@@ -100,15 +131,35 @@ Board file extract:
...
+ usb at 0,70090000 {
+ ...
+
+ phys = <&padctl 5>, <&padctl 6>, <&padctl 7>;
+ phy-names = "utmi-1", "utmi-2", "usb3-0";
+
+ ...
+ }
+
+ ...
+
padctl: padctl at 0,7009f000 {
pinctrl-0 = <&padctl_default>;
pinctrl-names = "default";
+ vbus-2-supply = <&vdd_usb3_vbus>;
+
padctl_default: pinmux {
- usb3 {
- nvidia,lanes = "pcie-0", "pcie-1";
+ otg {
+ nvidia,lanes = "otg-1", "otg-2";
+ nvidia,function = "xusb";
+ };
+
+ usb3p0 {
+ nvidia,lanes = "pcie-0";
nvidia,function = "usb3";
nvidia,iddq = <0>;
+ nvidia,usb2-port = <2>;
+ nvidia,usb3-port = <0>;
};
pcie {
diff --git a/include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h b/include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h
index 914d56d..c83a4d4 100644
--- a/include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h
+++ b/include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h
@@ -3,5 +3,12 @@
#define TEGRA_XUSB_PADCTL_PCIE 0
#define TEGRA_XUSB_PADCTL_SATA 1
+#define TEGRA_XUSB_PADCTL_USB3_P0 2
+#define TEGRA_XUSB_PADCTL_USB3_P1 3
+#define TEGRA_XUSB_PADCTL_UTMI_P0 4
+#define TEGRA_XUSB_PADCTL_UTMI_P1 5
+#define TEGRA_XUSB_PADCTL_UTMI_P2 6
+#define TEGRA_XUSB_PADCTL_HSIC_P0 7
+#define TEGRA_XUSB_PADCTL_HSIC_P1 8
#endif /* _DT_BINDINGS_PINCTRL_TEGRA_XUSB_H */
--
2.1.0.rc2.206.gedb03e5
next prev parent reply other threads:[~2014-11-17 22:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 22:41 [PATCH V5 00/12] Tegra xHCI support Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 01/12] xhci: Set shared HCD's hcd_priv in xhci_gen_setup Andrew Bresticker
2014-11-17 23:04 ` Felipe Balbi
2014-11-17 22:41 ` [PATCH V5 02/12] mailbox: Make struct mbox_controller's ops field const Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 03/12] mailbox: Fix up error handling in mbox_request_channel() Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 04/12] of: Add NVIDIA Tegra XUSB mailbox binding Andrew Bresticker
2014-11-24 9:25 ` Jassi Brar
2014-11-17 22:41 ` [PATCH V5 05/12] mailbox: Add NVIDIA Tegra XUSB mailbox driver Andrew Bresticker
2014-11-24 8:34 ` Jassi Brar
2014-11-24 17:20 ` Andrew Bresticker
2014-11-17 22:41 ` Andrew Bresticker [this message]
2014-11-17 22:41 ` [PATCH V5 07/12] pinctrl: tegra-xusb: Add USB PHY support Andrew Bresticker
2014-11-24 9:18 ` Jassi Brar
2014-11-17 22:41 ` [PATCH V5 08/12] of: Add NVIDIA Tegra xHCI controller binding Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 09/12] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver Andrew Bresticker
2014-11-17 23:12 ` Felipe Balbi
2014-11-17 23:51 ` Andrew Bresticker
2014-11-18 0:33 ` Felipe Balbi
2014-11-18 17:12 ` Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 10/12] ARM: tegra: Add Tegra124 XUSB mailbox and xHCI controller Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 11/12] ARM: tegra: jetson-tk1: Add xHCI support Andrew Bresticker
2014-11-17 22:41 ` [PATCH V5 12/12] ARM: tegra: venice2: " Andrew Bresticker
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=1416264102-1323-7-git-send-email-abrestic@chromium.org \
--to=abrestic@chromium.org \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).