From: Shawn Guo <shawnguo2@yeah.net>
To: Xu Yang <xu.yang_2@nxp.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, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/5] arm64: dts: imx8dxl-ss-conn: change usbphy1 compatible
Date: Fri, 1 Nov 2024 16:06:42 +0800 [thread overview]
Message-ID: <ZySMErIOlyRWzzrj@dragon> (raw)
In-Reply-To: <20240926073951.783869-3-xu.yang_2@nxp.com>
On Thu, Sep 26, 2024 at 03:39:48PM +0800, Xu Yang wrote:
> Make fsl,imx8dxl-usbphy compatible with fsl,imx7ulp-usbphy to fix below
> warning:
>
> /home/nxf75279/work/linux-next/arch/arm64/boot/dts/freescale/imx8dxl-evk.dtb: usbphy@5b100000: 'nxp,sim' is a required property
A relative path might be a better fit:
arch/arm64/boot/dts/freescale/imx8dxl-evk.dtb: usbphy@5b100000: 'nxp,sim' is a required property
I applied all 4 DTS patches with this fix-up.
Shawn
> from schema $id: http://devicetree.org/schemas/phy/fsl,mxs-usbphy.yaml#
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8dxl-ss-conn.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8dxl-ss-conn.dtsi b/arch/arm64/boot/dts/freescale/imx8dxl-ss-conn.dtsi
> index 1e02b04494e9..9b114bed084b 100644
> --- a/arch/arm64/boot/dts/freescale/imx8dxl-ss-conn.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8dxl-ss-conn.dtsi
> @@ -138,6 +138,10 @@ &gpmi {
> interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> +&usbphy1 {
> + compatible = "fsl,imx8dxl-usbphy", "fsl,imx7ulp-usbphy";
> +};
> +
> &usdhc1 {
> compatible = "fsl,imx8dxl-usdhc", "fsl,imx8qxp-usdhc";
> interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>;
> --
> 2.34.1
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-11-01 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 7:39 [PATCH 0/5] dtbs_check warning clean up against fsl,mxs-usbphy.yaml Xu Yang
2024-09-26 7:39 ` [PATCH 1/5] dt-bindings: phy: mxs-usb-phy: add imx8qxp compatible Xu Yang
2024-09-26 16:05 ` Conor Dooley
2024-09-26 7:39 ` [PATCH 2/5] arm64: dts: imx8dxl-ss-conn: change usbphy1 compatible Xu Yang
2024-11-01 8:06 ` Shawn Guo [this message]
2024-09-26 7:39 ` [PATCH 3/5] arm64: dts: imx8qm: " Xu Yang
2024-09-26 7:39 ` [PATCH 4/5] arm64: dts: imx8qxp: " Xu Yang
2024-09-26 7:39 ` [PATCH 5/5] ARM: dts: imx6qdl: convert fsl,tx-d-cal to correct value Xu Yang
2024-10-17 15:36 ` [PATCH 0/5] dtbs_check warning clean up against fsl,mxs-usbphy.yaml Vinod Koul
2024-10-29 15:15 ` Alexander Stein
2024-10-29 15:29 ` Frank Li
2024-10-29 15:41 ` [PATCH 0/5] dtbs_check warning clean up against fsl, mxs-usbphy.yaml Alexander Stein
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=ZySMErIOlyRWzzrj@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@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).