mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <kamlesh@ti.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
	<quic_bjorande@quicinc.com>, <arnd@arndb.de>,
	<geert+renesas@glider.be>, <krzysztof.kozlowski@linaro.org>,
	<treding@nvidia.com>, <nfraprado@collabora.com>,
	<broonie@kernel.org>, <rafal@milecki.pl>, <vigneshr@ti.com>,
	<afd@ti.com>, <j-choudhary@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <praneeth@ti.com>,
	Kamlesh Gurudasani <kamlesh@ti.com>
Subject: [PATCH] arm64: defconfig: Enable security accelerator driver for TI K3 SoCs
Date: Mon, 17 Apr 2023 18:57:17 +0530	[thread overview]
Message-ID: <20230417132717.1990023-2-kamlesh@ti.com> (raw)
In-Reply-To: <20230417132717.1990023-1-kamlesh@ti.com>

From: Kamlesh Gurudasani <kamlesh@ti.com>

Enable TI's SA2UL driver to support security acceleration on TI K3 SoCs.

Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
---
 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index b6342b40c600..c9e3b3b9bab4 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -1477,6 +1477,7 @@ CONFIG_CRYPTO_DEV_HISI_SEC2=m
 CONFIG_CRYPTO_DEV_HISI_ZIP=m
 CONFIG_CRYPTO_DEV_HISI_HPRE=m
 CONFIG_CRYPTO_DEV_HISI_TRNG=m
+CONFIG_CRYPTO_DEV_SA2UL=m
 CONFIG_DMA_RESTRICTED_POOL=y
 CONFIG_CMA_SIZE_MBYTES=32
 CONFIG_PRINTK_TIME=y
-- 
2.34.1


  reply	other threads:[~2023-04-17 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 13:27 [PATCH] arm64: defconfig: Enable crypto test module kamlesh
2023-04-17 13:27 ` kamlesh [this message]
2023-04-17 14:36   ` [PATCH] arm64: defconfig: Enable security accelerator driver for TI K3 SoCs Arnd Bergmann
2023-04-17 14:33 ` [PATCH] arm64: defconfig: Enable crypto test module Arnd Bergmann

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=20230417132717.1990023-2-kamlesh@ti.com \
    --to=kamlesh@ti.com \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=geert+renesas@glider.be \
    --cc=j-choudhary@ti.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=praneeth@ti.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=rafal@milecki.pl \
    --cc=treding@nvidia.com \
    --cc=vigneshr@ti.com \
    --cc=will@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

all inboxes | Powered by JetHome®