[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f9e1481-db9c-cd5f-c38d-bdcd3040315f@linux.microsoft.com>
Date: Wed, 8 Jun 2022 12:33:41 -0700
From: Dhananjay Phadke <dphadke@...ux.microsoft.com>
To: Neal Liu <neal_liu@...eedtech.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S . Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...id.au>,
Johnny Huang <johnny_huang@...eedtech.com>
Cc: linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] crypto: aspeed: add HACE crypto driver
On 6/6/2022 8:43 PM, Neal Liu wrote:
>>> +struct aspeed_hace_alg {
>>> + struct aspeed_hace_dev *hace_dev;
>>> + union {
>>> + struct skcipher_alg skcipher;
>>> + struct aead_alg aead;
>>> + struct ahash_alg ahash;
>>> + struct kpp_alg kpp;
>>> + struct akcipher_alg akcipher;
>>
>> Your patch dont do any kpp or akcipher (and aead/skcipher also).
>> Please drop this.
>
> I miss this part, I'll revise it in next patch, thanks.
Hi Neal,
Are you planning to submit aead separately? HW programming interface
for aes-gcm is almost same as other aes modes except extra regs/fields
for tag etc.
Thanks,
Dhananjay
Powered by blists - more mailing lists