From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
open list <linux-kernel@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>
Subject: Re: [tpmdd-devel] [PATCH v3 1/3] tpm_crb: map locality registers
Date: Mon, 12 Dec 2016 17:32:02 +0200 [thread overview]
Message-ID: <20161212153202.d2ky3b5jsgaiacpi@intel.com> (raw)
In-Reply-To: <20161212153108.mc5xf72npprz7wpe@intel.com>
On Mon, Dec 12, 2016 at 05:31:08PM +0200, Jarkko Sakkinen wrote:
> On Mon, Dec 12, 2016 at 05:20:01PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Dec 12, 2016 at 02:25:32PM +0000, Winkler, Tomas wrote:
> > > >
> > > > In order to provide access to locality registers, this commits adds mapping of
> > > > the head of the CRB registers, which are located right before the control area.
> > > >
> > > > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > > > ---
> > > > drivers/char/tpm/tpm_crb.c | 89 +++++++++++++++++++++++++++++------------
> > > > -----
> > > > 1 file changed, 57 insertions(+), 32 deletions(-)
> > > >
> > > > diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c index
> > > > 717b6b4..80b9759 100644
> > > > --- a/drivers/char/tpm/tpm_crb.c
> > > > +++ b/drivers/char/tpm/tpm_crb.c
> > > > @@ -52,18 +52,28 @@ enum crb_cancel {
> > > > CRB_CANCEL_INVOKE = BIT(0),
> > > > };
> > > >
> > > > -struct crb_control_area {
> > > > - u32 req;
> > > > - u32 sts;
> > > > - u32 cancel;
> > > > - u32 start;
> > > > - u32 int_enable;
> > > > - u32 int_sts;
> > > > - u32 cmd_size;
> > > > - u32 cmd_pa_low;
> > > > - u32 cmd_pa_high;
> > > > - u32 rsp_size;
> > > > - u64 rsp_pa;
> > > > +struct crb_regs_head {
> > > > + u32 loc_state;
> > > > + u32 reserved1;
> > > > + u32 loc_ctrl;
> > > > + u32 loc_sts;
> > > > + u8 reserved2[32];
> > > > + u64 intf_id;
> > > > + u64 ctrl_ext;
> > > > +} __packed;
> > > > +
> > >
> > > > +struct crb_regs_tail {
> > > Why to change the name this is still control_area
>
> And how would you name struct crb_regs_h then?
>
> In my opinion PC it makes a lot of sense to speak about registers here
~~
Typo.
/Jarkko
next prev parent reply other threads:[~2016-12-12 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 11:49 [PATCH v3 0/3] Locality support for tpm_crb Jarkko Sakkinen
[not found] ` <20161207115001.18332-1-jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-12-07 11:49 ` [PATCH v3 1/3] tpm_crb: map locality registers Jarkko Sakkinen
2016-12-12 14:25 ` [tpmdd-devel] " Winkler, Tomas
2016-12-12 15:20 ` Jarkko Sakkinen
2016-12-12 15:28 ` Winkler, Tomas
2016-12-12 17:46 ` Jarkko Sakkinen
2016-12-12 15:31 ` Jarkko Sakkinen
2016-12-12 15:32 ` Jarkko Sakkinen [this message]
2016-12-12 15:57 ` Winkler, Tomas
2016-12-12 17:53 ` Jarkko Sakkinen
2016-12-12 17:59 ` Jarkko Sakkinen
2016-12-07 11:49 ` [PATCH v3 2/3] tpm_crb: encapsulate crb_wait_for_reg_32 Jarkko Sakkinen
2016-12-07 11:50 ` [PATCH v3 3/3] tpm_crb: request and relinquish locality 0 Jarkko Sakkinen
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=20161212153202.d2ky3b5jsgaiacpi@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tomas.winkler@intel.com \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).