From: Lokesh Vutla <lokeshvutla@ti.com> To: <herbert@gondor.apana.org.au>, <linux-crypto@vger.kernel.org>, <davem@davemloft.net> Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <t-kristo@ti.com>, <nsekhar@ti.com>, <lokeshvutla@ti.com> Subject: [PATCH v2 2/7] crypto: omap-aes: Increase priority of hw accelerator Date: Tue, 7 Jul 2015 21:01:44 +0530 [thread overview] Message-ID: <1436283109-13318-3-git-send-email-lokeshvutla@ti.com> (raw) In-Reply-To: <1436283109-13318-1-git-send-email-lokeshvutla@ti.com> Increasing the priority of omap-aes hw algos, in order to take precedence over sw algos. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> --- drivers/crypto/omap-aes.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c index 4a0e808..54925d9 100644 --- a/drivers/crypto/omap-aes.c +++ b/drivers/crypto/omap-aes.c @@ -834,7 +834,7 @@ static struct crypto_alg algs_ecb_cbc[] = { { .cra_name = "ecb(aes)", .cra_driver_name = "ecb-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, @@ -856,7 +856,7 @@ static struct crypto_alg algs_ecb_cbc[] = { { .cra_name = "cbc(aes)", .cra_driver_name = "cbc-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, @@ -882,7 +882,7 @@ static struct crypto_alg algs_ctr[] = { { .cra_name = "ctr(aes)", .cra_driver_name = "ctr-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Lokesh Vutla <lokeshvutla@ti.com> To: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, davem@davemloft.net Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, t-kristo@ti.com, nsekhar@ti.com, lokeshvutla@ti.com Subject: [PATCH v2 2/7] crypto: omap-aes: Increase priority of hw accelerator Date: Tue, 7 Jul 2015 21:01:44 +0530 [thread overview] Message-ID: <1436283109-13318-3-git-send-email-lokeshvutla@ti.com> (raw) In-Reply-To: <1436283109-13318-1-git-send-email-lokeshvutla@ti.com> Increasing the priority of omap-aes hw algos, in order to take precedence over sw algos. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> --- drivers/crypto/omap-aes.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c index 4a0e808..54925d9 100644 --- a/drivers/crypto/omap-aes.c +++ b/drivers/crypto/omap-aes.c @@ -834,7 +834,7 @@ static struct crypto_alg algs_ecb_cbc[] = { { .cra_name = "ecb(aes)", .cra_driver_name = "ecb-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, @@ -856,7 +856,7 @@ static struct crypto_alg algs_ecb_cbc[] = { { .cra_name = "cbc(aes)", .cra_driver_name = "cbc-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, @@ -882,7 +882,7 @@ static struct crypto_alg algs_ctr[] = { { .cra_name = "ctr(aes)", .cra_driver_name = "ctr-aes-omap", - .cra_priority = 100, + .cra_priority = 300, .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_KERN_DRIVER_ONLY | CRYPTO_ALG_ASYNC, -- 1.9.1
next prev parent reply other threads:[~2015-07-07 15:34 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-07 15:31 [PATCH v2 0/7] crypto: omap-aes: Add support for GCM mode Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-07 15:31 ` [PATCH v2 1/7] crypto: omap-aes: Fix CTR mode Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla [this message] 2015-07-07 15:31 ` [PATCH v2 2/7] crypto: omap-aes: Increase priority of hw accelerator Lokesh Vutla 2015-07-07 15:31 ` [PATCH v2 3/7] crypto: omap-aes: Fix configuring of AES mode Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-07 15:31 ` [PATCH v2 4/7] crypto: omap-aes: Use BIT() macro Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-07 15:31 ` [PATCH v2 5/7] crypto: aead: Add aead_request_cast() api Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-08 3:56 ` Herbert Xu 2015-07-08 6:43 ` Lokesh Vutla 2015-07-08 6:43 ` Lokesh Vutla 2015-07-07 15:31 ` [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-08 4:18 ` Herbert Xu 2015-07-08 6:59 ` Lokesh Vutla 2015-07-08 6:59 ` Lokesh Vutla 2015-07-08 7:48 ` Herbert Xu 2015-07-08 7:53 ` Herbert Xu 2015-07-08 8:30 ` Lokesh Vutla 2015-07-08 8:30 ` Lokesh Vutla 2015-07-08 8:15 ` Lokesh Vutla 2015-07-08 8:15 ` Lokesh Vutla 2015-07-10 14:09 ` Lokesh Vutla 2015-07-10 14:09 ` Lokesh Vutla 2015-07-11 2:40 ` Herbert Xu 2015-09-15 13:28 ` [PATCH v3] " Lokesh Vutla 2015-09-15 13:28 ` Lokesh Vutla 2015-09-18 13:17 ` Herbert Xu 2015-09-20 10:38 ` Matthijs van Duin 2015-07-07 15:31 ` [PATCH v2 7/7] crypto: tcrypt: Fix AEAD speed tests Lokesh Vutla 2015-07-07 15:31 ` Lokesh Vutla 2015-07-08 7:11 ` [PATCH v2 0/7] crypto: omap-aes: Add support for GCM mode 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=1436283109-13318-3-git-send-email-lokeshvutla@ti.com \ --to=lokeshvutla@ti.com \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=nsekhar@ti.com \ --cc=t-kristo@ti.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.