public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kent Yoder <shpedoikal@gmail.com>
Cc: Duncan Laurie <dlaurie@chromium.org>,
	Dirk Hohndel <dirk@hohndel.org>,
	Kent Yoder <key@linux.vnet.ibm.com>,
	Luigi Semenzato <semenzato@chromium.org>,
	TPM Device Driver List <tpmdd-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] TPM: Retry SaveState command in suspend path
Date: Wed, 17 Apr 2013 09:18:48 -0700	[thread overview]
Message-ID: <20130417161848.GA8752@kroah.com> (raw)
In-Reply-To: <CAM0nabG_iOcThp-9QvupWEi38q0y9Zg7pOpdmue6X7yEw7FRfw@mail.gmail.com>

On Wed, Apr 17, 2013 at 09:54:24AM -0500, Kent Yoder wrote:
> On Tue, Apr 16, 2013 at 6:57 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Mar 19, 2013 at 10:00:02AM -0500, Kent Yoder wrote:
> >> Hi Duncan,
> >>
> >> On Sun, Mar 17, 2013 at 4:56 PM, Duncan Laurie <dlaurie@chromium.org> wrote:
> >> > If the TPM has already been sent a SaveState command before the driver
> >> > is loaded it may have problems sending that same command again later.
> >> >
> >> > This issue is seen with the Chromebook Pixel due to a firmware bug in
> >> > the legacy mode boot path which is sending the SaveState command
> >> > before booting the kernel.  More information is available at
> >> > http://crbug.com/203524
> >> >
> >> > This change introduces a retry of the SaveState command in the suspend
> >> > path in order to work around this issue.  A future firmware update
> >> > should fix this but this is also a trivial workaround in the driver
> >> > that has no effect on systems that do not show this problem.
> >>
> >>   I'm not convinced that this needs to be upstream.  The simplest
> >> route would seem to be to carry this out of tree until your firmware
> >> is fixed.
> >
> > Really?  We have machines that we are using right now that need this fix
> > in order to work properly.
> >
> > The kernel handles buggy firmware/bioses all the time, we need to work
> > properly on all hardware, we can't count on a firmware update ever
> > getting pushed out publically, and for those of us using this hardware,
> > we want it to work.
> 
>   That makes sense -- on first read I thought this was an issue with
> Chrome OS only.  I see now this is an issue with reinstalling other
> OS's over Chrome.  I've staged this over here:
> 
> git://github.com/shpedoikal/linux.git tpmdd-04-17-13
> 
> and I'll push this to James later today.

Thank you very much, it's appreciated.  I'll watch out for it to hit
Linus's tree and add it to the -stable releases as well.

greg k-h

      reply	other threads:[~2013-04-17 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 21:56 [PATCH] TPM: Retry SaveState command in suspend path Duncan Laurie
2013-03-18  8:56 ` [tpmdd-devel] " Peter.Huewe
2013-03-19 15:00 ` Kent Yoder
2013-04-16 23:57   ` Greg KH
2013-04-17 14:54     ` Kent Yoder
2013-04-17 16:18       ` Greg KH [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=20130417161848.GA8752@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dirk@hohndel.org \
    --cc=dlaurie@chromium.org \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=semenzato@chromium.org \
    --cc=shpedoikal@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --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