From: <nicolas.ferre@microchip.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Conor Dooley <conor.dooley@microchip.com>,
<linux-kernel@vger.kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
<devicetree@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: [PATCH] ARM: dts: at91/trivial: fix typo in crypto DT naming
Date: Wed, 6 Sep 2023 15:58:38 +0200 [thread overview]
Message-ID: <20230906135838.59247-1-nicolas.ferre@microchip.com> (raw)
From: Nicolas Ferre <nicolas.ferre@microchip.com>
Fix typo in DT name for TDES node.
Fixes: 4b6140b96dfe ("ARM: dts: at91: Use the generic "crypto" node name for the crypto IPs")
Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
---
arch/arm/boot/dts/microchip/sama5d4.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/microchip/sama5d4.dtsi b/arch/arm/boot/dts/microchip/sama5d4.dtsi
index 41284e013f53..cbfc60fed37c 100644
--- a/arch/arm/boot/dts/microchip/sama5d4.dtsi
+++ b/arch/arm/boot/dts/microchip/sama5d4.dtsi
@@ -694,7 +694,7 @@ aes: crypto@fc044000 {
clock-names = "aes_clk";
};
- tdes: crpyto@fc04c000 {
+ tdes: crypto@fc04c000 {
compatible = "atmel,at91sam9g46-tdes";
reg = <0xfc04c000 0x100>;
interrupts = <14 IRQ_TYPE_LEVEL_HIGH 0>;
--
2.39.2
next reply other threads:[~2023-09-06 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 13:58 nicolas.ferre [this message]
2023-09-06 14:21 ` [PATCH] ARM: dts: at91/trivial: fix typo in crypto DT naming Tudor Ambarus
2023-09-18 4:08 ` claudiu beznea
2023-09-18 11:22 ` Nicolas Ferre
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=20230906135838.59247-1-nicolas.ferre@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tudor.ambarus@linaro.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).