From: "Rob Herring (Arm)" <robh@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Alexandre Torgue" <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Leonard Göhrs" <l.goehrs@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH stm32-next v3 0/2] ARM: dts: stm32: lxa-fairytux2: add gen{1,2} boards
Date: Thu, 23 Jan 2025 09:57:47 -0600 [thread overview]
Message-ID: <173764775141.3793586.6690578690442295161.robh@kernel.org> (raw)
In-Reply-To: <20250121-lxa-fairytux-v3-0-8d42d7d232fb@pengutronix.de>
On Tue, 21 Jan 2025 12:14:04 +0100, Marc Kleine-Budde wrote:
> Hello,
>
> this series adds support for the Linux Automation GmbH FairyTux2
> boards generation 1 and 2.
>
> The FairyTux2 is a small Linux device based on an Octavo Systems
> OSD32MP153c SiP, that occupies just two slots on a DIN rail.
>
> regards,
> Marc
>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> Changes in v3:
> - 2/2: fix use generic node names for external GPIO and USB Type-C controller (thanks Krzysztof)
> - 2/2: LEDs: replace label by color and function property (thanks Krzysztof)
> - 2/2: gen2: sort nodes of i2c1 by address (thanks Krzysztof)
> - Link to v2: https://patch.msgid.link/20250120-lxa-fairytux-v2-0-95f4a0eaa44d@pengutronix.de
>
> Changes in v2:
> - 1/2: Added Krzysztof's Acked-by
> - 2/2: fix alignment for gpio-line-names (thanks Krzysztof)
> - 2/2: only use color:function for LED labels (thanks Krzysztof)
> - 2/2: use generic node names for external GPIO and USB Type-C controller
> - Link to v1: https://patch.msgid.link/20241210-lxa-fairytux-v1-0-9aea01cdb83e@pengutronix.de
>
> ---
> Leonard Göhrs (2):
> dt-bindings: arm: stm32: add compatible strings for Linux Automation GmbH LXA FairyTux 2
> ARM: dts: stm32: lxa-fairytux2: add Linux Automation GmbH FairyTux 2
>
> .../devicetree/bindings/arm/stm32/stm32.yaml | 2 +
> arch/arm/boot/dts/st/Makefile | 2 +
> .../boot/dts/st/stm32mp153c-lxa-fairytux2-gen1.dts | 103 ++++++
> .../boot/dts/st/stm32mp153c-lxa-fairytux2-gen2.dts | 147 ++++++++
> .../arm/boot/dts/st/stm32mp153c-lxa-fairytux2.dtsi | 397 +++++++++++++++++++++
> 5 files changed, 651 insertions(+)
> ---
> base-commit: b7ebfb84a09de6b44492974339654d8ffc5ad9e1
> change-id: 20241210-lxa-fairytux-e730979d3d3f
>
> Best regards,
> --
> Marc Kleine-Budde <mkl@pengutronix.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
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/st/' for 20250121-lxa-fairytux-v3-0-8d42d7d232fb@pengutronix.de:
arch/arm/boot/dts/st/ste-hrefv60plus-tvk.dtb: gpio@a03fe000: compatible:0: 'stericsson,db8500-gpio' is not one of ['st,nomadik-gpio', 'mobileye,eyeq5-gpio']
from schema $id: http://devicetree.org/schemas/gpio/st,nomadik-gpio.yaml#
next prev parent reply other threads:[~2025-01-23 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 11:14 Marc Kleine-Budde
2025-01-21 11:14 ` [PATCH stm32-next v3 1/2] dt-bindings: arm: stm32: add compatible strings for Linux Automation GmbH LXA FairyTux 2 Marc Kleine-Budde
2025-01-21 11:14 ` [PATCH stm32-next v3 2/2] ARM: dts: stm32: lxa-fairytux2: add Linux Automation GmbH " Marc Kleine-Budde
2025-01-22 7:54 ` Krzysztof Kozlowski
2025-01-23 15:57 ` Rob Herring (Arm) [this message]
2025-01-23 16:05 ` [PATCH stm32-next v3 0/2] ARM: dts: stm32: lxa-fairytux2: add gen{1,2} boards Marc Kleine-Budde
2025-02-03 12:00 ` Alexandre TORGUE
2025-02-03 13:10 ` Marc Kleine-Budde
2025-02-03 12:02 ` Alexandre TORGUE
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=173764775141.3793586.6690578690442295161.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=l.goehrs@pengutronix.de \
--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=mkl@pengutronix.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®