devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Valentin Caron <valentin.caron@foss.st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+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>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] ARM: dts: stm32: stm32mp15 various fixes and add stm32mp13 usart nodes
Date: Tue, 28 Mar 2023 17:58:09 +0200	[thread overview]
Message-ID: <38c0e334-7b88-d139-37f7-ad3e99b0bb16@foss.st.com> (raw)
In-Reply-To: <20230328153723.498672-1-valentin.caron@foss.st.com>

On 3/28/23 17:37, Valentin Caron wrote:
> On stm32mp15 device trees:
>    - Fix pins of USART2 of stm32mp15 dk* boards
>    - Remove duplicates serial aliases
> 
> On stm32mp13 device trees:
>    - Add USART nodes in stm32mp131.dtsi
>    - Add USART nodes in stm32mp135f-dk.dts
>    
> Changes in v2:
>    - Drop patch about SCMI clock of USART1.
> 
> Valentin Caron (6):
>    ARM: dts: stm32: fix slew-rate of USART2 on stm32mp15xx-dkx
>    ARM: dts: stm32: clean uart aliases on stm32mp15xx-dkx boards
>    ARM: dts: stm32: clean uart aliases on stm32mp15xx-exx boards
>    ARM: dts: stm32: add uart nodes on stm32mp13
>    ARM: dts: stm32: add pins for usart2/1/4/8 in stm32mp13-pinctrl
>    ARM: dts: stm32: add uart nodes and uart aliases on stm32mp135f-dk
> 
>   arch/arm/boot/dts/stm32mp13-pinctrl.dtsi | 129 +++++++++++++++++++++++
>   arch/arm/boot/dts/stm32mp131.dtsi        |  97 ++++++++++++++++-
>   arch/arm/boot/dts/stm32mp135f-dk.dts     |  42 +++++++-
>   arch/arm/boot/dts/stm32mp15-pinctrl.dtsi |   4 +-
>   arch/arm/boot/dts/stm32mp157a-dk1.dts    |   3 -
>   arch/arm/boot/dts/stm32mp157c-dk2.dts    |   3 -
>   arch/arm/boot/dts/stm32mp157c-ed1.dts    |   8 +-
>   arch/arm/boot/dts/stm32mp157c-ev1.dts    |   9 +-
>   arch/arm/boot/dts/stm32mp15xx-dkx.dtsi   |   6 ++
>   9 files changed, 282 insertions(+), 19 deletions(-)
> 
Series applied on stm32-next.

Regards
Alex

      parent reply	other threads:[~2023-03-28 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 15:37 [PATCH v2 0/6] ARM: dts: stm32: stm32mp15 various fixes and add stm32mp13 usart nodes Valentin Caron
2023-03-28 15:37 ` [PATCH v2 1/6] ARM: dts: stm32: fix slew-rate of USART2 on stm32mp15xx-dkx Valentin Caron
2023-03-28 15:37 ` [PATCH v2 2/6] ARM: dts: stm32: clean uart aliases on stm32mp15xx-dkx boards Valentin Caron
2023-03-28 15:37 ` [PATCH v2 3/6] ARM: dts: stm32: clean uart aliases on stm32mp15xx-exx boards Valentin Caron
2023-03-28 15:37 ` [PATCH v2 4/6] ARM: dts: stm32: add uart nodes on stm32mp13 Valentin Caron
2023-03-28 15:37 ` [PATCH v2 5/6] ARM: dts: stm32: add pins for usart2/1/4/8 in stm32mp13-pinctrl Valentin Caron
2023-03-28 15:37 ` [PATCH v2 6/6] ARM: dts: stm32: add uart nodes and uart aliases on stm32mp135f-dk Valentin Caron
2023-03-28 15:58 ` 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=38c0e334-7b88-d139-37f7-ad3e99b0bb16@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --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+dt@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).