From: Brijesh Singh <brijesh.singh@amd.com>
To: linux-crypto@vger.kernel.org
Cc: gary.hook@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net, Brijesh Singh <brijesh.singh@amd.com>
Subject: [PATCH v3 0/5] Introduce AMD Secure Processor device
Date: Thu, 29 Jun 2017 11:48:27 -0500 [thread overview]
Message-ID: <20170629164832.13252-1-brijesh.singh@amd.com> (raw)
CCP device (drivers/crypto/ccp/ccp.ko) is part of AMD Secure Processor,
which is not dedicated solely to crypto. The AMD Secure Processor includes
CCP and PSP (Platform Secure Processor) devices.
This patch series adds a framework that allows functional component of the
AMD Secure Processor to be initialized and handled appropriately. The series
does not makes any logic modification into CCP - it refactors the code to
integerate CCP into AMD secure processor framework.
---
Changes since v2:
- move the ccp->io_regs initialization before device setup().
- maintain the original Kconfig hierarchy
- rename ccp-{pci,platform}.c -> sp-{pci,platform}.c
- do not fail the module_init() when ccp device is not found
Changes since v1:
- remove unused function [sp_get_device()]
Brijesh Singh (5):
crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup
crypto: ccp - Introduce the AMD Secure Processor device
crypto: cpp - Abstract interrupt registeration
crypto: ccp - rename ccp driver initialize files as sp device
crypto: ccp - remove ccp_present() check from device initialize
drivers/crypto/Kconfig | 6 +-
drivers/crypto/ccp/Kconfig | 21 ++-
drivers/crypto/ccp/Makefile | 6 +-
drivers/crypto/ccp/ccp-dev-v3.c | 17 +-
drivers/crypto/ccp/ccp-dev-v5.c | 12 +-
drivers/crypto/ccp/ccp-dev.c | 124 ++++++++-----
drivers/crypto/ccp/ccp-dev.h | 25 +--
drivers/crypto/ccp/ccp-pci.c | 356 --------------------------------------
drivers/crypto/ccp/ccp-platform.c | 293 -------------------------------
drivers/crypto/ccp/sp-dev.c | 275 +++++++++++++++++++++++++++++
drivers/crypto/ccp/sp-dev.h | 132 ++++++++++++++
drivers/crypto/ccp/sp-pci.c | 276 +++++++++++++++++++++++++++++
drivers/crypto/ccp/sp-platform.c | 252 +++++++++++++++++++++++++++
include/linux/ccp.h | 7 +-
14 files changed, 1060 insertions(+), 742 deletions(-)
delete mode 100644 drivers/crypto/ccp/ccp-pci.c
delete mode 100644 drivers/crypto/ccp/ccp-platform.c
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
--
2.9.4
next reply other threads:[~2017-06-29 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 16:48 Brijesh Singh [this message]
2017-06-29 16:48 ` [PATCH v3 1/5] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup Brijesh Singh
2017-06-29 16:48 ` [PATCH v3 2/5] crypto: ccp - Introduce the AMD Secure Processor device Brijesh Singh
2017-06-29 16:48 ` [PATCH v3 3/5] crypto: cpp - Abstract interrupt registeration Brijesh Singh
2017-06-29 16:48 ` [PATCH v3 4/5] crypto: ccp - rename ccp driver initialize files as sp device Brijesh Singh
2017-06-29 16:48 ` [PATCH v3 5/5] crypto: ccp - remove ccp_present() check from device initialize 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=20170629164832.13252-1-brijesh.singh@amd.com \
--to=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 \
/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).