From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Valentin Caron <valentin.caron@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] arm64: dts: st: add usart nodes for stm32mp25
Date: Wed, 5 Jun 2024 09:38:08 +0200 [thread overview]
Message-ID: <53bd5ee4-dbf0-48d1-b110-248d43bbbfa4@foss.st.com> (raw)
In-Reply-To: <20240520140024.3711080-1-valentin.caron@foss.st.com>
Hi
On 5/20/24 16:00, Valentin Caron wrote:
> STM32MP25 got the same serial hardware block as STM32MP1x but with two improvements:
> - TX and RX FIFO have been extended to 64 bytes.
> - one instance more than in STM32MP1x series (4x usart and 5x uart).
>
> STM32MP257F-EV1 board has one usart used by console and one usart on IO port.
>
> Valentin Caron (3):
> arm64: dts: st: add usart nodes on stm32mp25
> arm64: dts: st: add usart6 pinctrl used on stm32mp257f-ev1 board
> arm64: dts: st: add usart6 on stm32mp257f-ev1 board
>
> arch/arm64/boot/dts/st/stm32mp25-pinctrl.dtsi | 41 +++++++++++
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 72 +++++++++++++++++++
> arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 10 +++
> 3 files changed, 123 insertions(+)
>
Series applied on stm32-next.
thanks!!
Alex
prev parent reply other threads:[~2024-06-05 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 14:00 [PATCH 0/3] arm64: dts: st: add usart nodes for stm32mp25 Valentin Caron
2024-05-20 14:00 ` [PATCH 1/3] arm64: dts: st: add usart nodes on stm32mp25 Valentin Caron
2024-05-20 14:00 ` [PATCH 2/3] arm64: dts: st: add usart6 pinctrl used on stm32mp257f-ev1 board Valentin Caron
2024-05-20 14:00 ` [PATCH 3/3] arm64: dts: st: add usart6 " Valentin Caron
2024-06-05 7:38 ` 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=53bd5ee4-dbf0-48d1-b110-248d43bbbfa4@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh@kernel.org \
--cc=valentin.caron@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).