diff options
author | Aaron Durbin <adurbin@chromium.org> | 2013-07-24 16:02:14 -0500 |
---|---|---|
committer | Patrick Georgi <patrick@georgi-clan.de> | 2013-12-21 10:49:11 +0100 |
commit | c422002b5f819de97d12dfec16cc55488f28642e (patch) | |
tree | 94bcdb8acb9a3ca42ec6049de023ca1f8e0dcf18 /util/kconfig/kconfig_load.c | |
parent | 980180962a1855220de08779fa4697c78757614a (diff) |
tpm: provide explicit tpm register access
An issue was observed using a specific vendor's TPM in that it
chokes on access to registers that are not explicitly defined in the
PC client specification. The previous driver used generic access
functions for reading and writing registers. However, issues come
to play when reading from the status register. It read it as a 32-bit
value, but that read address 0x1b which is not defined in the spec.
Instead of using generic access functions for the tpm registers
provide explicit ones. To that end provide more high level wrapper
functions to perform the semantic access required.
Change-Id: I781b31723f819e1387d7aa25512c83780ea0877f
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/63243
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: http://review.coreboot.org/4388
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <patrick@georgi-clan.de>
Diffstat (limited to 'util/kconfig/kconfig_load.c')
0 files changed, 0 insertions, 0 deletions