[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f3ff613761f345859d131e96bcd037ff@huawei.com>
Date: Tue, 14 Jan 2020 12:31:37 +0000
From: wanghongzhe <wanghongzhe@...wei.com>
To: "peterhuewe@....de" <peterhuewe@....de>
CC: "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Zhangchenfeng (EulerOS)" <zhangchenfeng1@...wei.com>
Subject: [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout
when i reach TPM_RETRY, the cs cannot change back to 'high'.So the TPM chips thinks this communication is not over.
And next times communication cannot be effective because the communications mixed up with the last time.
Signed-off-by: Wang Hongzhe <wanghongzhe@...wei.com>
---
drivers/char/tpm/tpm_tis_spi.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/char/tpm/tpm_tis_spi.c b/drivers/char/tpm/tpm_tis_spi.c index d1754fd..a1ae4f6 100644
--- a/drivers/char/tpm/tpm_tis_spi.c
+++ b/drivers/char/tpm/tpm_tis_spi.c
@@ -67,7 +67,14 @@ static int tpm_tis_spi_flow_control(struct tpm_tis_spi_phy *phy,
}
if (i == TPM_RETRY)
+ {
+ spi_xfer.cs_change = 0;
+ spi_xfer->len = 1;
+ spi_message_init(&m);
+ spi_message_add_tail(spi_xfer, &m);
+ ret = spi_sync_locked(phy->spi_device, &m);
return -ETIMEDOUT;
+ }
}
return 0;
--
1.7.12.4
Powered by blists - more mailing lists