From: Alexandre Torgue <alexandre.torgue@st.com>
To: Erwan Le Ray <erwan.leray@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: Re: [PATCH 0/3] STM32 update uart4 pin configuration for low power
Date: Mon, 15 Jun 2020 12:12:00 +0200 [thread overview]
Message-ID: <751071df-6879-da91-3519-38770971c43f@st.com> (raw)
In-Reply-To: <20200528073853.24759-1-erwan.leray@st.com>
Hi Erwan
On 5/28/20 9:38 AM, Erwan Le Ray wrote:
> Update uart4 pin configuration for low power in pinctrl, and for ed/ev
> and dkx boards.
>
> Erwan Le Ray (3):
> ARM: dts: stm32: update uart4 pin configuration for low power on
> stm32mp157
> ARM: dts: stm32: Update pin states for uart4 on stm32mp157c-ed1
> ARM: dts: stm32: Update UART4 pin states on stm32mp15xx-dkx
>
> arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 17 +++++++++++++++++
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 4 +++-
> arch/arm/boot/dts/stm32mp15xx-dkx.dtsi | 4 +++-
> 3 files changed, 23 insertions(+), 2 deletions(-)
>
Series applied on stm32-next.
Regards
Alex
prev parent reply other threads:[~2020-06-15 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 7:38 [PATCH 0/3] STM32 update uart4 pin configuration for low power Erwan Le Ray
2020-05-28 7:38 ` [PATCH 1/3] ARM: dts: stm32: update uart4 pin configuration for low power on stm32mp157 Erwan Le Ray
2020-05-28 7:38 ` [PATCH 2/3] ARM: dts: stm32: Update pin states for uart4 on stm32mp157c-ed1 Erwan Le Ray
2020-05-28 7:38 ` [PATCH 3/3] ARM: dts: stm32: Update UART4 pin states on stm32mp15xx-dkx Erwan Le Ray
2020-06-15 10:12 ` 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=751071df-6879-da91-3519-38770971c43f@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=erwan.leray@st.com \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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