Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	imx@lists.linux.dev,  Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	 devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	 Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH] arm64: dts: imx8mp: Update Data Modul i.MX8M Plus eDM SBC DT to rev.903
Date: Fri, 27 Dec 2024 09:18:55 -0600	[thread overview]
Message-ID: <173531253398.3886481.9345779510218290682.robh@kernel.org> (raw)
In-Reply-To: <20241226171404.84095-1-marex@denx.de>


On Thu, 26 Dec 2024 18:13:27 +0100, Marek Vasut wrote:
> Update the DT to match newest Data Modul i.MX8M Plus eDM SBC rev.903
> board which implements significant changes. Keep some of the rev.900
> and rev.902 nodes in the DT so that a DTO can be used to support old
> rev.900 and rev.902 boards easily.
> 
> The changes from rev.900 to rev.902 are:
> - Both ethernet PHYs replaced from AR8031 to BCM54213PE
> - Both ethernet PHYs MDIO address changed
> - PCIe WiFi now comes with dedicated regulator
> - I2C TPM chip address
> - Additional GPIO expander for LVDS panel control added
> - Current EEPROM I2C address changed
> - Another optional EEPROM added onto another I2C bus
> 
> The changes from rev.902 to rev.903 are:
> - Additional GPIO expander for WiFi and LVDS panel control added
> - Multiple GPIOs are reassigned
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Fabio Estevam <festevam@gmail.com>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: imx@lists.linux.dev
> Cc: linux-arm-kernel@lists.infradead.org
> ---
>  .../freescale/imx8mp-data-modul-edm-sbc.dts   | 147 +++++++++++++++---
>  1 file changed, 128 insertions(+), 19 deletions(-)
> 


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


New warnings running 'make CHECK_DTBS=y freescale/imx8mp-data-modul-edm-sbc.dtb' for 20241226171404.84095-1-marex@denx.de:

arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dtb: tpm@2e: compatible: 'oneOf' conditional failed, one must be fixed:
	['st,st33tphf2ei2c', 'tcg,tpm-tis-i2c'] is too long
	'st,st33tphf2ei2c' is not one of ['infineon,slb9673', 'nuvoton,npct75x', 'st,st33ktpm2xi2c']
	'st,st33tphf2ei2c' is not one of ['atmel,at97sc3204t', 'infineon,slb9635tt', 'infineon,slb9645tt', 'infineon,tpm_i2c_infineon', 'nuvoton,npct501', 'nuvoton,npct601', 'st,st33zp24-i2c', 'winbond,wpct301']
	from schema $id: http://devicetree.org/schemas/tpm/tcg,tpm-tis-i2c.yaml#
arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dtb: tpm@2e: Unevaluated properties are not allowed ('compatible' was unexpected)
	from schema $id: http://devicetree.org/schemas/tpm/tcg,tpm-tis-i2c.yaml#
arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dtb: /soc@0/bus@30800000/i2c@30a20000/tpm@2e: failed to match any schema with compatible: ['st,st33tphf2ei2c', 'tcg,tpm-tis-i2c']
arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dtb: rtc@68: #clock-cells: 1 was expected
	from schema $id: http://devicetree.org/schemas/rtc/st,m41t80.yaml#
arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dtb: rtc@68: Unevaluated properties are not allowed ('#clock-cells' was unexpected)
	from schema $id: http://devicetree.org/schemas/rtc/st,m41t80.yaml#






  reply	other threads:[~2024-12-27 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 17:13 [PATCH] arm64: dts: imx8mp: Update Data Modul i.MX8M Plus eDM SBC DT to rev.903 Marek Vasut
2024-12-27 15:18 ` Rob Herring (Arm) [this message]
2025-12-26 10:24   ` Marek Vasut
2025-12-29  2:42     ` Shawn Guo
2025-12-29  2:53       ` Marek Vasut
2025-12-29  3:45         ` 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=173531253398.3886481.9345779510218290682.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --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=marex@denx.de \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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