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 1/3] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup
Date: Mon, 26 Jun 2017 16:17:16 -0500 [thread overview]
Message-ID: <262828f7-b433-b271-3caf-dbb4a8a7c5dd@amd.com> (raw)
In-Reply-To: <20170623160630.63292-2-brijesh.singh@amd.com>
On 6/23/2017 11:06 AM, Brijesh Singh wrote:
> Update pci and platform files to use devres interface to allocate the PCI
> and iomap resources. Also add helper functions to consolicate module init,
> exit and power mangagement code duplication.
>
> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
> ---
> drivers/crypto/ccp/ccp-dev-v3.c | 8 +++
> drivers/crypto/ccp/ccp-dev.c | 61 ++++++++++++++++++++
> drivers/crypto/ccp/ccp-dev.h | 6 ++
> drivers/crypto/ccp/ccp-pci.c | 114 +++++++++-----------------------------
> drivers/crypto/ccp/ccp-platform.c | 56 ++-----------------
> 5 files changed, 107 insertions(+), 138 deletions(-)
>
> diff --git a/drivers/crypto/ccp/ccp-dev-v3.c b/drivers/crypto/ccp/ccp-dev-v3.c
> index 367c2e3..1cae5a3 100644
> --- a/drivers/crypto/ccp/ccp-dev-v3.c
> +++ b/drivers/crypto/ccp/ccp-dev-v3.c
> @@ -586,6 +586,14 @@ static const struct ccp_actions ccp3_actions = {
> .irqhandler = ccp_irq_handler,
> };
>
> +const struct ccp_vdata ccpv3_platform = {
> + .version = CCP_VERSION(3, 0),
> + .setup = NULL,
> + .perform = &ccp3_actions,
> + .bar = 2,
Platform devices don't use BARs so should probably delete this (unless
you want to make it more generic and then use this value for the
IORESOURCE_MEM entry).
> + .offset = 0,
> +};
> +
> const struct ccp_vdata ccpv3 = {
> .version = CCP_VERSION(3, 0),
> .setup = NULL,
> diff --git a/drivers/crypto/ccp/ccp-dev.c b/drivers/crypto/ccp/ccp-dev.c
> index 2506b50..ce35e43 100644
> --- a/drivers/crypto/ccp/ccp-dev.c
> +++ b/drivers/crypto/ccp/ccp-dev.c
> @@ -538,8 +538,69 @@ bool ccp_queues_suspended(struct ccp_device *ccp)
>
> return ccp->cmd_q_count == suspended;
> }
> +
> +int ccp_dev_suspend(struct ccp_device *ccp, pm_message_t state)
> +{
> + unsigned long flags;
> + unsigned int i;
> +
> + spin_lock_irqsave(&ccp->cmd_lock, flags);
> +
> + ccp->suspending = 1;
> +
> + /* Wake all the queue kthreads to prepare for suspend */
> + for (i = 0; i < ccp->cmd_q_count; i++)
> + wake_up_process(ccp->cmd_q[i].kthread);
> +
> + spin_unlock_irqrestore(&ccp->cmd_lock, flags);
> +
> + /* Wait for all queue kthreads to say they're done */
> + while (!ccp_queues_suspended(ccp))
> + wait_event_interruptible(ccp->suspend_queue,
> + ccp_queues_suspended(ccp));
> +
> + return 0;
> +}
> +
> +int ccp_dev_resume(struct ccp_device *ccp)
> +{
> + unsigned long flags;
> + unsigned int i;
> +
> + spin_lock_irqsave(&ccp->cmd_lock, flags);
> +
> + ccp->suspending = 0;
> +
> + /* Wake up all the kthreads */
> + for (i = 0; i < ccp->cmd_q_count; i++) {
> + ccp->cmd_q[i].suspended = 0;
> + wake_up_process(ccp->cmd_q[i].kthread);
> + }
> +
> + spin_unlock_irqrestore(&ccp->cmd_lock, flags);
> +
> + return 0;
> +}
> #endif
>
> +int ccp_dev_init(struct ccp_device *ccp)
> +{
> + if (ccp->vdata->setup)
> + ccp->vdata->setup(ccp);
> +
> + ccp->io_regs = ccp->io_map + ccp->vdata->offset;
This should be before the above call to setup().
Thanks,
Tom
> +
> + return ccp->vdata->perform->init(ccp);
> +}
> +
> +void ccp_dev_destroy(struct ccp_device *ccp)
> +{
> + if (!ccp)
> + return;
> +
> + ccp->vdata->perform->destroy(ccp);
> +}
> +
> static int __init ccp_mod_init(void)
> {
> #ifdef CONFIG_X86
next prev parent reply other threads:[~2017-06-26 21:17 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 [this message]
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
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=262828f7-b433-b271-3caf-dbb4a8a7c5dd@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
all inboxes | Powered by JetHome®