From: <Tudor.Ambarus@microchip.com>
To: <Kavyasree.Kotagiri@microchip.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>
Cc: <UNGLinuxDriver@microchip.com>, <linux-crypto@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] crypto: atmel: add support for AES and SHA IPs available on lan966x SoC
Date: Fri, 4 Feb 2022 09:54:19 +0000 [thread overview]
Message-ID: <97a76204-520e-2899-2f87-a28396e012b4@microchip.com> (raw)
In-Reply-To: <20220128071755.25277-1-kavyasree.kotagiri@microchip.com>
On 1/28/22 09:17, Kavyasree Kotagiri wrote:
> This patch adds support for hardware version of AES and SHA IPs
> available on lan966x SoC.
>
> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Tested-by: Tudor Ambarus <tudor.ambarus@microchip.com>
tested with sama7g5 which has:
[ 0.891304] atmel_aes e1810000.aes: version: 0x702
[ 0.896042] atmel_sha e1814000.sha: version: 0x700
> ---
> v1 -> v2:
> - Removed fallthrough line, as it is not required.
>
> drivers/crypto/atmel-aes.c | 1 +
> drivers/crypto/atmel-sha.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/crypto/atmel-aes.c b/drivers/crypto/atmel-aes.c
> index fe0558403191..f72c6b3e4ad8 100644
> --- a/drivers/crypto/atmel-aes.c
> +++ b/drivers/crypto/atmel-aes.c
> @@ -2509,6 +2509,7 @@ static void atmel_aes_get_cap(struct atmel_aes_dev *dd)
>
> /* keep only major version number */
> switch (dd->hw_version & 0xff0) {
> + case 0x700:
> case 0x500:
> dd->caps.has_dualbuff = 1;
> dd->caps.has_cfb64 = 1;
> diff --git a/drivers/crypto/atmel-sha.c b/drivers/crypto/atmel-sha.c
> index 1b13f601fd95..d1628112dacc 100644
> --- a/drivers/crypto/atmel-sha.c
> +++ b/drivers/crypto/atmel-sha.c
> @@ -2508,6 +2508,7 @@ static void atmel_sha_get_cap(struct atmel_sha_dev *dd)
>
> /* keep only major version number */
> switch (dd->hw_version & 0xff0) {
> + case 0x700:
> case 0x510:
> dd->caps.has_dma = 1;
> dd->caps.has_dualbuff = 1;
next prev parent reply other threads:[~2022-02-04 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 7:17 Kavyasree Kotagiri
2022-02-04 9:54 ` Tudor.Ambarus [this message]
2022-02-05 4:31 ` Herbert Xu
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=97a76204-520e-2899-2f87-a28396e012b4@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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®