From: Alexandre Torgue <alexandre.torgue@st.com>
To: Lionel Debieve <lionel.debieve@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: dts: stm32: Add HASH support on stm32mp157c
Date: Mon, 25 Jun 2018 14:16:19 +0200 [thread overview]
Message-ID: <e830c0ab-409a-7d6c-b654-9640f0fe36fd@st.com> (raw)
In-Reply-To: <20180514100034.10282-1-lionel.debieve@st.com>
Hi Lionel,
On 05/14/2018 12:00 PM, Lionel Debieve wrote:
> This patch add HASH instance of the stm32mp157c SoC
>
> Signed-off-by: Lionel Debieve <lionel.debieve@st.com>
> ---
> arch/arm/boot/dts/stm32mp157c.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi b/arch/arm/boot/dts/stm32mp157c.dtsi
> index b66f673b5038..cb39fb6d9960 100644
> --- a/arch/arm/boot/dts/stm32mp157c.dtsi
> +++ b/arch/arm/boot/dts/stm32mp157c.dtsi
> @@ -702,6 +702,18 @@
> status = "disabled";
> };
>
> + hash1: hash@54002000 {
> + compatible = "st,stm32f756-hash";
> + reg = <0x54002000 0x400>;
> + interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&rcc HASH1>;
> + resets = <&rcc HASH1_R>;
> + dmas = <&mdma1 31 0x10 0x1000A02 0x0 0x0 0x0>;
> + dma-names = "in";
> + dma-maxburst = <2>;
> + status = "disabled";
> + };
> +
> rng1: rng@54003000 {
> compatible = "st,stm32-rng";
> reg = <0x54003000 0x400>;
>
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2018-06-25 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 10:00 [PATCH 1/1] ARM: dts: stm32: Add HASH support on stm32mp157c Lionel Debieve
2018-06-25 12:16 ` 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=e830c0ab-409a-7d6c-b654-9640f0fe36fd@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lionel.debieve@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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