From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Dmitry Torokhov <dtor@chromium.org>
Cc: Andrey Pronin <apronin@chromium.org>,
Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Christophe Ricard <christophe.ricard@gmail.com>,
smbarber@chromium.org, dianders@chromium.org
Subject: Re: [PATCH v3 2/2] tpm_tis_spi: add max xfer size
Date: Tue, 9 Aug 2016 11:14:40 +0300 [thread overview]
Message-ID: <20160809081439.GB10537@intel.com> (raw)
In-Reply-To: <20160728225316.GB28623@dtor-ws>
On Thu, Jul 28, 2016 at 03:53:16PM -0700, Dmitry Torokhov wrote:
> On Wed, Jul 27, 2016 at 08:49:57PM -0700, Andrey Pronin wrote:
> > Reject burstcounts larger than 64 bytes reported by tpm.
> > SPI Hardware Protocol defined in section 6.4 of TCG PTP
> > Spec supports up to 64 bytes of data in a transaction.
> >
> > Signed-off-by: Andrey Pronin <apronin@chromium.org>
>
> Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
> > ---
> > drivers/char/tpm/tpm_tis_spi.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/char/tpm/tpm_tis_spi.c b/drivers/char/tpm/tpm_tis_spi.c
> > index dbaad9c..b103373 100644
> > --- a/drivers/char/tpm/tpm_tis_spi.c
> > +++ b/drivers/char/tpm/tpm_tis_spi.c
> > @@ -206,6 +206,7 @@ static const struct tpm_tis_phy_ops tpm_spi_phy_ops = {
> > .read16 = tpm_tis_spi_read16,
> > .read32 = tpm_tis_spi_read32,
> > .write32 = tpm_tis_spi_write32,
> > + .max_xfer_size = MAX_SPI_FRAMESIZE,
> > };
> >
> > static int tpm_tis_spi_probe(struct spi_device *dev)
> > --
> > 2.6.6
> >
>
> --
> Dmitry
prev parent reply other threads:[~2016-08-09 8:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:39 [PATCH 0/2] tpm: add optional max xfer size check Andrey Pronin
2016-07-15 1:39 ` [PATCH 1/2] tpm_tis_core: " Andrey Pronin
2016-07-15 3:13 ` Jason Gunthorpe
2016-07-15 3:25 ` Andrey Pronin
2016-07-15 3:48 ` Guenter Roeck
2016-07-18 18:53 ` Jarkko Sakkinen
2016-07-15 1:39 ` [PATCH 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 0/2] tpm: add optional max xfer size check Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 1/2] tpm_tis_core: " Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-20 15:10 ` [PATCH v2 0/2] tpm: add optional max xfer size check Jarkko Sakkinen
2016-07-28 3:49 ` [PATCH v3 " Andrey Pronin
2016-07-28 3:49 ` [PATCH v3 1/2] tpm_tis_core: " Andrey Pronin
2016-07-28 22:52 ` Dmitry Torokhov
2016-08-09 8:14 ` Jarkko Sakkinen
2016-07-28 3:49 ` [PATCH v3 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-28 22:53 ` Dmitry Torokhov
2016-08-09 8:14 ` Jarkko Sakkinen [this message]
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=20160809081439.GB10537@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=apronin@chromium.org \
--cc=christophe.ricard@gmail.com \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=smbarber@chromium.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.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;
as well as URLs for NNTP newsgroup(s).