tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <jejb@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
	"Christophe Ricard" <christophe.ricard@gmail.com>,
	linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
	"Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com>,
	apronin@chromium.org
Subject: Re: [tpmdd-devel] tpm: read burstcount from TPM_STS in one 32-bit transaction
Date: Tue, 25 Jul 2017 10:36:11 -0700	[thread overview]
Message-ID: <1501004171.3689.25.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170725150443.7cf8fc91@kitsune.suse.cz>

On Tue, 2017-07-25 at 15:04 +0200, Michal Suchánek wrote:
> Hello,
> 
> in commit 9754d45e9970 ("tpm: read burstcount from TPM_STS in one
> 32-bit transaction") you change reading of two 8-bit values to one
> 32bit read. This is obviously wrong wrt endianess unless the
> underlying tpm_tis_read32 does endian conversion. 

Some of the bus read primitives do do endianness conversions.  The
problem is with the SPI attachment, which has unclear endianness.  A
standard PCI bus attachment uses ioread32() which automatically
transforms from a little endian bus to the cpu endianness, however SPI
is forced to transfer the bytes one at a time over the serial bus and
then transform.  The assumption seems to be that the TIS TPM is
replying in little endian format when SPI connected.

We can probably get the PPC people to confirm this, I believe they have
a SPI attached TPM.

James

  reply	other threads:[~2017-07-25 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 13:04 tpm: read burstcount from TPM_STS in one 32-bit transaction Michal Suchánek
2017-07-25 17:36 ` James Bottomley [this message]
2017-07-25 18:17   ` [tpmdd-devel] " Michal Suchánek
     [not found]     ` <20170725201758.230de968-6hIufAJW0g4CVLCxKZUutA@public.gmane.org>
2017-08-01 13:31       ` Jarkko Sakkinen
     [not found]   ` <1501004171.3689.25.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-08-01 15:59     ` George Wilson

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=1501004171.3689.25.camel@linux.vnet.ibm.com \
    --to=jejb@linux.vnet.ibm.com \
    --cc=apronin@chromium.org \
    --cc=christophe.ricard@gmail.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --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).