From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Yann Gautier <yann.gautier@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 00/10] ARM: dts: stm32: update sdmmc nodes
Date: Mon, 7 Feb 2022 11:39:14 +0100 [thread overview]
Message-ID: <b35ab20d-479f-a5ae-0e43-2b3c03f087e1@foss.st.com> (raw)
In-Reply-To: <20220112163226.25384-1-yann.gautier@foss.st.com>
Hi Yann
On 1/12/22 17:32, Yann Gautier wrote:
> This patches series brings updates for SDMMC nodes on STM32MP13
> (max frequency, pins slew-rates, sleep pins, and controller version).
> The sdmmc2 node is also added as STM32MP13 embeds 2 SDMMC controllers.
>
> The compatible for sdmmc nodes is also updated for both STM32MP13
> and STM32MP15, to align with bootloaders DT, and after arm,pl18x.yaml
> has been updated [1].
>
> [1] commit 552bc46484b3 ("dt-bindings: mmc: mmci: Add st,stm32-sdmmc2
> compatible")
>
> Gerald Baeza (1):
> ARM: dts: stm32: update sdmmc slew-rate in stm32mp13 pinctrl
>
> Yann Gautier (9):
> ARM: dts: stm32: add st,stm32-sdmmc2 compatible on stm32mp151
> ARM: dts: stm32: add st,stm32-sdmmc2 compatible on stm32mp131
> ARM: dts: stm32: increase SDMMC max-frequency for STM32MP13
> ARM: dts: stm32: update SDMMC clock slew-rate on STM32MP135F-DK board
> ARM: dts: stm32: add sdmmc sleep pins for STM32MP13
> ARM: dts: stm32: add sdmmc sleep config for STM32MP135F-DK
> ARM: dts: stm32: update SDMMC version for STM32MP13
> ARM: dts: stm32: add SDMMC2 in STM32MP13 DT
> ARM: dts: stm32: add sdmmc2 pins for STM32MP13
>
> arch/arm/boot/dts/stm32mp13-pinctrl.dtsi | 81 ++++++++++++++++++++----
> arch/arm/boot/dts/stm32mp131.dtsi | 20 +++++-
> arch/arm/boot/dts/stm32mp135f-dk.dts | 7 +-
> arch/arm/boot/dts/stm32mp151.dtsi | 6 +-
> 4 files changed, 94 insertions(+), 20 deletions(-)
>
Series applied on stm32-next.
Thanks
alex
prev parent reply other threads:[~2022-02-07 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:32 [PATCH 00/10] ARM: dts: stm32: update sdmmc nodes Yann Gautier
2022-01-12 16:32 ` [PATCH 01/10] ARM: dts: stm32: add st,stm32-sdmmc2 compatible on stm32mp151 Yann Gautier
2022-01-12 16:32 ` [PATCH 02/10] ARM: dts: stm32: add st,stm32-sdmmc2 compatible on stm32mp131 Yann Gautier
2022-01-12 16:32 ` [PATCH 03/10] ARM: dts: stm32: increase SDMMC max-frequency for STM32MP13 Yann Gautier
2022-01-12 16:32 ` [PATCH 04/10] ARM: dts: stm32: update sdmmc slew-rate in stm32mp13 pinctrl Yann Gautier
2022-01-12 16:32 ` [PATCH 05/10] ARM: dts: stm32: update SDMMC clock slew-rate on STM32MP135F-DK board Yann Gautier
2022-01-12 16:32 ` [PATCH 06/10] ARM: dts: stm32: add sdmmc sleep pins for STM32MP13 Yann Gautier
2022-01-12 16:32 ` [PATCH 07/10] ARM: dts: stm32: add sdmmc sleep config for STM32MP135F-DK Yann Gautier
2022-02-07 10:39 ` Alexandre TORGUE [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=b35ab20d-479f-a5ae-0e43-2b3c03f087e1@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yann.gautier@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).