From: Oleksij Rempel <o.rempel@pengutronix.de>
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: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v1 0/7] ARM: dts: stm32: Fix mecio1 hardware revisions and ADC/GPIO mappings
Date: Thu, 7 May 2026 07:14:13 +0200 [thread overview]
Message-ID: <afwfpST_NNAWSo1l@pengutronix.de> (raw)
In-Reply-To: <20260318105123.819807-1-o.rempel@pengutronix.de>
Hi Alexandre,
Can you please take a look at this patch stack :)
Best Regards,
Oleksij
On Wed, Mar 18, 2026 at 11:51:16AM +0100, Oleksij Rempel wrote:
> This series updates the STM32MP15x MECIO1 device trees to properly
> account for the physical hardware changes between the R0 and R1 board
> revisions.
>
> David Jander (7):
> ARM: dts: stm32: stm32mp15x-mecio1-io: Enable internal ADC reference
> ARM: dts: stm32: stm32mp15x-mecio1-io: Fix ADC sampling times
> ARM: dts: stm32: stm32mp15x-mecio1-io: Move divergent mecio1 ADC
> channels to board files
> ARM: dts: stm32: stm32mp15x-mecio1-io: Fix GPIO names typo
> ARM: dts: stm32: stm32mp15x-mecio1-io: Move gpio-line-names to board
> files
> ARM: dts: stm32: stm32mp15x-mecio1-io: Fix expander gpio line typo
> ARM: dts: stm32: stm32mp15x-mecio1-io: Move expander gpio-line-names
> to board files
>
> arch/arm/boot/dts/st/stm32mp151c-mecio1r0.dts | 128 +++++++++++++++
> arch/arm/boot/dts/st/stm32mp153c-mecio1r1.dts | 144 +++++++++++++++++
> .../arm/boot/dts/st/stm32mp15x-mecio1-io.dtsi | 146 ++----------------
> 3 files changed, 288 insertions(+), 130 deletions(-)
>
> --
> 2.47.3
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2026-05-07 5:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:51 [PATCH v1 0/7] ARM: dts: stm32: Fix mecio1 hardware revisions and ADC/GPIO mappings Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 1/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Enable internal ADC reference Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 2/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Fix ADC sampling times Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 3/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Move divergent mecio1 ADC channels to board files Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 4/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Fix GPIO names typo Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 5/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Move gpio-line-names to board files Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 6/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Fix expander gpio line typo Oleksij Rempel
2026-03-18 10:51 ` [PATCH v1 7/7] ARM: dts: stm32: stm32mp15x-mecio1-io: Move expander gpio-line-names to board files Oleksij Rempel
2026-05-07 5:14 ` Oleksij Rempel [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=afwfpST_NNAWSo1l@pengutronix.de \
--to=o.rempel@pengutronix.de \
--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=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--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