public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Yoder <key@linux.vnet.ibm.com>
To: Peter Huewe <peter.huewe@infineon.com>
Cc: srajiv@linux.vnet.ibm.com, tpmdd@selhorst.net,
	tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Olof Johansson <olof@lixom.net>,
	Luigi Semenzato <semenzato@google.com>,
	andi.shyti@gmail.com, Bryan Freed <bfreed@chromium.org>
Subject: Re: [PATCH 2/2] CHROMIUM: tpm: tpm_i2c_infineon: Lock the I2C adapter for a sequence of requests.
Date: Wed, 11 Jul 2012 10:19:18 -0500	[thread overview]
Message-ID: <20120711151918.GB21153@linux.vnet.ibm.com> (raw)
In-Reply-To: <1339505034-6400-2-git-send-email-peter.huewe@infineon.com>

Hi Peter / Bryan,

On Tue, Jun 12, 2012 at 02:43:54PM +0200, Peter Huewe wrote:
> From: Bryan Freed <bfreed@chromium.org>
> 
> This is derived from Peter Huewe's recommended fix:
> 
> On some ChromeOS systems, a TPM sharing the I2C bus with another device
> gets confused when it sees I2C requests to that other device.
> This change locks the I2C adapter for the duration of the full sequence
> of I2C requests the TPM needs to complete.
> 
> smbus_xfer is not supported, but SMBUS is not supported by the original
> driver, either.
> 
> Signed-off-by: Bryan Freed <bfreed@chromium.org>
> Signed-off-by: Peter Huewe <peter.huewe@infineon.com>

  I've applied this patch to my tpmdd staging tree [1].

Thanks,
Kent

[1] git://github.com/shpedoikal/linux.git tpmdd-next


  parent reply	other threads:[~2012-07-11 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:43 [PATCH 1/2] char/tpm: Add new driver for Infineon I2C TIS TPM Peter Huewe
2012-06-12 12:43 ` [PATCH 2/2] CHROMIUM: tpm: tpm_i2c_infineon: Lock the I2C adapter for a sequence of requests Peter Huewe
2012-06-13  7:38   ` Marcel Selhorst
2012-07-11 15:19   ` Kent Yoder [this message]
2012-06-13  7:37 ` [PATCH 1/2] char/tpm: Add new driver for Infineon I2C TIS TPM Marcel Selhorst
2012-06-13  8:02   ` Olof Johansson
2012-06-13 13:19     ` Rajiv Andrade
2012-06-13 17:04     ` Marcel Selhorst
2012-07-10 15:14       ` Kent Yoder
2012-06-13  8:35 ` Andi
2012-07-11 15:16 ` Kent Yoder
2012-07-11 15:21   ` [tpmdd-devel] " Peter.Huewe

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=20120711151918.GB21153@linux.vnet.ibm.com \
    --to=key@linux.vnet.ibm.com \
    --cc=andi.shyti@gmail.com \
    --cc=bfreed@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=peter.huewe@infineon.com \
    --cc=semenzato@google.com \
    --cc=srajiv@linux.vnet.ibm.com \
    --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