From: Yannic Moog <Y.Moog@phytec.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Yashwanth Varakala <Y.Varakala@phytec.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Will Deacon <will@kernel.org>, Teresa Remmet <T.Remmet@phytec.de>,
Benjamin Hahn <B.Hahn@phytec.de>, Jan Remmet <J.Remmet@phytec.de>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
Fabio Estevam <festevam@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"Rob Herring (Arm)" <robh@kernel.org>
Subject: Re: [PATCH v3 0/2] Add new imx imx95-libra-rdk-fpsc SBC
Date: Tue, 8 Jul 2025 07:47:29 +0000 [thread overview]
Message-ID: <eb32cbf24224e711dc09441f5aa44a2812565e09.camel@phytec.de> (raw)
In-Reply-To: <174975871561.2915543.9713933816111618183.robh@kernel.org>
Hi Shawn,
Afaik these warning were due to misalignment of bindings and devicetree patches.
They have since been resolved, at least my CHECK_DTBS run is clean again.
Is there something that is holding this series up from being picked up?
If you want me to, I can also resend.
Yannic
Am Donnerstag, dem 12.06.2025 um 15:12 -0500 schrieb Rob Herring (Arm):
>
> On Wed, 11 Jun 2025 15:05:29 +0200, Yannic Moog wrote:
> > The Libra i.MX 95 is a SBC that consists of the Libra base board
> > and the phyCORE i.MX 95 FPSC SoM.
> > This series adds its binding and device trees.
> >
> > ---
> > Changes in v3:
> > - fix more style issues
> > - remove the rs232/485 gpio hog -> switch on the board is used instead
> > - remove erroneously added build artefacts
> > - Link to v2:
> > https://lore.kernel.org/r/20250509-wip-y-moog-phytec-de-imx95-libra-v2-2-b241a915f2be@phytec.de
> >
> > Changes in v2:
> > - fix indentation error in bindings
> > - align alias naming with FPSC enumeration
> > - Link to v1:
> > https://lore.kernel.org/r/20250507-wip-y-moog-phytec-de-imx95-libra-v1-0-4b73843ad4cd@phytec.de
> >
> > ---
> > Yannic Moog (2):
> > dt-bindings: add imx95-libra-rdk-fpsc
> > arm64: dts: add imx95-libra-rdk-fpsc board
> >
> > Documentation/devicetree/bindings/arm/fsl.yaml | 7 +
> > arch/arm64/boot/dts/freescale/Makefile | 1 +
> > .../boot/dts/freescale/imx95-libra-rdk-fpsc.dts | 318 ++++++++++
> > .../boot/dts/freescale/imx95-phycore-fpsc.dtsi | 656
> > +++++++++++++++++++++
> > 4 files changed, 982 insertions(+)
> > ---
> > base-commit: 68087d05675e3ac0ed632bc7b175abf06617c584
> > change-id: 20250415-wip-y-moog-phytec-de-imx95-libra-27c9ce555b91
> >
> > Best regards,
> > --
> > Yannic Moog <y.moog@phytec.de>
> >
> >
> >
>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
> pip3 install dtschema --upgrade
>
>
> This patch series was applied (using b4) to base:
> Base: using specified base-commit 68087d05675e3ac0ed632bc7b175abf06617c584
>
> If this is not the correct base, please add 'base-commit' tag
> (or use b4 which does this automatically)
>
> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/freescale/'
> for 20250611-wip-y-moog-phytec-de-imx95-libra-v3-0-c8d09f1bdbf0@phytec.de:
>
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: usb@4c200000
> (fsl,imx95-usb): compatible: 'oneOf' conditional failed, one must be fixed:
> ['fsl,imx95-usb', 'fsl,imx7d-usb', 'fsl,imx27-usb'] is too long
> 'fsl,imx95-usb' is not one of ['fsl,imx27-usb']
> 'fsl,imx95-usb' is not one of ['fsl,imx23-usb', 'fsl,imx25-usb',
> 'fsl,imx28-usb', 'fsl,imx35-usb', 'fsl,imx50-usb', 'fsl,imx51-usb',
> 'fsl,imx53-usb', 'fsl,imx6q-usb', 'fsl,imx6sl-usb', 'fsl,imx6sx-usb',
> 'fsl,imx6ul-usb', 'fsl,imx7d-usb', 'fsl,vf610-usb']
> 'fsl,imx95-usb' is not one of ['fsl,imx8dxl-usb', 'fsl,imx8ulp-usb']
> 'fsl,imx95-usb' is not one of ['fsl,imx8mm-usb', 'fsl,imx8mn-usb',
> 'fsl,imx93-usb']
> 'fsl,imx95-usb' is not one of ['fsl,imx6sll-usb', 'fsl,imx7ulp-usb']
> 'fsl,imx27-usb' was expected
> 'fsl,imx7ulp-usb' was expected
> 'fsl,imx6ul-usb' was expected
> from schema $id:
> http://devicetree.org/schemas/usb/chipidea,usb2-imx.yaml#
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: usb@4c200000
> (fsl,imx95-usb): interrupts: [[0, 176, 4], [0, 174, 4]] is too long
> from schema $id:
> http://devicetree.org/schemas/usb/chipidea,usb2-imx.yaml#
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: /soc/usb@4c200000:
> failed to match any schema with compatible: ['fsl,imx95-usb', 'fsl,imx7d-usb',
> 'fsl,imx27-usb']
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: usbmisc@4c200200
> (fsl,imx95-usbmisc): compatible: 'oneOf' conditional failed, one must be
> fixed:
> ['fsl,imx95-usbmisc', 'fsl,imx7d-usbmisc', 'fsl,imx6q-usbmisc'] is
> too long
> 'fsl,imx95-usbmisc' is not one of ['fsl,imx25-usbmisc', 'fsl,imx27-
> usbmisc', 'fsl,imx35-usbmisc', 'fsl,imx51-usbmisc', 'fsl,imx53-usbmisc',
> 'fsl,imx6q-usbmisc', 'fsl,vf610-usbmisc']
> 'fsl,imx95-usbmisc' is not one of ['fsl,imx6ul-usbmisc', 'fsl,imx6sl-
> usbmisc', 'fsl,imx6sx-usbmisc', 'fsl,imx7d-usbmisc']
> 'fsl,imx95-usbmisc' is not one of ['fsl,imx7ulp-usbmisc',
> 'fsl,imx8mm-usbmisc', 'fsl,imx8mn-usbmisc', 'fsl,imx8ulp-usbmisc']
> 'fsl,imx6sll-usbmisc' was expected
> 'fsl,imx6q-usbmisc' was expected
> 'fsl,imx6ul-usbmisc' was expected
> from schema $id: http://devicetree.org/schemas/usb/fsl,usbmisc.yaml#
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: usbmisc@4c200200
> (fsl,imx95-usbmisc): reg: [[0, 1277166080, 0, 512], [0, 1275133972, 0, 4]] is
> too long
> from schema $id: http://devicetree.org/schemas/usb/fsl,usbmisc.yaml#
> arch/arm64/boot/dts/freescale/imx95-libra-rdk-fpsc.dtb: /soc/usbmisc@4c200200:
> failed to match any schema with compatible: ['fsl,imx95-usbmisc', 'fsl,imx7d-
> usbmisc', 'fsl,imx6q-usbmisc']
>
>
>
>
next prev parent reply other threads:[~2025-07-08 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 13:05 [PATCH v3 0/2] Add new imx imx95-libra-rdk-fpsc SBC Yannic Moog
2025-06-11 13:05 ` [PATCH v3 1/2] dt-bindings: add imx95-libra-rdk-fpsc Yannic Moog
2025-06-11 13:05 ` [PATCH v3 2/2] arm64: dts: add imx95-libra-rdk-fpsc board Yannic Moog
2025-06-11 16:41 ` Frank Li
2025-06-12 20:12 ` [PATCH v3 0/2] Add new imx imx95-libra-rdk-fpsc SBC Rob Herring (Arm)
2025-07-08 7:47 ` Yannic Moog [this message]
2025-07-11 7:30 ` Shawn Guo
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=eb32cbf24224e711dc09441f5aa44a2812565e09.camel@phytec.de \
--to=y.moog@phytec.de \
--cc=B.Hahn@phytec.de \
--cc=J.Remmet@phytec.de \
--cc=T.Remmet@phytec.de \
--cc=Y.Varakala@phytec.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
--cc=will@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