[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160720195422.GA30947@obsidianresearch.com>
Date: Wed, 20 Jul 2016 13:54:22 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Andrey Pronin <apronin@...omium.org>
Cc: Rob Herring <robh@...nel.org>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Peter Huewe <peterhuewe@....de>,
Marcel Selhorst <tpmdd@...horst.net>,
tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
Christophe Ricard <christophe.ricard@...il.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 1/2] tpm: devicetree: document properties for cr50
On Wed, Jul 20, 2016 at 12:49:12PM -0700, Andrey Pronin wrote:
> Sorry, I just updated this patch description in v2 to indicate why they are not
> hard-coded, but didn't answer explicitly. As the firmware changes, a different
> revision of it can have a different time before it sleeps in its configuration,
> or the time it takes it to startup may be different. Thus, there's a way to
> set it here w/o changing the driver.
This sort of stuff should be read out of the firmware, not DT..
Why has Google created such a non-standard TPM firmware???
Jason
Powered by blists - more mailing lists