On Fri, May 04, 2018 at 08:00:22AM -0500, David R. Bild wrote: > Normally the system platform (i.e., BIOS/UEFI for x86) is responsible > for performing initialization of the TPM. For these modules, the host > kernel is the platform, so we perform the initialization in the driver > before registering the TPM with the kernel TPM subsystem. > > The initialization consists of issuing the TPM startup command, > running the TPM self-test, and setting the TPM platform hierarchy > authorization to a random, unsaved value so that it can never be used > after the driver has loaded. The tpm driver already does most of this stuff automatically, why duplicate it there and why is it coded in a way that doesn't use the existing TPM services to do it? Make no sense to me. Jason
