From: Mimi Zohar <zohar@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Markku Savela" <msa@moth.iki.fi>,
linux-integrity <linux-integrity@vger.kernel.org>,
"Peter Hüwe" <PeterHuewe@gmx.de>
Subject: Re: IMA fails to see TPM chip (rpi3, linaro optee)
Date: Tue, 26 Feb 2019 14:05:11 -0500 [thread overview]
Message-ID: <1551207911.3946.9.camel@linux.ibm.com> (raw)
In-Reply-To: <20190226180913.GA22368@linux.intel.com>
On Tue, 2019-02-26 at 20:09 +0200, Jarkko Sakkinen wrote:
> On Tue, Feb 26, 2019 at 09:04:38AM -0500, Mimi Zohar wrote:
> > Hi Ard, thank you for responding. The clk not being initialized early
> > enough has been a problem for years. Because of the clk not being
> > initialized, the TPM initialization is deferred, causing IMA to go
> > into TPM-bypass mode.
>
> I'd guess this is an SPI issue and not really something that TPM could
> resolve? Please correct me if I'm wrong. I.e. SPI gets initialized after
> IMA.
>
Peter's original post with some debugging is here:
https://lore.kernel.org/linux-integrity/trinity-3e6c2430-417d-4eef-b067-e30d68592b4d-1506716047790@3c-app-gmx-bs69/
next prev parent reply other threads:[~2019-02-26 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:36 IMA fails to see TPM chip (rpi3, linaro optee) Markku Savela
2019-02-18 10:13 ` Markku Savela
2019-02-20 8:14 ` Markku Savela
2019-02-21 9:08 ` Markku Savela
2019-02-21 12:49 ` Mimi Zohar
2019-02-21 13:17 ` Markku Savela
2019-02-21 13:23 ` Markku Savela
2019-02-26 8:12 ` Markku Savela
2019-02-26 12:14 ` Mimi Zohar
2019-02-26 12:38 ` Ard Biesheuvel
2019-02-26 14:04 ` Mimi Zohar
2019-02-26 18:09 ` Jarkko Sakkinen
2019-02-26 19:05 ` Mimi Zohar [this message]
2019-03-07 17:15 ` James Bottomley
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=1551207911.3946.9.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=PeterHuewe@gmx.de \
--cc=ard.biesheuvel@linaro.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=msa@moth.iki.fi \
/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).