From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: [PATCH v3 2/2] tpm_tis_spi: add max xfer size Date: Tue, 9 Aug 2016 11:14:40 +0300 Message-ID: <20160809081439.GB10537@intel.com> References: <1468546745-14646-1-git-send-email-apronin@chromium.org> <1469677797-74304-3-git-send-email-apronin@chromium.org> <20160728225316.GB28623@dtor-ws> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20160728225316.GB28623@dtor-ws> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tpmdd-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Dmitry Torokhov Cc: Christophe Ricard , dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: tpmdd-devel@lists.sourceforge.net 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 > > Reviewed-by: Dmitry Torokhov Reviewed-by: Jarkko Sakkinen /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 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev