From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
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 v2 0/3] ARM: dts: stm32: add timers support on stm32mp13
Date: Tue, 17 Jan 2023 12:17:19 +0100 [thread overview]
Message-ID: <5c742bec-723d-b6dd-2571-a574ebbf3ad5@foss.st.com> (raw)
In-Reply-To: <20230110091713.444395-1-olivier.moysan@foss.st.com>
On 1/10/23 10:17, Olivier Moysan wrote:
> Add STM32 TIM and LPTIM support to STM32MP13 SoCs family.
> Add also support of timers available on DK board RPI expansion connector.
> These timers are configured in the DK board device tree, but let in
> disabled state by default.
>
> Changes in v2:
> - rebase serie
>
> Olivier Moysan (3):
> ARM: dts: stm32: add timers support on stm32mp131
> ARM: dts: stm32: add timer pins muxing for stm32mp135f-dk
> ARM: dts: stm32: add timers support on stm32mp135f-dk
>
> arch/arm/boot/dts/stm32mp13-pinctrl.dtsi | 60 +++
> arch/arm/boot/dts/stm32mp131.dtsi | 557 +++++++++++++++++++++++
> arch/arm/boot/dts/stm32mp135f-dk.dts | 58 +++
> 3 files changed, 675 insertions(+)
>
Series applied on stm32-next.
Regards
Alex
prev parent reply other threads:[~2023-01-17 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 9:17 [PATCH v2 0/3] ARM: dts: stm32: add timers support on stm32mp13 Olivier Moysan
2023-01-10 9:17 ` [PATCH v2 1/3] ARM: dts: stm32: add timers support on stm32mp131 Olivier Moysan
2023-01-10 9:17 ` [PATCH v2 2/3] ARM: dts: stm32: add timer pins muxing for stm32mp135f-dk Olivier Moysan
2023-01-10 9:17 ` [PATCH v2 3/3] ARM: dts: stm32: add timers support on stm32mp135f-dk Olivier Moysan
2023-01-17 11:17 ` 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=5c742bec-723d-b6dd-2571-a574ebbf3ad5@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--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=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.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;
as well as URLs for NNTP newsgroup(s).