From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Tudor Ambarus - M18064 <Tudor.Ambarus@microchip.com>,
"Claudiu Beznea - M18063" <Claudiu.Beznea@microchip.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH] ARM: dts: at91: sama7g5: Add crypto nodes
Date: Fri, 4 Feb 2022 18:42:46 +0100 [thread overview]
Message-ID: <d1933f3a-bd62-0cd3-4e09-ea9c20d356ac@microchip.com> (raw)
In-Reply-To: <baa455c6-cdcb-7db4-1857-c2479fc21953@microchip.com>
On 04/02/2022 at 18:36, Tudor Ambarus - M18064 wrote:
> On 2/4/22 15:37, Tudor Ambarus wrote:
>> Describe and enable the AES, SHA and TDES crypto IPs.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>> ---
>> arch/arm/boot/dts/sama7g5.dtsi | 35 ++++++++++++++++++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/sama7g5.dtsi b/arch/arm/boot/dts/sama7g5.dtsi
>> index 7972cb8c2562..1f2731a64139 100644
>> --- a/arch/arm/boot/dts/sama7g5.dtsi
>> +++ b/arch/arm/boot/dts/sama7g5.dtsi
>> @@ -393,6 +393,29 @@ pit64b1: timer@e1804000 {
>> clock-names = "pclk", "gclk";
>> };
>>
>> + aes: aes@e1810000 {
>> + compatible = "atmel,at91sam9g46-aes";
>> + reg = <0xe1810000 0x100>;
>> + interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
>> + dmas = <&dma0 AT91_XDMAC_DT_PERID(1)>,
>> + <&dma0 AT91_XDMAC_DT_PERID(2)>;
>> + dma-names = "tx", "rx";
>> + clocks = <&pmc PMC_TYPE_PERIPHERAL 27>;
>> + clock-names = "aes_clk";
>> + status = "okay";
>> + };
>> +
>> + sha: sha@e1814000 {
>> + compatible = "atmel,at91sam9g46-sha";
>> + reg = <0xe1814000 0x100>;
>> + interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
>> + dmas = <&dma0 AT91_XDMAC_DT_PERID(48)>;
>> + dma-names = "tx";
>> + clocks = <&pmc PMC_TYPE_PERIPHERAL 83>;
>> + clock-names = "sha_clk";
>> + status = "okay";
>> + };
>> +
>> flx0: flexcom@e1818000 {
>> compatible = "atmel,sama5d2-flexcom";
>> reg = <0xe1818000 0x200>;
>> @@ -475,6 +498,18 @@ trng: rng@e2010000 {
>> status = "disabled";
>> };
>>
>> + tdes@e2014000 {
> tdes: tdes@e2014000
>
> I should have added a label here. Nicolas, maybe you can add it when applying,
> if everything else looks ok to you.
Yep, if everything else is okay I can definitively add it when applying.
Regards,
Nicolas
>> + compatible = "atmel,at91sam9g46-tdes";
>> + reg = <0xe2014000 0x100>;
>> + interrupts = <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>;
>> + dmas = <&dma0 AT91_XDMAC_DT_PERID(54)>,
>> + <&dma0 AT91_XDMAC_DT_PERID(53)>;
>> + dma-names = "tx", "rx";
>> + clocks = <&pmc PMC_TYPE_PERIPHERAL 96>;
>> + clock-names = "tdes_clk";
>> + status = "okay";
>> + };
>> +
>> flx4: flexcom@e2018000 {
>> compatible = "atmel,sama5d2-flexcom";
>> reg = <0xe2018000 0x200>;
>
--
Nicolas Ferre
prev parent reply other threads:[~2022-02-04 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:37 [PATCH] ARM: dts: at91: sama7g5: Add crypto nodes Tudor Ambarus
2022-02-04 17:36 ` Tudor.Ambarus
2022-02-04 17:42 ` Nicolas Ferre [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=d1933f3a-bd62-0cd3-4e09-ea9c20d356ac@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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