From: Randy Dunlap <rdunlap@infradead.org>
To: Daniel Parks <danielrparks@ti.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 6/6] crypto: sa2ul_pka: Add SA2UL PKA driver
Date: Mon, 8 Aug 2022 14:52:13 -0700 [thread overview]
Message-ID: <a7a08d22-e04a-d3c2-f245-b676aac9e551@infradead.org> (raw)
In-Reply-To: <b16fdaee8bcaaaa25d01c2e981ddf782ccf726b4.1659985696.git.danielrparks@ti.com>
Hi--
On 8/8/22 12:12, Daniel Parks wrote:
> diff --git a/drivers/crypto/sa2ul_pka/Kconfig b/drivers/crypto/sa2ul_pka/Kconfig
> new file mode 100644
> index 000000000000..c4f87b14878e
> --- /dev/null
> +++ b/drivers/crypto/sa2ul_pka/Kconfig
> @@ -0,0 +1,26 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +
> +config CRYPTO_DEV_SA2UL_PKA
> + tristate "Support for TI security accelerator public-key module"
> + depends on CRYPTO_DEV_SA2UL || COMPILE_TEST
> + select ARM64_CRYPTO
> + select CRYPTO_AKCIPHER
> + select CRYPTO_RSA
> + select PACKING
> + select CRYPTO_DH
> + help
> + The K3 security accelerator engine contains a public-key
> + cryptography module. Select this if you want to use hardware
> + acceleration for asymmetric cryptography on these devices. This
> + engine is not available to the Linux cores on most devices; check
> + your device tree if unsure.
> +
> +config CRYPTO_DEV_SA2UL_PKA_DEBUG
> + bool "Debugging options for TI security accelerator public-key module"
> + depends on CRYPTO_DEV_SA2UL_PKA
> + default n
> + help
> + Enables the module options 'snapshot' and 'poison_mem' to assist
> + in debugging the PKA driver. Choosing "y" will allow the root user
> + to extract cryptographic keys from the driver, so do not enable in
> + a production build.
Too much help text indentation.
from Documentation/process/coding-style.rst:
For all of the Kconfig* configuration files throughout the source tree,
the indentation is somewhat different. Lines under a ``config`` definition
are indented with one tab, while help text is indented an additional two
spaces.
--
~Randy
prev parent reply other threads:[~2022-08-08 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 19:12 [RFC PATCH 0/6] Add SA2UL Public Key Accelerator driver Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 1/6] dt-bindings: crypto: ti,sa2ul: add pka subdevice Daniel Parks
2022-08-09 5:44 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring
2022-08-08 19:12 ` [RFC PATCH 2/6] dt-bindings: crypto: add binding for eip29t2 public key accelerator (PKA) Daniel Parks
2022-08-09 5:47 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring
2022-08-08 19:12 ` [RFC PATCH 3/6] arm64: dts: ti: k3-am64-main: add SA2UL public key accelerator subdevice Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 4/6] arm64: dts: ti: k3-j721e-main: " Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 5/6] crypto: sa2ul: turn on PKA engine Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 6/6] crypto: sa2ul_pka: Add SA2UL PKA driver Daniel Parks
2022-08-08 21:52 ` Randy Dunlap [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=a7a08d22-e04a-d3c2-f245-b676aac9e551@infradead.org \
--to=rdunlap@infradead.org \
--cc=danielrparks@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@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: 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).