Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Yannic Moog <y.moog@phytec.de>
Cc: Conor Dooley <conor+dt@kernel.org>,
	 Yashwanth Varakala <y.varakala@phytec.de>,
	 linux-arm-kernel@lists.infradead.org,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	 Fabio Estevam <festevam@gmail.com>,
	Jan Remmet <j.remmet@phytec.de>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	upstream@lists.phytec.de,  Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org,  Shawn Guo <shawnguo@kernel.org>,
	linux-kernel@vger.kernel.org,  Benjamin Hahn <b.hahn@phytec.de>,
	imx@lists.linux.dev,
	 Pengutronix Kernel Team <kernel@pengutronix.de>,
	 Teresa Remmet <t.remmet@phytec.de>
Subject: Re: [PATCH v2 0/3] Add new imx imx8mp-libra-rdk-fpsc SBC
Date: Thu, 03 Apr 2025 09:35:35 -0500	[thread overview]
Message-ID: <174369066563.2789714.13229546252082031365.robh@kernel.org> (raw)
In-Reply-To: <20250403-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-v2-0-c0d2eff683ac@phytec.de>


On Thu, 03 Apr 2025 13:29:26 +0200, 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.
> 
> ---
> Changes in v2:
> - reorder device tree nodes of SoM and board device trees according to https://github.com/lznuaa/dt-format
> - fix typo in reg: regulator-12v0 -> regulator-vdd-12v0
> - add to binding commit description the difference between phycore-som and phycore-fpsc
> - Link to v1: https://lore.kernel.org/r/20250328-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-v1-0-28324c7f81fa@phytec.de
> 
> ---
> 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   | 290 ++++++++
>  .../boot/dts/freescale/imx8mp-phycore-fpsc.dtsi    | 796 +++++++++++++++++++++
>  5 files changed, 1140 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 20250403-wip-y-moog-phytec-de-imx8mp-phycore-fpsc-v2-0-c0d2eff683ac@phytec.de:

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#
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#







      parent reply	other threads:[~2025-04-03 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 11:29 [PATCH v2 0/3] Add new imx imx8mp-libra-rdk-fpsc SBC Yannic Moog
2025-04-03 11:29 ` [PATCH v2 1/3] dt-bindings: add imx8mp-libra-rdk-fpsc Yannic Moog
2025-04-03 11:29 ` [PATCH v2 2/3] arm64: dts: add imx8mp-libra-rdk-fpsc board Yannic Moog
2025-04-03 18:56   ` Frank Li
2025-04-15  8:20     ` Yannic Moog
2025-04-15 16:54       ` Frank Li
2025-04-16  7:22         ` Yannic Moog
2025-04-03 11:29 ` [PATCH v2 3/3] arm64: dts: add imx8mp-libra-rdk-fpsc LVDS panel overlay Yannic Moog
2025-04-03 18:31   ` Frank Li
2025-04-15  8:52     ` Yannic Moog
2025-04-03 14:35 ` 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=174369066563.2789714.13229546252082031365.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=krzysztof.kozlowski@linaro.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