From: Tom Lendacky <thomas.lendacky@amd.com>
To: Brijesh Singh <brijesh.singh@amd.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: gary.hook@amd.com, herbert@gondor.apana.org.au, davem@davemloft.net
Subject: Re: [PATCH v2 2/3] crypto: ccp - Introduce the AMD Secure Processor device
Date: Wed, 28 Jun 2017 15:30:23 -0500 [thread overview]
Message-ID: <fd5c85fd-1270-f8fd-0562-3c52c03b3a19@amd.com> (raw)
In-Reply-To: <79ad80ef-1c25-334a-9885-77373f356df2@amd.com>
On 6/28/2017 3:26 PM, Brijesh Singh wrote:
>
>
> On 06/28/2017 02:53 PM, Tom Lendacky wrote:
>>>
>>> In this I am leaving the top level config as-is and adding
>>> CONFIG_CRYPTO_DEV_SP_CCP to enable the CCP device support inside the
>>> SP device driver.
>>>
>>> [*] Support for AMD Secure Processor
>>> <M> Secure Processor device driver
>>> <M> Encryption and hashing offload support
>>> -*- Cryptographic Coprocessor device
>>
>> I think the "Encryption and hashing offload support" should be indented
>> under "Cryptographic Coprocessor device" since it is a function of the
>> CCP and not the SP. Not sure if we can remove a level of menu somehow,
>> something to explore.
>
> Good point, the updated Kconfig looks like this and let me know it works.
I think that looks better.
Thanks,
Tom
>
> [*] Support for AMD Secure Processor
> <M> Secure Processor device driver
> [*] Cryptographic Coprocessor device
> <M> Encryption and hashing offload support
>
> # cat drivers/crypto/ccp/Kconfig
>
> config CRYPTO_DEV_CCP_DD
> tristate "Secure Processor device driver"
> default m
> help
> Provides AMD Secure Processor device driver.
> If you choose 'M' here, this module will be called ccp.
>
> config CRYPTO_DEV_SP_CCP
> bool "Cryptographic Coprocessor device"
> default y
> depends on CRYPTO_DEV_CCP_DD
> select HW_RANDOM
> select DMA_ENGINE
> select DMADEVICES
> select CRYPTO_SHA1
> select CRYPTO_SHA256
> help
> Provides the support for AMD Cryptographic Coprocessor (CCP)
> device
> which can be used to offload encryption operations such as
> SHA, AES
> and more.
>
> config CRYPTO_DEV_CCP_CRYPTO
> tristate "Encryption and hashing offload support"
> default m
> depends on CRYPTO_DEV_CCP_DD
> depends on CRYPTO_DEV_SP_CCP
> select CRYPTO_HASH
> select CRYPTO_BLKCIPHER
> select CRYPTO_AUTHENC
> help
> Support for using the cryptographic API with the AMD
> Cryptographic
> Coprocessor. This module supports offload of SHA and AES
> algorithms.
> If you choose 'M' here, this module will be called ccp_crypto.
next prev parent reply other threads:[~2017-06-28 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 16:06 [PATCH v2 0/3] Introduce AMD Secure Processor device Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 1/3] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup Brijesh Singh
2017-06-26 21:17 ` Tom Lendacky
2017-06-26 22:22 ` Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 2/3] crypto: ccp - Introduce the AMD Secure Processor device Brijesh Singh
2017-06-28 17:47 ` Tom Lendacky
2017-06-28 19:39 ` Brijesh Singh
2017-06-28 19:53 ` Tom Lendacky
2017-06-28 20:26 ` Brijesh Singh
2017-06-28 20:30 ` Tom Lendacky [this message]
2017-07-06 8:37 ` kbuild test robot
2017-07-06 12:27 ` Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 3/3] crypto: cpp - Abstract interrupt registeration Brijesh Singh
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=fd5c85fd-1270-f8fd-0562-3c52c03b3a19@amd.com \
--to=thomas.lendacky@amd.com \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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