From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Thomas Bourgoin <thomas.bourgoin@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.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 0/3] Enable the CRC and CRYP IP on STM32MP135F-DK board.
Date: Thu, 29 Feb 2024 10:27:24 +0100 [thread overview]
Message-ID: <1da6174d-a8b2-420b-a1f2-db6975d68948@foss.st.com> (raw)
In-Reply-To: <20240219113745.92538-1-thomas.bourgoin@foss.st.com>
Hi Thomas
On 2/19/24 12:37, Thomas Bourgoin wrote:
> Enable the CRC and CRYP internal peripherals on STM32MP135F-DK board.
>
> The first 2 patches adds the node crc1 in file stm32mp131.dtsi and
> enables it for the board stm32mp135f-dk.
> The last patch of the patchset enables the node cryp for the board
> stm32mp135f-dk.
>
> Lionel Debieve (2):
> ARM: dts: stm32: add CRC on stm32mp131
> ARM: dts: stm32: enable CRC on stm32mp135f-dk
>
> Thomas Bourgoin (1):
> ARM: dts: stm32: enable crypto accelerator on stm32mp135f-dk
>
> arch/arm/boot/dts/st/stm32mp131.dtsi | 7 +++++++
> arch/arm/boot/dts/st/stm32mp135f-dk.dts | 8 ++++++++
> 2 files changed, 15 insertions(+)
>
Series applied on stm32-next.
Thanks
Alex
> --
> 2.25.1
>
prev parent reply other threads:[~2024-02-29 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 11:37 [PATCH 0/3] Enable the CRC and CRYP IP on STM32MP135F-DK board Thomas Bourgoin
2024-02-19 11:37 ` [PATCH 1/3] ARM: dts: stm32: add CRC on stm32mp131 Thomas Bourgoin
2024-02-19 11:37 ` [PATCH 2/3] ARM: dts: stm32: enable CRC on stm32mp135f-dk Thomas Bourgoin
2024-02-19 11:37 ` [PATCH 3/3] ARM: dts: stm32: enable crypto accelerator " Thomas Bourgoin
2024-02-29 9:27 ` 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=1da6174d-a8b2-420b-a1f2-db6975d68948@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=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thomas.bourgoin@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).