From: Nagarjuna Kristam <nkristam@nvidia.com>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
mark.rutland@arm.com, robh+dt@kernel.org,
linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [Patch V4 4/8] dt-bindings: usb: Add NVIDIA Tegra XUSB device mode controller binding
Date: Fri, 14 Jun 2019 11:11:48 +0530 [thread overview]
Message-ID: <faab4699-399c-4f7c-46b9-ca269ed44646@nvidia.com> (raw)
In-Reply-To: <1560238989.8487.122.camel@mhfsdcap03>
On 11-06-2019 13:13, Chunfeng Yun wrote:
> On Mon, 2019-06-10 at 15:49 +0530, Nagarjuna Kristam wrote:
>> Add device-tree binding documentation for the XUSB device mode controller
>> present on Tegra210 SoC. This controller supports the USB 3.0
>> specification.
>>
>> Signed-off-by: Nagarjuna Kristam <nkristam@nvidia.com>
>> Reviewed-by: JC Kuo <jckuo@nvidia.com>
>> ---
>> .../devicetree/bindings/usb/nvidia,tegra-xudc.txt | 108 +++++++++++++++++++++
>> 1 file changed, 108 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.txt
>>
>> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.txt b/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.txt
>> new file mode 100644
>> index 0000000..cde4e11
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.txt
>> @@ -0,0 +1,108 @@
>> +Device tree binding for NVIDIA Tegra XUSB device mode controller (XUDC)
>> +=======================================================================
>> +
>> +The Tegra XUDC controller supports both USB 2.0 HighSpeed/FullSpeed and
>> +USB 3.0 SuperSpeed protocols.
>> +
>> +Required properties:
>> +--------------------
>> +- compatible: For Tegra210, must contain "nvidia,tegra210-xudc".
>> +- reg: Must contain the base and length of the XUSB device registers, XUSB device
>> + PCI Config registers and XUSB device controller registers.
>> +- reg-names: Must include all the register names needed for the driver
> add names list?
>
Will update.
-Nagarjuna
>> +- interrupts: Must contain the XUSB device interrupt.
>> +- clocks: Must contain an entry for all clocks used.
>> + See ../clock/clock-bindings.txt for details.
>> +- clock-names: Must include the following entries:
>> + - dev: Clock to enable core XUSB dev clock.
>> + - ss: Clock to enable XUSB super speed clock.
>> + - ss_src: Clock to enable XUSB super speed dev clock.
>> + - hs_src: Clock to enable XUSB high speed dev clock.
>> + - fs_src: Clock to enable XUSB full speed dev clock.
>> +- nvidia,xusb-padctl: phandle to the XUSB pad controller that is used to
>> + configure the USB pads used by the XUDC controller.
>> +- power-domains: A list of PM domain specifiers that reference each power-domain
>> + used by the XUSB device mode controller. This list must comprise of a specifier
>> + for the XUSBA and XUSBB power-domains. See ../power/power_domain.txt and
>> + ../arm/tegra/nvidia,tegra20-pmc.txt for details.
>> +- power-domain-names: A list of names that represent each of the specifiers in
>> + the 'power-domains' property. Must include 'ss' and 'dev'.
>> +- phys: Must contain an entry for each entry in phy-names.
>> + See ../phy/phy-bindings.txt for details.
>> +- phy-names: Should include an entry for each PHY used by the controller.
>> + Names must be "usb2", and "usb3" if support SuperSpeed device mode.
>> + - "usb3" phy, SuperSpeed (SSTX+/SSTX-/SSRX+/SSRX-) data lines.
>> + - "usb2" phy, USB 2.0 (D+/D-) data lines.
>> +
>> +For Tegra210:
>> +- avddio-usb-supply: PCIe/USB3 analog logic power supply. Must supply 1.05 V.
>> +- hvdd-usb-supply: USB controller power supply. Must supply 3.3 V.
>> +
>> +
>> +Optional properties:
>> +--------------------
>> +- usb-role-switch: boolean property to indicate use of USB Role Switch driver.
>> +
>> +Sub-nodes:
>> +----------
>> +- The port would be added as subnode if use "usb-role-switch" property.
>> + see graph.txt.
>> +
>> +Example:
>> +--------
>> + pmc: pmc@7000e400 {
>> + compatible = "nvidia,tegra210-pmc";
>> + reg = <0x0 0x7000e400 0x0 0x400>;
>> + clocks = <&tegra_car TEGRA210_CLK_PCLK>, <&clk32k_in>;
>> + clock-names = "pclk", "clk32k_in";
>> +
>> + powergates {
>> + pd_xusbss: xusba {
>> + clocks = <&tegra_car TEGRA210_CLK_XUSB_SS>;
>> + resets = <&tegra_car 156>;
>> + #power-domain-cells = <0>;
>> + };
>> +
>> + pd_xusbdev: xusbb {
>> + clocks = <&tegra_car TEGRA210_CLK_XUSB_DEV>;
>> + resets = <&tegra_car 95>;
>> + #power-domain-cells = <0>;
>> + };
>> + };
>> + };
>> +
>> + xudc@700d0000 {
>> + compatible = "nvidia,tegra210-xudc";
>> + reg = <0x0 0x700d0000 0x0 0x8000>,
>> + <0x0 0x700d8000 0x0 0x1000>,
>> + <0x0 0x700d9000 0x0 0x1000>;
>> + reg-names = "base", "fpci", "ipfs";
>> +
>> + interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + clocks = <&tegra_car TEGRA210_CLK_XUSB_DEV>,
>> + <&tegra_car TEGRA210_CLK_XUSB_SS>,
>> + <&tegra_car TEGRA210_CLK_XUSB_SSP_SRC>,
>> + <&tegra_car TEGRA210_CLK_XUSB_HS_SRC>,
>> + <&tegra_car TEGRA210_CLK_XUSB_FS_SRC>;
>> + clock-names = "dev", "ss", "ss_src", "hs_src", "fs_src";
>> +
>> + power-domains = <&pd_xusbdev>, <&pd_xusbss>;
>> + power-domain-names = "dev", "ss";
>> +
>> + nvidia,xusb-padctl = <&padctl>;
>> +
>> + phys = <&{/padctl@7009f000/pads/usb2/lanes/usb2-0}>;
>> + phy-names = "usb2;
>> +
>> + avddio-usb-supply = <&vdd_pex_1v05>;
>> + hvdd-usb-supply = <&vdd_3v3_sys>;
>> +
>> + usb-role-switch;
>> + port {
>> + usb_role_switch: endpoint@0 {
>> + remote-endpoint = <&bconn_ep>;
>> + };
>> + };
>> +
>> + };
>
>
next prev parent reply other threads:[~2019-06-14 5:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 10:19 [Patch V4 0/8] Tegra XUSB gadget driver support Nagarjuna Kristam
2019-06-10 10:19 ` [Patch V4 1/8] phy: tegra: xusb: t210: add XUSB dual mode support Nagarjuna Kristam
2019-06-27 9:39 ` Thierry Reding
2019-06-10 10:19 ` [Patch V4 2/8] phy: tegra: xusb: t210: add usb3 port fake support Nagarjuna Kristam
2019-06-27 9:21 ` Thierry Reding
2019-06-10 10:19 ` [Patch V4 3/8] phy: tegra: xusb: t210: add vbus override support Nagarjuna Kristam
2019-06-10 10:19 ` [Patch V4 4/8] dt-bindings: usb: Add NVIDIA Tegra XUSB device mode controller binding Nagarjuna Kristam
2019-06-11 7:43 ` Chunfeng Yun
2019-06-14 5:41 ` Nagarjuna Kristam [this message]
2019-06-10 10:19 ` [Patch V4 5/8] arm64: tegra: Add xudc node for Tegra210 Nagarjuna Kristam
2019-06-10 10:19 ` [Patch V4 6/8] arm64: tegra: Enable xudc on Jetson TX1 Nagarjuna Kristam
2019-06-10 10:19 ` [Patch V4 7/8] usb: gadget: Add UDC driver for tegra XUSB device mode controller Nagarjuna Kristam
2019-06-10 10:19 ` [Patch V4 8/8] arm64: defconfig: Enable tegra XUDC driver Nagarjuna Kristam
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=faab4699-399c-4f7c-46b9-ca269ed44646@nvidia.com \
--to=nkristam@nvidia.com \
--cc=balbi@kernel.org \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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