From: Vincent Jardin via B4 Relay <devnull+vjardin.free.fr@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Sahil Malhotra" <sahil.malhotra@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Gaurav Jain" <gaurav.jain@nxp.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Vincent Jardin <vjardin@free.fr>
Subject: [PATCH 2/3] dt-bindings: crypto: fsl,sec-v4.0: add fsl,qi2-crypto-priority
Date: Mon, 28 Sep 2026 16:01:04 +0200 [thread overview]
Message-ID: <20260928-for-upstream-caam-qi2-priority-v1-2-e4a8e5f01dbc@free.fr> (raw)
In-Reply-To: <20260928-for-upstream-caam-qi2-priority-v1-0-e4a8e5f01dbc@free.fr>
From: Vincent Jardin <vjardin@free.fr>
Let a board set the crypto API priority of the algorithms the DPAA2
front end (dpaa2_caam) registers.
Benefits: Its DTS decides whether the SEC or the CPU is the default for
in-kernel crypto.
Signed-off-by: Vincent Jardin <vjardin@free.fr>
---
Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml b/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
index dcc755d2709a..0231fe3853b0 100644
--- a/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
+++ b/Documentation/devicetree/bindings/crypto/fsl,sec-v4.0.yaml
@@ -86,6 +86,15 @@ properties:
description: Defines the 'ERA' of the SEC device.
$ref: /schemas/types.yaml#/definitions/uint32
+ fsl,qi2-crypto-priority:
+ description:
+ Crypto API priority of the algorithms the DPAA2 (QI2) front end
+ registers. Below the CPU's own implementations, the SEC is used only
+ when asked for by driver name. The dpaa2_caam.priority module
+ parameter overrides it.
+ $ref: /schemas/types.yaml#/definitions/uint32
+ default: 2000
+
patternProperties:
'^jr@[0-9a-f]+$':
type: object
--
2.43.0
next prev parent reply other threads:[~2026-09-28 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 14:01 [PATCH 0/3] crypto: caam/qi2 - algorithm priority configurable Vincent Jardin via B4 Relay
2026-09-28 14:01 ` [PATCH 1/3] crypto: caam/qi2 - algorithm priority be a parameter Vincent Jardin via B4 Relay
2026-09-29 12:29 ` Herbert Xu
2026-09-29 12:57 ` Vincent Jardin
2026-09-28 14:01 ` Vincent Jardin via B4 Relay [this message]
2026-09-28 14:07 ` [PATCH 2/3] dt-bindings: crypto: fsl,sec-v4.0: add fsl,qi2-crypto-priority sashiko-bot
2026-09-29 9:08 ` Krzysztof Kozlowski
2026-09-29 12:58 ` Vincent Jardin
2026-09-28 14:01 ` [PATCH 3/3] crypto: caam/qi2 - priority from the DTS Vincent Jardin via B4 Relay
2026-09-28 22:41 ` [PATCH 0/3] crypto: caam/qi2 - algorithm priority configurable Eric Biggers
2026-09-29 16:45 ` Vincent Jardin
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=20260928-for-upstream-caam-qi2-priority-v1-2-e4a8e5f01dbc@free.fr \
--to=devnull+vjardin.free.fr@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=robh@kernel.org \
--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