From: Thomas Bourgoin <thomas.bourgoin@foss.st.com>
To: 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>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Thomas Bourgoin <thomas.bourgoin@foss.st.com>,
<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: [PATCH 2/3] ARM: dts: stm32: enable CRC on stm32mp135f-dk
Date: Mon, 19 Feb 2024 12:37:44 +0100 [thread overview]
Message-ID: <20240219113745.92538-3-thomas.bourgoin@foss.st.com> (raw)
In-Reply-To: <20240219113745.92538-1-thomas.bourgoin@foss.st.com>
From: Lionel Debieve <lionel.debieve@foss.st.com>
Enable Cyclic redundancy check on stm32mp135f-dk.
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/stm32mp135f-dk.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/st/stm32mp135f-dk.dts b/arch/arm/boot/dts/st/stm32mp135f-dk.dts
index eea740d097c7..a7b1b2ca9d0b 100644
--- a/arch/arm/boot/dts/st/stm32mp135f-dk.dts
+++ b/arch/arm/boot/dts/st/stm32mp135f-dk.dts
@@ -93,6 +93,10 @@ channel@12 {
};
};
+&crc1 {
+ status = "okay";
+};
+
&i2c1 {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&i2c1_pins_a>;
--
2.25.1
next prev parent reply other threads:[~2024-02-19 11:40 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 ` Thomas Bourgoin [this message]
2024-02-19 11:37 ` [PATCH 3/3] ARM: dts: stm32: enable crypto accelerator on stm32mp135f-dk Thomas Bourgoin
2024-02-29 9:27 ` [PATCH 0/3] Enable the CRC and CRYP IP on STM32MP135F-DK board Alexandre TORGUE
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=20240219113745.92538-3-thomas.bourgoin@foss.st.com \
--to=thomas.bourgoin@foss.st.com \
--cc=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 \
/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).