From: "Rob Herring (Arm)" <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: devicetree@vger.kernel.org, kernel@pengutronix.de,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
netdev@vger.kernel.org, David Jander <david@protonic.nl>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-stm32@st-md-mailman.stormreply.com,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] arm: dts: st: Add MECIO1 and MECT1S board variants
Date: Tue, 06 Aug 2024 07:43:43 -0600 [thread overview]
Message-ID: <172295171745.1220395.8839837354648720418.robh@kernel.org> (raw)
In-Reply-To: <20240806120332.405064-1-o.rempel@pengutronix.de>
On Tue, 06 Aug 2024 14:03:32 +0200, Oleksij Rempel wrote:
> From: David Jander <david@protonic.nl>
>
> Introduce device tree support for the MECIO1 and MECT1S board variants.
> MECIO1 is an I/O and motor control board used in blood sample analysis
> machines. MECT1S is a 1000Base-T1 switch for internal machine networks
> of blood sample analysis machines.
>
> Signed-off-by: David Jander <david@protonic.nl>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> .../devicetree/bindings/arm/stm32/stm32.yaml | 8 +
> arch/arm/boot/dts/st/Makefile | 3 +
> arch/arm/boot/dts/st/stm32mp151c-mecio1r0.dts | 48 ++
> arch/arm/boot/dts/st/stm32mp151c-mect1s.dts | 297 ++++++++++
> arch/arm/boot/dts/st/stm32mp153c-mecio1r1.dts | 48 ++
> .../arm/boot/dts/st/stm32mp15x-mecio1-io.dtsi | 533 ++++++++++++++++++
> 6 files changed, 937 insertions(+)
> create mode 100644 arch/arm/boot/dts/st/stm32mp151c-mecio1r0.dts
> create mode 100644 arch/arm/boot/dts/st/stm32mp151c-mect1s.dts
> create mode 100644 arch/arm/boot/dts/st/stm32mp153c-mecio1r1.dts
> create mode 100644 arch/arm/boot/dts/st/stm32mp15x-mecio1-io.dtsi
>
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 st/stm32mp151c-mecio1r0.dtb st/stm32mp151c-mect1s.dtb st/stm32mp153c-mecio1r1.dtb' for 20240806120332.405064-1-o.rempel@pengutronix.de:
arch/arm/boot/dts/st/stm32mp151c-mect1s.dtb: switch@0: Unevaluated properties are not allowed ('reset-gpios' was unexpected)
from schema $id: http://devicetree.org/schemas/net/dsa/nxp,sja1105.yaml#
prev parent reply other threads:[~2024-08-06 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 12:03 [PATCH v1] arm: dts: st: Add MECIO1 and MECT1S board variants Oleksij Rempel
2024-08-06 12:39 ` Krzysztof Kozlowski
2024-08-06 13:15 ` Oleksij Rempel
2024-08-06 13:31 ` Krzysztof Kozlowski
2024-08-06 13:43 ` 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=172295171745.1220395.8839837354648720418.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@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