From: Amelie Delaunay <amelie.delaunay@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Amelie Delaunay <amelie.delaunay@foss.st.com>
Subject: [PATCH 0/2] ARM: dts: stm32: fix misalignments in nodes of STM32MP1x
Date: Wed, 4 Mar 2026 09:06:58 +0100 [thread overview]
Message-ID: <20260304-mp1x_alignment_issues-v1-0-19a8013782a5@foss.st.com> (raw)
Since the ETZPC system bus was introduced on STM32MP13 and STM32MP15,
misalignments have appeared in some nodes moved under the etzpc
parent node in stm32mp151.dtsi and stm32mp131.dtsi.
Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
---
Amelie Delaunay (2):
ARM: dts: stm32: fix misalignments in nodes of stm32mp151
ARM: dts: stm32: fix misalignments in nodes of stm32mp131
arch/arm/boot/dts/st/stm32mp131.dtsi | 14 +++++++-------
arch/arm/boot/dts/st/stm32mp151.dtsi | 14 +++++++-------
2 files changed, 14 insertions(+), 14 deletions(-)
---
base-commit: 291f393298f72091490dfa70ab4a0ebdbb4c7d7e
change-id: 20260303-mp1x_alignment_issues-62a3fdc37d03
Best regards,
--
Amelie Delaunay <amelie.delaunay@foss.st.com>
next reply other threads:[~2026-03-04 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:06 Amelie Delaunay [this message]
2026-03-04 8:06 ` [PATCH 1/2] ARM: dts: stm32: fix misalignments in nodes of stm32mp151 Amelie Delaunay
2026-03-04 8:07 ` [PATCH 2/2] ARM: dts: stm32: fix misalignments in nodes of stm32mp131 Amelie Delaunay
2026-03-12 12:31 ` [PATCH 0/2] ARM: dts: stm32: fix misalignments in nodes of STM32MP1x 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=20260304-mp1x_alignment_issues-v1-0-19a8013782a5@foss.st.com \
--to=amelie.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robh@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®