30fc8d138e
tpm_crb is a driver for TPM 2.0 Command Response Buffer (CRB) Interface as defined in PC Client Platform TPM Profile (PTP) Specification. Only polling and single locality is supported as these are the limitations of the available hardware, Platform Trust Techonlogy (PTT) in Haswell CPUs. The driver always applies CRB with ACPI start because PTT reports using only ACPI start as start method but as a result of my testing it requires also CRB start. Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Reviewed-by: Jasob Gunthorpe <jason.gunthorpe@obsidianresearch.com> Reviewed-by: Stefan Berger <stefanb@linux.vnet.ibm.com> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
134 lines
4.8 KiB
Text
134 lines
4.8 KiB
Text
#
|
|
# TPM device configuration
|
|
#
|
|
|
|
menuconfig TCG_TPM
|
|
tristate "TPM Hardware Support"
|
|
depends on HAS_IOMEM
|
|
select SECURITYFS
|
|
---help---
|
|
If you have a TPM security chip in your system, which
|
|
implements the Trusted Computing Group's specification,
|
|
say Yes and it will be accessible from within Linux. For
|
|
more information see <http://www.trustedcomputinggroup.org>.
|
|
An implementation of the Trusted Software Stack (TSS), the
|
|
userspace enablement piece of the specification, can be
|
|
obtained at: <http://sourceforge.net/projects/trousers>. To
|
|
compile this driver as a module, choose M here; the module
|
|
will be called tpm. If unsure, say N.
|
|
Notes:
|
|
1) For more TPM drivers enable CONFIG_PNP, CONFIG_ACPI
|
|
and CONFIG_PNPACPI.
|
|
2) Without ACPI enabled, the BIOS event log won't be accessible,
|
|
which is required to validate the PCR 0-7 values.
|
|
|
|
if TCG_TPM
|
|
|
|
config TCG_TIS
|
|
tristate "TPM Interface Specification 1.2 Interface"
|
|
depends on X86
|
|
---help---
|
|
If you have a TPM security chip that is compliant with the
|
|
TCG TIS 1.2 TPM specification say Yes and it will be accessible
|
|
from within Linux. To compile this driver as a module, choose
|
|
M here; the module will be called tpm_tis.
|
|
|
|
config TCG_TIS_I2C_ATMEL
|
|
tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
|
|
depends on I2C
|
|
---help---
|
|
If you have an Atmel I2C TPM security chip say Yes and it will be
|
|
accessible from within Linux.
|
|
To compile this driver as a module, choose M here; the module will
|
|
be called tpm_tis_i2c_atmel.
|
|
|
|
config TCG_TIS_I2C_INFINEON
|
|
tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)"
|
|
depends on I2C
|
|
---help---
|
|
If you have a TPM security chip that is compliant with the
|
|
TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack
|
|
Specification 0.20 say Yes and it will be accessible from within
|
|
Linux.
|
|
To compile this driver as a module, choose M here; the module
|
|
will be called tpm_i2c_infineon.
|
|
|
|
config TCG_TIS_I2C_NUVOTON
|
|
tristate "TPM Interface Specification 1.2 Interface (I2C - Nuvoton)"
|
|
depends on I2C
|
|
---help---
|
|
If you have a TPM security chip with an I2C interface from
|
|
Nuvoton Technology Corp. say Yes and it will be accessible
|
|
from within Linux.
|
|
To compile this driver as a module, choose M here; the module
|
|
will be called tpm_i2c_nuvoton.
|
|
|
|
config TCG_NSC
|
|
tristate "National Semiconductor TPM Interface"
|
|
depends on X86
|
|
---help---
|
|
If you have a TPM security chip from National Semiconductor
|
|
say Yes and it will be accessible from within Linux. To
|
|
compile this driver as a module, choose M here; the module
|
|
will be called tpm_nsc.
|
|
|
|
config TCG_ATMEL
|
|
tristate "Atmel TPM Interface"
|
|
depends on PPC64 || HAS_IOPORT_MAP
|
|
---help---
|
|
If you have a TPM security chip from Atmel say Yes and it
|
|
will be accessible from within Linux. To compile this driver
|
|
as a module, choose M here; the module will be called tpm_atmel.
|
|
|
|
config TCG_INFINEON
|
|
tristate "Infineon Technologies TPM Interface"
|
|
depends on PNP
|
|
---help---
|
|
If you have a TPM security chip from Infineon Technologies
|
|
(either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it
|
|
will be accessible from within Linux.
|
|
To compile this driver as a module, choose M here; the module
|
|
will be called tpm_infineon.
|
|
Further information on this driver and the supported hardware
|
|
can be found at http://www.trust.rub.de/projects/linux-device-driver-infineon-tpm/
|
|
|
|
config TCG_IBMVTPM
|
|
tristate "IBM VTPM Interface"
|
|
depends on PPC_PSERIES
|
|
---help---
|
|
If you have IBM virtual TPM (VTPM) support say Yes and it
|
|
will be accessible from within Linux. To compile this driver
|
|
as a module, choose M here; the module will be called tpm_ibmvtpm.
|
|
|
|
config TCG_TIS_I2C_ST33
|
|
tristate "TPM Interface Specification 1.2 Interface (I2C - STMicroelectronics)"
|
|
depends on I2C
|
|
depends on GPIOLIB
|
|
---help---
|
|
If you have a TPM security chip from STMicroelectronics working with
|
|
an I2C bus say Yes and it will be accessible from within Linux.
|
|
To compile this driver as a module, choose M here; the module will be
|
|
called tpm_i2c_stm_st33.
|
|
|
|
config TCG_XEN
|
|
tristate "XEN TPM Interface"
|
|
depends on TCG_TPM && XEN
|
|
select XEN_XENBUS_FRONTEND
|
|
---help---
|
|
If you want to make TPM support available to a Xen user domain,
|
|
say Yes and it will be accessible from within Linux. See
|
|
the manpages for xl, xl.conf, and docs/misc/vtpm.txt in
|
|
the Xen source repository for more details.
|
|
To compile this driver as a module, choose M here; the module
|
|
will be called xen-tpmfront.
|
|
|
|
config TCG_CRB
|
|
tristate "TPM 2.0 CRB Interface"
|
|
depends on X86 && ACPI
|
|
---help---
|
|
If you have a TPM security chip that is compliant with the
|
|
TCG CRB 2.0 TPM specification say Yes and it will be accessible
|
|
from within Linux. To compile this driver as a module, choose
|
|
M here; the module will be called tpm_crb.
|
|
|
|
endif # TCG_TPM
|