There were a few problem here:
- TPM2_Shutdown results in a response that we need to either process or ignore, otherwise any tpm20_write or tpm20_harvest call will trivially hang on an sc->pending_data_length != 0
- We should have a matching TPM2_Startup upon resume to restore any state that should have persisted
- We must drain the harvest task before we suspend to avoid problems there
Fixes: 3deb21f1afd5 ("random: TPM_HARVEST should have been [...]")
Co-authored-by: markj (D53835)