From: <Claudiu.Beznea@microchip.com>
To: <Tudor.Ambarus@microchip.com>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>
Cc: <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: at91: sama7g5: Add crypto nodes
Date: Mon, 7 Feb 2022 10:33:47 +0000 [thread overview]
Message-ID: <ed6abe6c-11f4-8a5b-e97e-dbfe8c6f093f@microchip.com> (raw)
In-Reply-To: <20220207034303.72827-1-tudor.ambarus@microchip.com>
On 07.02.2022 05:43, Tudor Ambarus wrote:
> Describe and enable the AES, SHA and TDES crypto IPs. Tested with the
> extra run-time self tests of the registered crypto algorithms.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> v2:
> - add label to the tdes node
> - update commit description and specify testing method
> - put clocks and clock-names properties before dmas and dma-names
> because the clocks are mandatory, while DMA is optional for TDES and SHA
>
> 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..a87f498cf098 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>;
> + clocks = <&pmc PMC_TYPE_PERIPHERAL 27>;
> + clock-names = "aes_clk";
> + dmas = <&dma0 AT91_XDMAC_DT_PERID(1)>,
> + <&dma0 AT91_XDMAC_DT_PERID(2)>;
> + dma-names = "tx", "rx";
> + status = "okay";
Hi Tudor,
Lines with:
status = "okay";
could be removed as this is the default state.
Thank you,
Claudiu Beznea
> + };
> +
> + sha: sha@e1814000 {
> + compatible = "atmel,at91sam9g46-sha";
> + reg = <0xe1814000 0x100>;
> + interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&pmc PMC_TYPE_PERIPHERAL 83>;
> + clock-names = "sha_clk";
> + dmas = <&dma0 AT91_XDMAC_DT_PERID(48)>;
> + dma-names = "tx";
> + status = "okay";
> + };
> +
> flx0: flexcom@e1818000 {
> compatible = "atmel,sama5d2-flexcom";
> reg = <0xe1818000 0x200>;
> @@ -475,6 +498,18 @@ trng: rng@e2010000 {
> status = "disabled";
> };
>
> + tdes: tdes@e2014000 {
> + compatible = "atmel,at91sam9g46-tdes";
> + reg = <0xe2014000 0x100>;
> + interrupts = <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&pmc PMC_TYPE_PERIPHERAL 96>;
> + clock-names = "tdes_clk";
> + dmas = <&dma0 AT91_XDMAC_DT_PERID(54)>,
> + <&dma0 AT91_XDMAC_DT_PERID(53)>;
> + dma-names = "tx", "rx";
> + status = "okay";
> + };
> +
> flx4: flexcom@e2018000 {
> compatible = "atmel,sama5d2-flexcom";
> reg = <0xe2018000 0x200>;
prev parent reply other threads:[~2022-02-07 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 3:43 [PATCH v2] ARM: dts: at91: sama7g5: Add crypto nodes Tudor Ambarus
2022-02-07 10:33 ` Claudiu.Beznea [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=ed6abe6c-11f4-8a5b-e97e-dbfe8c6f093f@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@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;
as well as URLs for NNTP newsgroup(s).