From: Shawn Guo <shawnguo@kernel.org>
To: Li Jun <jun.li@nxp.com>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org, robh+dt@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peter.chen@nxp.com
Subject: Re: [PATCH 5/6] arm64: dts: imx8mp-evk: enable usb1 as host mode
Date: Tue, 23 Jun 2020 19:14:24 +0800 [thread overview]
Message-ID: <20200623111423.GZ30139@dragon> (raw)
In-Reply-To: <1591701165-12872-6-git-send-email-jun.li@nxp.com>
On Tue, Jun 09, 2020 at 07:12:44PM +0800, Li Jun wrote:
> Enable usb host port with type-A connector on imx8mp-evk board.
>
> Signed-off-by: Li Jun <jun.li@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 32 ++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> index 3da1fff..fbe056c 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> @@ -43,6 +43,19 @@
> gpio = <&gpio2 19 GPIO_ACTIVE_HIGH>;
> enable-active-high;
> };
> +
> + reg_usb1_host_vbus: regulator-usb1-vbus {
> + compatible = "regulator-fixed";
> + regulator-name = "usb1_host_vbus";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_usb1_vbus>;
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + gpio = <&gpio1 14 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-always-on;
Instead of having it regulator-always-on, it should be controlled by usb
device, right?
Shawn
> + };
> +
> };
>
> &fec {
> @@ -91,6 +104,19 @@
> status = "okay";
> };
>
> +&usb3_phy1 {
> + status = "okay";
> +};
> +
> +&usb3_1 {
> + status = "okay";
> +};
> +
> +&usb_dwc3_1 {
> + dr_mode = "host";
> + status = "okay";
> +};
> +
> &usdhc2 {
> assigned-clocks = <&clk IMX8MP_CLK_USDHC2>;
> assigned-clock-rates = <400000000>;
> @@ -172,6 +198,12 @@
> >;
> };
>
> + pinctrl_usb1_vbus: usb1grp {
> + fsl,pins = <
> + MX8MP_IOMUXC_GPIO1_IO14__GPIO1_IO14 0x19
> + >;
> + };
> +
> pinctrl_usdhc2: usdhc2grp {
> fsl,pins = <
> MX8MP_IOMUXC_SD2_CLK__USDHC2_CLK 0x190
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-06-23 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 11:12 [PATCH 0/6] add NXP imx8mp usb support Li Jun
2020-06-09 11:12 ` [PATCH 1/6] dt-bindings: usb: dwc3: add property to disable xhci 64bit support Li Jun
2020-06-10 2:47 ` Peter Chen
2020-06-10 4:22 ` Florian Fainelli
2020-07-06 9:56 ` Jun Li
2020-06-09 11:12 ` [PATCH 2/6] usb: host: xhci-plat: add quirk for XHCI_NO_64BIT_SUPPORT Li Jun
2020-06-09 11:12 ` [PATCH 3/6] usb: dwc3: add imx8mp dwc3 glue layer driver Li Jun
2020-06-10 2:59 ` Peter Chen
2020-06-09 11:12 ` [PATCH 4/6] arm64: dtsi: imx8mp: add usb nodes Li Jun
2020-06-09 11:12 ` [PATCH 5/6] arm64: dts: imx8mp-evk: enable usb1 as host mode Li Jun
2020-06-23 11:14 ` Shawn Guo [this message]
2020-06-23 12:37 ` Jun Li
2020-06-09 11:12 ` [PATCH 6/6] dt-bindings: usb: dwc3-imx8mp: add imx8mp dwc3 glue bindings Li Jun
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=20200623111423.GZ30139@dragon \
--to=shawnguo@kernel.org \
--cc=balbi@kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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