From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Marek Vasut <marex@denx.de>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Yannick Fertre <yannick.fertre@foss.st.com>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@dh-electronics.com>
Subject: [PATCH 0/3] STM32 warning cleanup
Date: Wed, 17 May 2023 15:22:11 +0200 [thread overview]
Message-ID: <20230517132214.254757-1-raphael.gallais-pou@foss.st.com> (raw)
This serie aims to reduce the number of device-tree warnings of
following boards :
- STM32F429-DISCO
- STM32MP15*
Those warnings were appearing either during build or when checking
dt-bindings and concern mostly LTDC and DSI IPs and were due to the
following cases:
- panel-dsi@0 nodes that needed
- unnecessary #address-cells and #size-cells properties
- residual 'reg' field on single endpoints
Raphael Gallais-Pou (3):
ARM: dts: stm32: fix warnings on stm32f469-disco board
dt-bindings: display: st,stm32-dsi: Remove unnecessary fields
ARM: dts: stm32: fix several DT warnings on stm32mp15
.../devicetree/bindings/display/st,stm32-dsi.yaml | 2 --
arch/arm/boot/dts/stm32f469-disco.dts | 4 ++--
arch/arm/boot/dts/stm32mp151.dtsi | 5 -----
arch/arm/boot/dts/stm32mp157.dtsi | 7 -------
.../dts/stm32mp157a-icore-stm32mp1-ctouch2-of10.dts | 6 ++++--
.../boot/dts/stm32mp157a-icore-stm32mp1-edimm2.2.dts | 6 ++++--
.../stm32mp157a-microgea-stm32mp1-microdev2.0-of7.dts | 3 +--
arch/arm/boot/dts/stm32mp157c-dk2.dts | 8 ++++++++
arch/arm/boot/dts/stm32mp157c-ev1.dts | 10 +++++++---
arch/arm/boot/dts/stm32mp157c-lxa-mc1.dts | 3 +--
arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi | 6 +-----
arch/arm/boot/dts/stm32mp15xx-dkx.dtsi | 3 +--
12 files changed, 29 insertions(+), 34 deletions(-)
--
2.25.1
next reply other threads:[~2023-05-17 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:22 Raphael Gallais-Pou [this message]
2023-05-17 13:22 ` [PATCH 1/3] ARM: dts: stm32: fix warnings on stm32f469-disco board Raphael Gallais-Pou
2023-05-17 13:22 ` [PATCH 2/3] dt-bindings: display: st,stm32-dsi: Remove unnecessary fields Raphael Gallais-Pou
2023-05-17 13:22 ` [PATCH 3/3] ARM: dts: stm32: fix several DT warnings on stm32mp15 Raphael Gallais-Pou
2023-05-17 14:06 ` [PATCH 0/3] STM32 warning cleanup Marek Vasut
2023-05-17 14:38 ` Raphael Gallais-Pou
2023-05-17 15:38 ` Marek Vasut
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=20230517132214.254757-1-raphael.gallais-pou@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@foss.st.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@foss.st.com \
/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;
as well as URLs for NNTP newsgroup(s).