[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0db0055f-9208-524f-74aa-674894ee90d3@amd.com>
Date: Thu, 2 Mar 2017 13:11:04 -0600
From: Brijesh Singh <brijesh.singh@....com>
To: Mark Rutland <mark.rutland@....com>
CC: <brijesh.singh@....com>, <simon.guinot@...uanux.org>,
<linux-efi@...r.kernel.org>, <kvm@...r.kernel.org>,
<rkrcmar@...hat.com>, <matt@...eblueprint.co.uk>,
<linux-pci@...r.kernel.org>, <linus.walleij@...aro.org>,
<gary.hook@....com>, <linux-mm@...ck.org>,
<paul.gortmaker@...driver.com>, <hpa@...or.com>, <cl@...ux.com>,
<dan.j.williams@...el.com>, <aarcange@...hat.com>,
<sfr@...b.auug.org.au>, <andriy.shevchenko@...ux.intel.com>,
<herbert@...dor.apana.org.au>, <bhe@...hat.com>,
<xemul@...allels.com>, <joro@...tes.org>, <x86@...nel.org>,
<peterz@...radead.org>, <piotr.luc@...el.com>, <mingo@...hat.com>,
<msalter@...hat.com>, <ross.zwisler@...ux.intel.com>, <bp@...e.de>,
<dyoung@...hat.com>, <thomas.lendacky@....com>, <jroedel@...e.de>,
<keescook@...omium.org>, <arnd@...db.de>, <toshi.kani@....com>,
<mathieu.desnoyers@...icios.com>, <luto@...nel.org>,
<devel@...uxdriverproject.org>, <bhelgaas@...gle.com>,
<tglx@...utronix.de>, <mchehab@...nel.org>,
<iamjoonsoo.kim@....com>, <labbott@...oraproject.org>,
<tony.luck@...el.com>, <alexandre.bounine@....com>,
<kuleshovmail@...il.com>, <linux-kernel@...r.kernel.org>,
<mcgrof@...nel.org>, <mst@...hat.com>,
<linux-crypto@...r.kernel.org>, <tj@...nel.org>,
<pbonzini@...hat.com>, <akpm@...ux-foundation.org>,
<davem@...emloft.net>
Subject: Re: [RFC PATCH v2 19/32] crypto: ccp: Introduce the AMD Secure
Processor device
Hi Mark,
On 03/02/2017 11:39 AM, Mark Rutland wrote:
> On Thu, Mar 02, 2017 at 10:16:15AM -0500, Brijesh Singh wrote:
>> The CCP device is part of the AMD Secure Processor. In order to expand the
>> usage of the AMD Secure Processor, create a framework that allows functional
>> components of the AMD Secure Processor to be initialized and handled
>> appropriately.
>>
>> Signed-off-by: Brijesh Singh <brijesh.singh@....com>
>> Signed-off-by: Tom Lendacky <thomas.lendacky@....com>
>> ---
>> drivers/crypto/Kconfig | 10 +
>> drivers/crypto/ccp/Kconfig | 43 +++--
>> drivers/crypto/ccp/Makefile | 8 -
>> drivers/crypto/ccp/ccp-dev-v3.c | 86 +++++-----
>> drivers/crypto/ccp/ccp-dev-v5.c | 73 ++++-----
>> drivers/crypto/ccp/ccp-dev.c | 137 +++++++++-------
>> drivers/crypto/ccp/ccp-dev.h | 35 ----
>> drivers/crypto/ccp/sp-dev.c | 308 ++++++++++++++++++++++++++++++++++++
>> drivers/crypto/ccp/sp-dev.h | 140 ++++++++++++++++
>> drivers/crypto/ccp/sp-pci.c | 324 ++++++++++++++++++++++++++++++++++++++
>> drivers/crypto/ccp/sp-platform.c | 268 +++++++++++++++++++++++++++++++
>> include/linux/ccp.h | 3
>> 12 files changed, 1240 insertions(+), 195 deletions(-)
>> create mode 100644 drivers/crypto/ccp/sp-dev.c
>> create mode 100644 drivers/crypto/ccp/sp-dev.h
>> create mode 100644 drivers/crypto/ccp/sp-pci.c
>> create mode 100644 drivers/crypto/ccp/sp-platform.c
>
>> diff --git a/drivers/crypto/ccp/Makefile b/drivers/crypto/ccp/Makefile
>> index 346ceb8..8127e18 100644
>> --- a/drivers/crypto/ccp/Makefile
>> +++ b/drivers/crypto/ccp/Makefile
>> @@ -1,11 +1,11 @@
>> -obj-$(CONFIG_CRYPTO_DEV_CCP_DD) += ccp.o
>> -ccp-objs := ccp-dev.o \
>> +obj-$(CONFIG_CRYPTO_DEV_SP_DD) += ccp.o
>> +ccp-objs := sp-dev.o sp-platform.o
>> +ccp-$(CONFIG_PCI) += sp-pci.o
>> +ccp-$(CONFIG_CRYPTO_DEV_CCP) += ccp-dev.o \
>> ccp-ops.o \
>> ccp-dev-v3.o \
>> ccp-dev-v5.o \
>> - ccp-platform.o \
>> ccp-dmaengine.o
>
> It looks like ccp-platform.c has morphed into sp-platform.c (judging by
> the compatible string and general shape of the code), and the original
> ccp-platform.c is no longer built.
>
> Shouldn't ccp-platform.c be deleted by this patch?
>
Good catch. Both ccp-platform.c and ccp-pci.c should have been deleted
by this patch. I missed deleting it, will fix in next rev.
~ Brijesh
Powered by blists - more mailing lists