All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: Nayna Jain <nayna@linux.vnet.ibm.com>,
	pau@linux.vnet.ibm.com, linux-integrity@vger.kernel.org
Subject: Re: Aw: Re:  tpm_tis_spi gets initialized long after IMA
Date: Fri, 29 Sep 2017 07:40:08 -0400	[thread overview]
Message-ID: <1506685208.5691.109.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <trinity-868e9e34-679a-4aff-97a3-9edf65a2fcda-1506673263842@3c-app-gmx-bs15>

On Fri, 2017-09-29 at 10:21 +0200, Peter Huewe wrote:
> Hi Mimi,
> 
> On Thu, 2017-09-28 at 23:36 +0200, Peter Huewe wrote:
> >> Okay,
> >> first error - CONFIG_SPI_BCM2835 has to be compiled in.
> >> That explains the 2.5 sec.
> 
> > Last December we were able to initialize the TPM before IMA.   It
> > required commit 29c7854 - "Register the clocks early during the boot
> > process, so that special/critical clocks can get enabled early
> > on in the boot process avoiding the risk of disabling a clock,
> > pll_divider or pll when a claiming driver fails to install
> > propperly - maybe it needs to defer."
> 
> > We built a custom kernel with both commit 29c7854 and building in
> > BCM2835_SPI (thanks Nayna).
> 
> To which tree is the commit id related to?
> i.e. where can I find the patch?

The patch replaces the call to builtin_platform_driver(), with a call
to core_initcall().

https://github.com/raspberrypi/linux/blob/rpi-4.8.y/drivers/clk/bcm/cl
k-bcm2835.c

static int __init __bcm2835_clk_driver_init(void)
{
	return platform_driver_register(&bcm2835_clk_driver);
}
core_initcall(__bcm2835_clk_driver_init);


Mimi

  reply	other threads:[~2017-09-29 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 21:18 tpm_tis_spi gets initialized long after IMA Peter Huewe
2017-09-28 21:36 ` Aw: " Peter Huewe
2017-09-29  1:09   ` Mimi Zohar
2017-09-29  8:21     ` Aw: " Peter Huewe
2017-09-29 11:40       ` Mimi Zohar [this message]
2017-09-29 18:44         ` Aw: " Peter Huewe
2017-09-29 19:49           ` pau
2017-09-29 20:14             ` Aw: " Peter Huewe
2017-12-15 13:26               ` Mimi Zohar
2017-12-21 13:59                 ` Mimi Zohar

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=1506685208.5691.109.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=PeterHuewe@gmx.de \
    --cc=linux-integrity@vger.kernel.org \
    --cc=nayna@linux.vnet.ibm.com \
    --cc=pau@linux.vnet.ibm.com \
    /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.