From: Xu Yang <xu.yang_2@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, gregkh@linuxfoundation.org,
peter.chen@kernel.org, herve.codina@bootlin.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-usb@vger.kernel.org, jun.li@nxp.com
Subject: Re: [PATCH v8 2/3] arm64: dts: imx95: add usb3 related nodes
Date: Wed, 16 Oct 2024 18:41:40 +0800 [thread overview]
Message-ID: <20241016104140.rjmszgplmql4hwrs@hippo> (raw)
In-Reply-To: <22464382.EfDdHjke4D@steina-w>
On Wed, Oct 16, 2024 at 10:53:50AM +0200, Alexander Stein wrote:
> Hi,
>
> another thing I just noticed.
>
> Am Dienstag, 15. Oktober 2024, 13:10:17 CEST schrieb Xu Yang:
> > Add usb3 phy and controller nodes for imx95.
> >
> > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> >
> > ---
> > Changes in v2:
> > - no changes
> > Changes in v3:
> > - no changes
> > Changes in v4:
> > - reorder nodes
> > Changes in v5:
> > - no changes
> > Changes in v6:
> > - rebase to latest
> > Changes in v7:
> > - no changes
> > Changes in v8:
> > - no changes
> > ---
> > arch/arm64/boot/dts/freescale/imx95.dtsi | 43 ++++++++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > index 03661e76550f..e3faa8462759 100644
> > --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> > +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > @@ -1473,6 +1473,49 @@ smmu: iommu@490d0000 {
> > };
> > };
> >
> > + usb3: usb@4c010010 {
> > + compatible = "fsl,imx95-dwc3", "fsl,imx8mp-dwc3";
> > + reg = <0x0 0x4c010010 0x0 0x04>,
> > + <0x0 0x4c1f0000 0x0 0x20>;
> > + clocks = <&scmi_clk IMX95_CLK_HSIO>,
> > + <&scmi_clk IMX95_CLK_32K>;
> > + clock-names = "hsio", "suspend";
> > + interrupts = <GIC_SPI 173 IRQ_TYPE_LEVEL_HIGH>;
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > + ranges;
> > + power-domains = <&scmi_devpd IMX95_PD_HSIO_TOP>;
> > + dma-ranges = <0x0 0x0 0x0 0x0 0x10 0x0>;
> > + status = "disabled";
> > +
> > + usb3_dwc3: usb@4c100000 {
> > + compatible = "snps,dwc3";
> > + reg = <0x0 0x4c100000 0x0 0x10000>;
> > + clocks = <&scmi_clk IMX95_CLK_HSIO>,
> > + <&scmi_clk IMX95_CLK_24M>,
> > + <&scmi_clk IMX95_CLK_32K>;
> > + clock-names = "bus_early", "ref", "suspend";
> > + interrupts = <GIC_SPI 175 IRQ_TYPE_LEVEL_HIGH>;
> > + phys = <&usb3_phy>, <&usb3_phy>;
> > + phy-names = "usb2-phy", "usb3-phy";
> > + snps,gfladj-refclk-lpm-sel-quirk;
> > + snps,parkmode-disable-ss-quirk;
> > + iommus = <&smmu 0xe>;
> > + };
> > + };
> > +
> > + usb3_phy: phy@4c1f0040 {
> > + compatible = "fsl,imx95-usb-phy", "fsl,imx8mp-usb-phy";
> > + reg = <0x0 0x4c1f0040 0x0 0x40>,
> > + <0x0 0x4c1fc000 0x0 0x100>;
> > + clocks = <&scmi_clk IMX95_CLK_HSIO>;
> > + clock-names = "phy";
> > + #phy-cells = <0>;
> > + power-domains = <&scmi_devpd IMX95_PD_HSIO_TOP>;
> > + orientation-switch;
> > + status = "disabled";
>
> I got these dtbs check warnings:
>
> arch/arm64/boot/dts/freescale/imx95-tqma9596sa-mb-smarc-2.dtb:
> phy@4c1f0040: 'oneOf' conditional failed, one must be fixed:
> 'port' is a required property
> 'ports' is a required property
> from schema $id: http://devicetree.org/schemas/phy/fsl,imx8mq-usb-phy.yaml#
> arch/arm64/boot/dts/freescale/imx95-tqma9596sa-mb-smarc-2.dtb:
> phy@4c1f0040: Unevaluated properties are not allowed ('orientation-switch' was unexpected)
> from schema $id: http://devicetree.org/schemas/phy/fsl,imx8mq-usb-phy.yaml#
Are you checking on usb tree? You need below two dt-binding patch.
- dt-bindings: usb: dwc3-imx8mp: add compatible string for imx95
- dt-bindings: phy: imx8mq-usb: add compatible "fsl,imx95-usb-phy"
>
>
> How am I supposed to specify a port when the usb3 is used in host mode, thus
> no USB Type-C connector and no 'port' OF-graph accordingly?
Host-only mode with Type-A connector? No Typec-C connector?
Sorry, I do not get your meaning.
Thanks,
Xu Yang
next prev parent reply other threads:[~2024-10-16 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:10 [PATCH v8 1/3] phy: fsl-imx8mq-usb: add tca function driver for imx95 Xu Yang
2024-10-15 11:10 ` [PATCH v8 2/3] arm64: dts: imx95: add usb3 related nodes Xu Yang
2024-10-16 8:38 ` Alexander Stein
2024-10-16 10:30 ` Xu Yang
2024-10-16 8:53 ` Alexander Stein
2024-10-16 10:41 ` Xu Yang [this message]
2024-10-16 11:03 ` Alexander Stein
2024-10-17 10:28 ` Xu Yang
2024-10-17 11:40 ` Alexander Stein
2024-10-15 11:10 ` [PATCH v8 3/3] arm64: dts: imx95-19x19-evk: add typec nodes and enable usb3 node Xu Yang
2024-10-21 18:18 ` [PATCH v8 1/3] phy: fsl-imx8mq-usb: add tca function driver for imx95 Vinod Koul
2024-10-21 18:57 ` Frank Li
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=20241016104140.rjmszgplmql4hwrs@hippo \
--to=xu.yang_2@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.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).