From: "Rob Herring (Arm)" <robh@kernel.org>
To: Yannic Moog <y.moog@phytec.de>
Cc: imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Benjamin Hahn <b.hahn@phytec.de>,
linux-kernel@vger.kernel.org, Teresa Remmet <t.remmet@phytec.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
upstream@lists.phytec.de,
Yashwanth Varakala <y.varakala@phytec.de>,
Shawn Guo <shawnguo@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jan Remmet <j.remmet@phytec.de>
Subject: Re: [PATCH 0/3] Add new imx imx8mp-libra-rdk-fpsc SBC
Date: Sat, 29 Mar 2025 19:27:04 -0500 [thread overview]
Message-ID: <174329418273.2439899.17086234453417036380.robh@kernel.org> (raw)
In-Reply-To: <20250328-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-v1-0-28324c7f81fa@phytec.de>
On Fri, 28 Mar 2025 14:04:36 +0100, Yannic Moog wrote:
> The Libra i.MX 8M Plus is a SBC that consists of the Libra base board
> and the phyCORE i.MX 8M Plus FPSC SoM.
> This series adds its binding and device trees.
> In addition add an overlay for an LVDS display that may optionally be
> connected to the Libra board.
>
> ---
> Yannic Moog (3):
> dt-bindings: add imx8mp-libra-rdk-fpsc
> arm64: dts: add imx8mp-libra-rdk-fpsc board
> arm64: dts: add imx8mp-libra-rdk-fpsc LVDS panel overlay
>
> Documentation/devicetree/bindings/arm/fsl.yaml | 7 +
> arch/arm64/boot/dts/freescale/Makefile | 3 +
> .../imx8mp-libra-rdk-fpsc-lvds-etml1010g3dra.dtso | 44 ++
> .../boot/dts/freescale/imx8mp-libra-rdk-fpsc.dts | 291 ++++++++
> .../boot/dts/freescale/imx8mp-phycore-fpsc.dtsi | 796 +++++++++++++++++++++
> 5 files changed, 1141 insertions(+)
> ---
> base-commit: 90453dc4dee29b96b9162895f45776bc25526e07
> change-id: 20241210-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-c273025682f2
>
> 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 90453dc4dee29b96b9162895f45776bc25526e07
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 20250328-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-v1-0-28324c7f81fa@phytec.de:
arch/arm64/boot/dts/freescale/imx8mp-libra-rdk-fpsc.dtb: clock-controller@30e20000: clocks: [[2, 284], [2, 123], [2, 124], [2, 125], [2, 127], [2, 128], [2, 182], [2, 321]] is too long
from schema $id: http://devicetree.org/schemas/clock/imx8mp-audiomix.yaml#
arch/arm64/boot/dts/freescale/imx8mp-libra-rdk-fpsc.dtb: clock-controller@30e20000: clock-names: ['ahb', 'sai1', 'sai2', 'sai3', 'sai5', 'sai6', 'sai7', 'axi'] is too long
from schema $id: http://devicetree.org/schemas/clock/imx8mp-audiomix.yaml#
prev parent reply other threads:[~2025-03-30 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 13:04 Yannic Moog
2025-03-28 13:04 ` [PATCH 1/3] dt-bindings: add imx8mp-libra-rdk-fpsc Yannic Moog
2025-03-28 13:58 ` Krzysztof Kozlowski
2025-03-31 6:03 ` Yannic Moog
2025-03-31 8:15 ` krzk
2025-03-28 13:04 ` [PATCH 2/3] arm64: dts: add imx8mp-libra-rdk-fpsc board Yannic Moog
2025-03-31 14:19 ` Frank Li
2025-04-01 5:13 ` Yannic Moog
2025-03-28 13:04 ` [PATCH 3/3] arm64: dts: add imx8mp-libra-rdk-fpsc LVDS panel overlay Yannic Moog
2025-03-30 0:27 ` Rob Herring (Arm) [this message]
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=174329418273.2439899.17086234453417036380.robh@kernel.org \
--to=robh@kernel.org \
--cc=b.hahn@phytec.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=j.remmet@phytec.de \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=t.remmet@phytec.de \
--cc=upstream@lists.phytec.de \
--cc=y.moog@phytec.de \
--cc=y.varakala@phytec.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
all inboxes | Powered by JetHome®