From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Peter Huewe <peter.huewe@infineon.com>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
peterhuewe@gmx.de, Christophe Ricard <christophe-h.ricard@st.com>
Subject: Re: [PATCH 0/5] Fix whole native SPI TPM driver
Date: Wed, 22 Feb 2017 23:19:24 +0200 [thread overview]
Message-ID: <20170222211924.zdikc5qfzuxiggte@intel.com> (raw)
In-Reply-To: <1487261306-2494-1-git-send-email-peter.huewe@infineon.com>
On Thu, Feb 16, 2017 at 04:08:21PM +0000, Peter Huewe wrote:
> During our testing it showed that unfortunately the whole native spi tpm driver
> was more or less non-functional since it was merged, e.g. the wrong byte for
> waitstate handling was used and transfers larger than 64 bytes did not work at all.
>
> This was probably caused by the merging of the different approaches back then,
> as the initial RFC patch did not have these problems, and also my sudden lack
> of time/commitment back then.
> I'm sorry that the final driver code went untested for that long time.
>
> This patch set fixes these issues one by one.
> In order to avoid duplication the read/write function was consolidated to one
> transfer function, so we do not have to apply the same fix at two locations.
> Maybe consider squashing it - we splitted it for easier review.
>
> Affected Kernels: 4.8, 4.9, 4.10
> Patchset was tested on Raspberry Pi2 with SLB9670 (TPM1.2 and TPM2.0)
>
> Peter Huewe (5):
> tpm_tis_spi: Use single function to transfer data
> tpm_tis_spi: Abort transfer when too many wait states are signaled
> tpm_tis_spi: Check correct byte for wait state indicator
> tpm_tis_spi: Remove limitation of transfers to MAX_SPI_FRAMESIZE bytes
> tpm_tis_spi: Add small delay after last transfer
>
> drivers/char/tpm/tpm_tis_spi.c | 163 +++++++++++++++++------------------------
> 1 file changed, 69 insertions(+), 94 deletions(-)
>
> --
> 2.7.4
>
I also found type errors a whilea ago:
https://patchwork.kernel.org/patch/9547993/
Do this take care of these issues?
/JArkko
next prev parent reply other threads:[~2017-02-22 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 16:08 [PATCH 0/5] Fix whole native SPI TPM driver Peter Huewe
2017-02-16 16:08 ` [PATCH 1/5] tpm_tis_spi: Use single function to transfer data Peter Huewe
2017-02-24 12:54 ` Jarkko Sakkinen
2017-02-16 16:08 ` [PATCH 2/5] tpm_tis_spi: Abort transfer when too many wait states are signaled Peter Huewe
2017-02-17 5:04 ` Christophe Ricard
2017-02-24 12:55 ` Jarkko Sakkinen
2017-02-16 16:08 ` [PATCH 3/5] tpm_tis_spi: Check correct byte for wait state indicator Peter Huewe
2017-02-17 5:09 ` Christophe Ricard
2017-02-17 7:15 ` Peter Huewe
2017-02-24 12:57 ` Jarkko Sakkinen
2017-02-16 16:08 ` [PATCH 4/5] tpm_tis_spi: Remove limitation of transfers to MAX_SPI_FRAMESIZE bytes Peter Huewe
2017-02-16 17:27 ` kbuild test robot
2017-02-17 5:11 ` Christophe Ricard
2017-02-17 7:19 ` Peter Huewe
2017-02-24 11:55 ` Jarkko Sakkinen
2017-02-24 12:59 ` Jarkko Sakkinen
2017-02-22 21:19 ` Jarkko Sakkinen [this message]
2017-02-22 22:32 ` [PATCH 0/5] Fix whole native SPI TPM driver Peter Huewe
2017-02-24 15:15 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170222211924.zdikc5qfzuxiggte@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=christophe-h.ricard@st.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.huewe@infineon.com \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox