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>,
Lionel Debieve <lionel.debieve@foss.st.com>
Subject: Re: [PATCH] ARM: dts: stm32: add HASH on stm32mp131
Date: Fri, 22 Sep 2023 11:04:23 +0200 [thread overview]
Message-ID: <e69618dd-e3b4-f987-15c7-1363881930b7@foss.st.com> (raw)
In-Reply-To: <20230816142617.2625802-1-thomas.bourgoin@foss.st.com>
Hi
On 8/16/23 16:26, Thomas BOURGOIN wrote:
> From: Lionel Debieve <lionel.debieve@foss.st.com>
>
> Add the HASH support on stm32mp131.
>
> Signed-off-by: Lionel Debieve <lionel.debieve@foss.st.com>
> Signed-off-by: Thomas Bourgoin <thomas.bourgoin@foss.st.com>
> ---
> arch/arm/boot/dts/st/stm32mp131.dtsi | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm/boot/dts/st/stm32mp131.dtsi b/arch/arm/boot/dts/st/stm32mp131.dtsi
> index 672f3b7735a2..4e4f64cfb75b 100644
> --- a/arch/arm/boot/dts/st/stm32mp131.dtsi
> +++ b/arch/arm/boot/dts/st/stm32mp131.dtsi
> @@ -1210,6 +1210,17 @@ timer {
> };
> };
>
> + hash: hash@54003000 {
> + compatible = "st,stm32mp13-hash";
> + reg = <0x54003000 0x400>;
> + interrupts = <GIC_SPI 81 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&rcc HASH1>;
> + resets = <&rcc HASH1_R>;
> + dmas = <&mdma 30 0x2 0x1000a02 0x0 0x0>;
> + dma-names = "in";
> + status = "disabled";
> + };
> +
> mdma: dma-controller@58000000 {
> compatible = "st,stm32h7-mdma";
> reg = <0x58000000 0x1000>;
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2023-09-22 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:26 [PATCH] ARM: dts: stm32: add HASH on stm32mp131 Thomas BOURGOIN
2023-09-22 9:04 ` 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=e69618dd-e3b4-f987-15c7-1363881930b7@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=lionel.debieve@foss.st.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).