From: Herbert Xu <herbert@gondor.apana.org.au>
To: vjardin@free.fr
Cc: "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Sahil Malhotra" <sahil.malhotra@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"Eric Biggers" <ebiggers@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] crypto: caam/qi2 - lower the algorithm priority
Date: Thu, 8 Oct 2026 19:21:51 +1100 [thread overview]
Message-ID: <asdSn2eaGbEs2FM_@gondor.apana.org.au> (raw)
In-Reply-To: <20260929-for-upstream-caam-qi2-priority-v2-1-bf0559ebf574@free.fr>
On Tue, Sep 29, 2026 at 10:29:04PM +0200, Vincent Jardin via B4 Relay wrote:
> From: Vincent Jardin <vjardin@free.fr>
>
> Lower the priority to 100, as done for QAT in commit
> 8024774190a5 ("crypto: qat - lower priority for skcipher and aead algorithms").
>
> The SEC stays reachable by driver name, and user space can raise its
> priority through the crypto_user interface.
>
> Suggested-by: Herbert Xu <herbert@gondor.apana.org.au>
> Link: https://lore.kernel.org/r/aruvJECCDNdguMdw@gondor.apana.org.au
> Signed-off-by: Vincent Jardin <vjardin@free.fr>
> ---
> v2 lowers the priority to 100, as was done for QAT, and leaves the
> choice to user space through crypto_user.
> ---
> Changes in v2:
> - Drop both the dpaa2_caam.priority module parameter and the
> fsl,qi2-crypto-priority DT property
> - Lower the default priority to 100, user space adjust it with
> crypto_user (Herbert).
> - No policy in the device tree (Krzysztof, Eric).
> - Link to v1: https://lore.kernel.org/r/20260928-for-upstream-caam-qi2-priority-v1-0-e4a8e5f01dbc@free.fr
> ---
> drivers/crypto/caam/caamalg_qi2.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-10-08 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 20:29 Vincent Jardin via B4 Relay
2026-09-30 7:21 ` [EXT] " Sahil Malhotra (OSS)
2026-09-30 9:08 ` Vincent Jardin
2026-09-30 10:19 ` Sahil Malhotra (OSS)
2026-10-08 8:21 ` Herbert Xu [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=asdSn2eaGbEs2FM_@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@nxp.com \
--cc=vjardin@free.fr \
/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®