From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: apronin@chromium.org
Cc: Christophe Ricard <christophe.ricard@gmail.com>,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org, leendert@watson.ibm.com
Subject: Re: [tpmdd-devel] [RESEND][PATCH] tpm: read burstcount from TPM_STS in one 32-bit transaction
Date: Tue, 19 Jul 2016 17:41:39 +0300 [thread overview]
Message-ID: <20160719144139.GB14878@intel.com> (raw)
In-Reply-To: <20160701084545.GA16059@intel.com>
On Fri, Jul 01, 2016 at 11:45:45AM +0300, Jarkko Sakkinen wrote:
> On Fri, Jul 01, 2016 at 11:43:23AM +0300, Jarkko Sakkinen wrote:
> > On Thu, Jun 30, 2016 at 10:25:43AM -0700, apronin@chromium.org wrote:
> > > From: Andrey Pronin <apronin@chromium.org>
> > >
> > > Some chips incorrectly support partial reads from TPM_STS register
> > > at non-zero offsets. Read the entire 32-bits register instead of
> > > making two 8-bit reads to support such devices and reduce the number
> > > of bus transactions when obtaining the burstcount from TPM_STS.
> > >
> > > Signed-off-by: Andrey Pronin <apronin@chromium.org>
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> Applied to my master branch.
I added also added a fixes line.
/Jarkko
prev parent reply other threads:[~2016-07-19 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 17:25 [RESEND][PATCH] tpm: read burstcount from TPM_STS in one 32-bit transaction apronin-F7+t8E8rja9g9hUCZPvPmw
2016-06-30 17:25 ` apronin
[not found] ` <1467307543-44566-1-git-send-email-apronin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-07-01 8:43 ` Jarkko Sakkinen
2016-07-01 8:43 ` Jarkko Sakkinen
[not found] ` <20160701084323.GA15718-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-01 8:45 ` Jarkko Sakkinen
2016-07-01 8:45 ` Jarkko Sakkinen
2016-07-19 14:41 ` Jarkko Sakkinen [this message]
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=20160719144139.GB14878@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=apronin@chromium.org \
--cc=christophe.ricard@gmail.com \
--cc=leendert@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.