From: Cosar Dindar <cosardindar@gmail.com>
To: robh+dt@kernel.org
Cc: mark.rutland@arm.com, linux@armlinux.org.uk,
mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
fabien.dessenne@st.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Cosar Dindar <cosardindar@gmail.com>
Subject: [PATCH v2 5/5] ARM: dts: stm32: Add CRC support to stm32f429
Date: Sat, 20 May 2017 16:33:19 +0300 [thread overview]
Message-ID: <fb1c9f073b72f7337ceccb219e59c633853789ee.1495285223.git.cosardindar@gmail.com> (raw)
In-Reply-To: <cover.1495285223.git.cosardindar@gmail.com>
Add CRC32 Crypto support to stm32f429.
Signed-off-by: Cosar Dindar <cosardindar@gmail.com>
---
arch/arm/boot/dts/stm32f429.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index b2a2b5c..18343de 100644
--- a/arch/arm/boot/dts/stm32f429.dtsi
+++ b/arch/arm/boot/dts/stm32f429.dtsi
@@ -766,6 +766,13 @@
};
};
+ crc: crc@40023000 {
+ compatible = "st,stm32f4-crc";
+ reg = <0x40023000 0x400>;
+ clocks = <&rcc 0 STM32F4_AHB1_CLOCK(CRC)>;
+ status = "disabled";
+ };
+
rcc: rcc@40023810 {
#reset-cells = <1>;
#clock-cells = <2>;
--
2.7.4
prev parent reply other threads:[~2017-05-20 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 13:30 [PATCH v2 0/5] Add support for the STM32F4 CRC32 Cosar Dindar
2017-05-20 13:31 ` [PATCH v2 1/5] crypto : stm32 - Add STM32F4 CRC32 support Cosar Dindar
2017-05-20 13:32 ` [PATCH v2 2/5] dt-bindings : Document the STM32F4 CRC32 binding Cosar Dindar
2017-05-30 22:50 ` Rob Herring
2017-05-31 8:17 ` Cosar Dindar
2017-05-20 13:32 ` [PATCH v2 3/5] ARM: dts: stm32: enable CRC32 on stm32429-disco board Cosar Dindar
2017-05-22 11:14 ` kbuild test robot
2017-05-20 13:33 ` [PATCH v2 4/5] ARM: dts: stm32: enable CRC32 on stm32429i-eval board Cosar Dindar
2017-05-20 13:33 ` Cosar Dindar [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=fb1c9f073b72f7337ceccb219e59c633853789ee.1495285223.git.cosardindar@gmail.com \
--to=cosardindar@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®