16 Jan, 2019

1 commit


30 Nov, 2018

1 commit

  • At present many TPM calls assume there is only one TPM in the system and
    look up this TPM themselves. This is inconsistent with driver model, which
    expects all driver methods to have a device parameter. Update the code to
    correct this.

    Signed-off-by: Simon Glass

    Simon Glass
     

28 Jul, 2018

1 commit

  • While there is probably no reason to do so in a real life situation, it
    will allow to compile test both stacks with the same sandbox defconfig.

    As we cannot define two 'tpm' commands at the same time, the command for
    TPM v1 is still called 'tpm' and the one for TPM v2 'tpm2'. While this
    is the exact command name that must be written into eg. test files, any
    user already using the TPM v2 stack can continue to do so by just writing
    'tpm' because as long as TPM v1 support is not compiled, U-Boot prompt
    will search for the closest command named after 'tpm'.

    The command set can also be changed at runtime (not supported yet, but
    ready to be), but as one can compile only either one stack or the other,
    there is still one spot in the code where conditionals are used: to
    retrieve the v1 or v2 command set.

    Signed-off-by: Miquel Raynal
    Reviewed-by: Simon Glass
    [trini: In sandbox_tpm2_fill_buf() use NULL not \0 to ensure NULL
    terminated string due to LLVM warning]
    Signed-off-by: Tom Rini

    Miquel Raynal
     

26 May, 2018

10 commits