From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org
Cc: linux-imx@nxp.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Xu Yang <xu.yang_2@nxp.com>
Subject: Re: [PATCH 3/4] arm64: dts: imx93: add usb nodes
Date: Thu, 14 Dec 2023 14:35:57 +0100 [thread overview]
Message-ID: <8309719.T7Z3S40VBb@steina-w> (raw)
In-Reply-To: <20231214112442.2412079-3-xu.yang_2@nxp.com>
Hi,
thanks for the patch.
Am Donnerstag, 14. Dezember 2023, 12:24:41 CET schrieb Xu Yang:
> There are 2 USB controllers on i.MX93. Add them.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx93.dtsi | 58 ++++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx93.dtsi
> b/arch/arm64/boot/dts/freescale/imx93.dtsi index 34c0540276d1..bcf4861cfede
> 100644
> --- a/arch/arm64/boot/dts/freescale/imx93.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx93.dtsi
> @@ -171,6 +171,20 @@ cm33: remoteproc-cm33 {
> status = "disabled";
> };
>
> + usbphynop1: usbphynop1 {
> + #phy-cells = <0>;
> + compatible = "usb-nop-xceiv";
compatible first.
> + clocks = <&clk IMX93_CLK_USB_PHY_BURUNIN>;
> + clock-names = "main_clk";
> + };
> +
> + usbphynop2: usbphynop2 {
> + #phy-cells = <0>;
> + compatible = "usb-nop-xceiv";
compatible first.
> + clocks = <&clk IMX93_CLK_USB_PHY_BURUNIN>;
> + clock-names = "main_clk";
> + };
> +
> soc@0 {
> compatible = "simple-bus";
> #address-cells = <1>;
> @@ -1059,5 +1073,49 @@ ddr-pmu@4e300dc0 {
> reg = <0x4e300dc0 0x200>;
> interrupts = <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>;
> };
> +
> + usbotg1: usb@4c100000 {
> + compatible = "fsl,imx8mm-usb", "fsl,imx7d-usb",
"fsl,imx27-usb";
> + reg = <0x4c100000 0x200>;
> + interrupts = <GIC_SPI 187 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clk IMX93_CLK_USB_CONTROLLER_GATE>,
> + <&clk IMX93_CLK_HSIO_32K_GATE>;
> + clock-names = "usb_ctrl_root_clk",
"usb_wakeup_clk";
drivers/usb/chipidea/ci_hdrc_imx.c uses 3 clocks: "ipg", "ahb" and "per", see
imx_get_clks(). How is this supposed to work?
> + assigned-clocks = <&clk IMX93_CLK_HSIO>;
> + assigned-clock-parents = <&clk
IMX93_CLK_SYS_PLL_PFD1_DIV2>;
> + assigned-clock-rates = <133000000>;
> + fsl,usbphy = <&usbphynop1>;
> + fsl,usbmisc = <&usbmisc1 0>;
> + status = "disabled";
> + };
> +
> + usbmisc1: usbmisc@4c100200 {
> + compatible = "fsl,imx8mm-usbmisc", "fsl,imx7d-
usbmisc",
> + "fsl,imx6q-usbmisc";
This means you are compatible to fsl,imx7d-usbmisc. Which means you use
register MX7D_USB_OTG_PHY_STATUS in USB misc (USBNC). But i.MX93 RM Rev. 2
(04/2023) lacks this and other registers.
> + #index-cells = <1>;
> + reg = <0x4c100200 0x200>;
reg after compatible.
> + };
> +
> + usbotg2: usb@4c200000 {
> + compatible = "fsl,imx8mm-usb", "fsl,imx7d-usb",
"fsl,imx27-usb";
> + reg = <0x4c200000 0x200>;
> + interrupts = <GIC_SPI 188 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clk IMX93_CLK_USB_CONTROLLER_GATE>,
> + <&clk IMX93_CLK_HSIO_32K_GATE>;
> + clock-names = "usb_ctrl_root_clk",
"usb_wakeup_clk";
The same as for usbotg1 applies here.
> + assigned-clocks = <&clk IMX93_CLK_HSIO>;
> + assigned-clock-parents = <&clk
IMX93_CLK_SYS_PLL_PFD1_DIV2>;
> + assigned-clock-rates = <133000000>;
> + fsl,usbphy = <&usbphynop2>;
> + fsl,usbmisc = <&usbmisc2 0>;
> + status = "disabled";
> + };
> +
> + usbmisc2: usbmisc@4c200200 {
> + compatible = "fsl,imx8mm-usbmisc", "fsl,imx7d-
usbmisc",
> + "fsl,imx6q-usbmisc";
> + #index-cells = <1>;
> + reg = <0x4c200200 0x200>;
The same as for usbmisc1 applies here.
> + };
> };
> };
Best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-12-14 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:24 [PATCH 1/4] arm64: dts: imx8ulp: add usb nodes Xu Yang
2023-12-14 11:24 ` [PATCH 2/4] arm64: dts: imx8ulp-evk: enable " Xu Yang
2023-12-14 11:30 ` Fabio Estevam
2023-12-14 12:44 ` [EXT] " Xu Yang
2023-12-14 11:58 ` Fabio Estevam
2023-12-14 12:50 ` [EXT] " Xu Yang
2023-12-14 13:15 ` Fabio Estevam
2023-12-15 1:56 ` Xu Yang
2023-12-18 11:56 ` 回复: " Jun Li
2023-12-14 11:24 ` [PATCH 3/4] arm64: dts: imx93: add " Xu Yang
2023-12-14 13:35 ` Alexander Stein [this message]
2023-12-15 2:12 ` [EXT] " Xu Yang
2023-12-15 6:32 ` Alexander Stein
2023-12-18 2:16 ` Xu Yang
2023-12-14 11:24 ` [PATCH 4/4] arm64: dts: imx93-11x11-evk: enable usb and typec nodes Xu Yang
2023-12-14 11:25 ` Fabio Estevam
2023-12-14 12:34 ` [EXT] " Xu Yang
2023-12-14 13:40 ` Alexander Stein
2023-12-15 2:21 ` [EXT] " Xu Yang
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=8309719.T7Z3S40VBb@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xu.yang_2@nxp.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;
as well as URLs for NNTP newsgroup(s).