From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Laurent Bigonville <bigon@debian.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Alexander.Steffen@infineon.com, linux-integrity@vger.kernel.org
Subject: Re: [tpmdd-devel] tpm device not showing up in /dev anymore
Date: Sat, 11 Nov 2017 08:45:16 -0700 [thread overview]
Message-ID: <20171111154516.GI17451@ziepe.ca> (raw)
In-Reply-To: <20171110205300.eyfkoyabobv7llgb@localhost.localdomain>
On Fri, Nov 10, 2017 at 01:53:00PM -0700, Jerry Snitselaar wrote:
> I wonder if it is possible that the release locality from the probe
> isn't completing on the chip until after the request/check that
> happens at the beginning of the tpm_get_timeouts. Perhaps we need
> something like wait_for_tpm_stat for the access register, and
> verifying that locality was released before returning out of
> release_locality?
This is not a bad guess.. Adding a largish delay after
release_locality might be interesting too.
Are we sure our tis request/release process is even right? Another
options is that the 'check if already in locality' doesn't work on
this chip, or isn't coded right...
Jason
next prev parent reply other threads:[~2017-11-11 15:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f9526f55-df96-64fc-a4d6-877ce04e7156@debian.org>
[not found] ` <dcad0104c46d4d5f88e642862bdb42c2@MUCSE603.infineon.com>
[not found] ` <47c4300b-8701-79a6-1c58-3a5853f4c5e3@debian.org>
[not found] ` <595efb25-8d87-f39d-037f-9c9a98462339@debian.org>
[not found] ` <857106e4bb864bb8a68b1381fffc8f50@MUCSE603.infineon.com>
[not found] ` <20170831164015.3ajgwydgxtippwoz@rhwork>
[not found] ` <0d9be244-ace0-030d-6ff9-c4e94c63b7e9@debian.org>
[not found] ` <20170906040555.fqedhmo5277sd6fq@linux.intel.com>
2017-10-14 8:13 ` [tpmdd-devel] tpm device not showing up in /dev anymore Jerry Snitselaar
2017-10-21 8:53 ` Laurent Bigonville
2017-10-23 13:23 ` Jarkko Sakkinen
2017-10-23 13:45 ` Jerry Snitselaar
2017-10-23 13:48 ` Laurent Bigonville
2017-10-24 13:51 ` Jarkko Sakkinen
2017-10-24 14:57 ` Jerry Snitselaar
2017-10-24 16:07 ` Jarkko Sakkinen
2017-11-09 0:04 ` Laurent Bigonville
2017-11-09 19:58 ` Laurent Bigonville
2017-11-09 23:50 ` Jerry Snitselaar
2017-11-10 2:19 ` Jerry Snitselaar
2017-11-10 0:28 ` Jerry Snitselaar
2017-11-10 7:07 ` Jerry Snitselaar
2017-11-10 8:21 ` Laurent Bigonville
2017-11-10 20:53 ` Jerry Snitselaar
2017-11-11 15:45 ` Jason Gunthorpe [this message]
2017-11-11 19:12 ` Jerry Snitselaar
2017-11-11 19:46 ` Jason Gunthorpe
2017-11-11 20:31 ` Jerry Snitselaar
2017-11-14 0:26 ` Laurent Bigonville
2017-11-14 2:45 ` Jason Gunthorpe
2017-11-14 14:59 ` Jarkko Sakkinen
2017-11-14 15:17 ` James Bottomley
2017-11-17 13:16 ` Jarkko Sakkinen
2018-01-02 23:54 ` Laurent Bigonville
2018-01-03 0:33 ` Jerry Snitselaar
2018-01-05 19:01 ` Laurent Bigonville
2018-02-09 10:53 ` Laurent Bigonville
2018-02-14 11:44 ` Jarkko Sakkinen
2018-03-09 17:24 ` Laurent Bigonville
2018-03-15 16:24 ` Jarkko Sakkinen
2018-05-03 11:38 ` Laurent Bigonville
2018-05-03 17:43 ` Jerry Snitselaar
2018-05-04 8:20 ` Jarkko Sakkinen
2018-05-04 8:18 ` Jarkko Sakkinen
2018-05-04 14:22 ` Jerry Snitselaar
2017-11-14 14:55 ` Jarkko Sakkinen
2017-11-14 14:43 ` Jarkko Sakkinen
2017-10-25 8:04 ` Laurent Bigonville
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=20171111154516.GI17451@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Alexander.Steffen@infineon.com \
--cc=bigon@debian.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@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