From: Brijesh Singh <brijesh.singh@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: brijesh.singh@amd.com, 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 17:22:10 -0500 [thread overview]
Message-ID: <ec17a9f8-0a5b-4d93-ca9c-a3755ff027ec@amd.com> (raw)
In-Reply-To: <262828f7-b433-b271-3caf-dbb4a8a7c5dd@amd.com>
On 06/26/2017 04:17 PM, Tom Lendacky wrote:
>> +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).
>
Yep, we don't need bar for platform device, it was copy paste from existing
ccpv3 structure. I will fix it in v3. thanks
>> +}
>> #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().
>
Good catch, actually the second patch takes care of it. But I agree with your
feedback, I will make sure that io_regs is set before invoking the setup() in
the first patch itself.
Thanks
Brijesh
next prev parent reply other threads:[~2017-06-26 22:22 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 [this message]
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=ec17a9f8-0a5b-4d93-ca9c-a3755ff027ec@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 \
--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
all inboxes | Powered by JetHome®