linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ryder.lee@mediatek.com (Ryder Lee)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v5 18/19] crypto: mediatek: move to generic async completion
Date: Tue, 15 Aug 2017 13:13:58 +0800	[thread overview]
Message-ID: <1502774038.962.2.camel@mtkswgap22> (raw)
In-Reply-To: <1502724094-23305-19-git-send-email-gilad@benyossef.com>

On Mon, 2017-08-14 at 18:21 +0300, Gilad Ben-Yossef wrote:
> The mediatek driver starts several async crypto ops and waits for their
> completions. Move it over to generic code doing the same.
> 
> Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
> ---

Acked-by: Ryder Lee <ryder.lee@mediatek.com>

>  drivers/crypto/mediatek/mtk-aes.c | 31 +++++--------------------------
>  1 file changed, 5 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/crypto/mediatek/mtk-aes.c b/drivers/crypto/mediatek/mtk-aes.c
> index 9e845e8..e2c7c95 100644
> --- a/drivers/crypto/mediatek/mtk-aes.c
> +++ b/drivers/crypto/mediatek/mtk-aes.c
> @@ -137,11 +137,6 @@ struct mtk_aes_gcm_ctx {
>  	struct crypto_skcipher *ctr;
>  };
>  
> -struct mtk_aes_gcm_setkey_result {
> -	int err;
> -	struct completion completion;
> -};
> -
>  struct mtk_aes_drv {
>  	struct list_head dev_list;
>  	/* Device list lock */
> @@ -936,17 +931,6 @@ static int mtk_aes_gcm_crypt(struct aead_request *req, u64 mode)
>  				    &req->base);
>  }
>  
> -static void mtk_gcm_setkey_done(struct crypto_async_request *req, int err)
> -{
> -	struct mtk_aes_gcm_setkey_result *result = req->data;
> -
> -	if (err == -EINPROGRESS)
> -		return;
> -
> -	result->err = err;
> -	complete(&result->completion);
> -}
> -
>  /*
>   * Because of the hardware limitation, we need to pre-calculate key(H)
>   * for the GHASH operation. The result of the encryption operation
> @@ -962,7 +946,7 @@ static int mtk_aes_gcm_setkey(struct crypto_aead *aead, const u8 *key,
>  		u32 hash[4];
>  		u8 iv[8];
>  
> -		struct mtk_aes_gcm_setkey_result result;
> +		struct crypto_wait wait;
>  
>  		struct scatterlist sg[1];
>  		struct skcipher_request req;
> @@ -1002,22 +986,17 @@ static int mtk_aes_gcm_setkey(struct crypto_aead *aead, const u8 *key,
>  	if (!data)
>  		return -ENOMEM;
>  
> -	init_completion(&data->result.completion);
> +	crypto_init_wait(&data->wait);
>  	sg_init_one(data->sg, &data->hash, AES_BLOCK_SIZE);
>  	skcipher_request_set_tfm(&data->req, ctr);
>  	skcipher_request_set_callback(&data->req, CRYPTO_TFM_REQ_MAY_SLEEP |
>  				      CRYPTO_TFM_REQ_MAY_BACKLOG,
> -				      mtk_gcm_setkey_done, &data->result);
> +				      crypto_req_done, &data->wait);
>  	skcipher_request_set_crypt(&data->req, data->sg, data->sg,
>  				   AES_BLOCK_SIZE, data->iv);
>  
> -	err = crypto_skcipher_encrypt(&data->req);
> -	if (err == -EINPROGRESS || err == -EBUSY) {
> -		err = wait_for_completion_interruptible(
> -			&data->result.completion);
> -		if (!err)
> -			err = data->result.err;
> -	}
> +	err = crypto_wait_req(crypto_skcipher_encrypt(&data->req),
> +			      &data->wait);
>  	if (err)
>  		goto out;
>  


--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-15  5:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 15:21 [PATCH v5 00/19] simplify crypto wait for async op Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 01/19] crypto: change transient busy return code to -EAGAIN Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 02/19] crypto: ccp: use -EAGAIN for transient busy indication Gilad Ben-Yossef
2017-08-14 16:55   ` Gary R Hook
2017-08-14 15:21 ` [PATCH v5 03/19] crypto: remove redundant backlog checks on EBUSY Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 04/19] crypto: marvell/cesa: " Gilad Ben-Yossef
2017-08-15  8:16   ` Boris Brezillon
2017-08-14 15:21 ` [PATCH v5 05/19] crypto: introduce crypto wait for async op Gilad Ben-Yossef
2017-08-15  2:23   ` Jonathan Cameron
2017-08-21 12:49     ` Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 06/19] crypto: move algif to generic async completion Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 07/19] crypto: move pub key " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 08/19] crypto: move drbg " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 09/19] crypto: move gcm " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 10/19] crypto: move testmgr " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 11/19] fscrypt: move " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 12/19] dm: move dm-verity " Gilad Ben-Yossef
2017-08-19 20:08   ` [dm-devel] " Mikulas Patocka
2017-08-21 12:48     ` Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 13/19] cifs: move " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 14/19] ima: " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 15/19] crypto: tcrypt: " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 16/19] crypto: talitos: " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 17/19] crypto: qce: " Gilad Ben-Yossef
2017-08-14 15:21 ` [PATCH v5 18/19] crypto: mediatek: " Gilad Ben-Yossef
2017-08-15  5:13   ` Ryder Lee [this message]
2017-08-14 15:21 ` [PATCH v5 19/19] crypto: adapt api sample to use async. op wait Gilad Ben-Yossef

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=1502774038.962.2.camel@mtkswgap22 \
    --to=ryder.lee@mediatek.com \
    --cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).