Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	gary.hook@amd.com, thomas.lendacky@amd.com,
	herbert@gondor.apana.org.au, davem@davemloft.net
Subject: Re: [PATCH 0/3] Introduce AMD Secure Processor device
Date: Thu, 22 Jun 2017 15:25:40 +0200	[thread overview]
Message-ID: <20170622132539.GA14239@localhost> (raw)
In-Reply-To: <20170622114204.4361-1-brijesh.singh@amd.com>

On Thu 2017-06-22 06:42:01, Brijesh Singh wrote:
> 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.

Ok, so this is just preparation. When finished, what services will it provide
to Linux userland?

  parent reply	other threads:[~2017-06-22 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 11:42 [PATCH 0/3] Introduce AMD Secure Processor device Brijesh Singh
2017-06-22 11:42 ` [PATCH 1/3] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup Brijesh Singh
2017-06-22 11:42 ` [PATCH 2/3] crypto: ccp - Introduce the AMD Secure Processor device Brijesh Singh
2017-06-22 11:42 ` [PATCH 3/3] crypto: cpp - Abstract interrupt registeration Brijesh Singh
2017-06-22 13:25 ` Pavel Machek [this message]
2017-06-23 21:23   ` [PATCH 0/3] Introduce AMD Secure Processor device 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=20170622132539.GA14239@localhost \
    --to=pavel@ucw.cz \
    --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 \
    --cc=thomas.lendacky@amd.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