From: Alain Volmat <avolmat@me.com>
To: Patrice Chotard <patrice.chotard@foss.st.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, avolmat@me.com
Subject: [PATCH v2 0/7] ARM: dts: sti: various DT fixes to avoid warnings
Date: Fri, 11 Feb 2022 19:16:07 +0100 [thread overview]
Message-ID: <20220211181614.683497-1-avolmat@me.com> (raw)
A first serie to correct a large amount of DT warnings seen when
building with the W=1 option and mainly due to having several time
the same reg property (clock) or having unnecessary reg value.
The first 3 patches related to clocks require that recent serie [1] of
clock drivers improvements be first merged.
[1] https://lore.kernel.org/linux-clk/20211202072850.194314-1-avolmat@me.com/T/#t
v2: squash together several patches from the previous serie in order to
avoid compilation issues
Alain Volmat (7):
ARM: dts: sti: ensure unique unit-address in stih407-clock
ARM: dts: sti: ensure unique unit-address in stih410-clock
ARM: dts: sti: ensure unique unit-address in stih418-clock
ARM: dts: sti: move some nodes out of the soc section in
stih407-family.dtsi
ARM: dts: sti: remove delta node from stih410.dtsi
ARM: dts: sti: move usb picophy nodes out of soc in stih410.dtsi
ARM: dts: sti: move usb picophy nodes out of soc in stih418.dtsi
arch/arm/boot/dts/stih407-clock.dtsi | 101 +++++-----
arch/arm/boot/dts/stih407-family.dtsi | 262 +++++++++++++-------------
arch/arm/boot/dts/stih410-b2120.dts | 16 +-
arch/arm/boot/dts/stih410-b2260.dts | 30 +--
arch/arm/boot/dts/stih410-clock.dtsi | 100 +++++-----
arch/arm/boot/dts/stih410.dtsi | 52 ++---
arch/arm/boot/dts/stih418-b2199.dts | 22 +--
arch/arm/boot/dts/stih418-clock.dtsi | 101 +++++-----
arch/arm/boot/dts/stih418.dtsi | 38 ++--
arch/arm/boot/dts/stihxxx-b2120.dtsi | 22 +--
10 files changed, 351 insertions(+), 393 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-11 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 18:16 Alain Volmat [this message]
2022-02-11 18:16 ` [PATCH v2 1/7] ARM: dts: sti: ensure unique unit-address in stih407-clock Alain Volmat
2022-02-15 16:49 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 2/7] ARM: dts: sti: ensure unique unit-address in stih410-clock Alain Volmat
2022-02-15 16:50 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 3/7] ARM: dts: sti: ensure unique unit-address in stih418-clock Alain Volmat
2022-02-15 16:50 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 4/7] ARM: dts: sti: move some nodes out of the soc section in stih407-family.dtsi Alain Volmat
2022-02-15 16:50 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 5/7] ARM: dts: sti: remove delta node from stih410.dtsi Alain Volmat
2022-02-15 16:50 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 6/7] ARM: dts: sti: move usb picophy nodes out of soc in stih410.dtsi Alain Volmat
2022-02-15 16:51 ` Patrice CHOTARD
2022-02-11 18:16 ` [PATCH v2 7/7] ARM: dts: sti: move usb picophy nodes out of soc in stih418.dtsi Alain Volmat
2022-02-15 16:52 ` Patrice CHOTARD
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=20220211181614.683497-1-avolmat@me.com \
--to=avolmat@me.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@foss.st.com \
--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
all inboxes | Powered by JetHome®