mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	tpmdd-devel@lists.sourceforge.net,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>,
	Marcel Selhorst <tpmdd@selhorst.net>,
	Christophe Ricard <christophe.ricard@gmail.com>
Subject: Re: [PATCH] tpm_tis: override reported C and D timeouts for Atmel 3203
Date: Fri, 13 Jan 2017 17:50:45 +0200	[thread overview]
Message-ID: <20170113155045.ncqgiioezajgelhp@intel.com> (raw)
In-Reply-To: <20f8645d-f3fd-550b-b830-d1e55b8f2d17@maciej.szmigiero.name>

On Thu, Jan 12, 2017 at 10:37:31PM +0100, Maciej S. Szmigiero wrote:
> On 12.01.2017 21:20, Jarkko Sakkinen wrote:
> > On Thu, Jan 12, 2017 at 09:09:33PM +0100, Maciej S. Szmigiero wrote:
> >> Hi Jason,
> >>
> >> On 12.01.2017 19:42, Jason Gunthorpe wrote:
> (..)
> >>> Can you also add a check for 0 timeouts in the core code and print a
> >>> FW_BUG :\
> >>
> >> Hmm, I dug in history of tpm-interface.c and the code had actually rejected
> >> zero timeouts until commit 8e54caf407b98e (this is the commit that
> >> introduced the Atmel 3204 workaround) and let default timeout values remain
> >> instead (it looks like they were exactly like these in above override at
> >> that time).
> >>
> >> Did Atmel 3204 report wrong but non-zero timeouts?
> > 
> > Wouldn't it make more sense to fix this by re-adding this fallback?
> 
> I think it would be a cleaner fix and also catch other problematic
> devices (if there are any) without needing to add individual overrides.

Please go with that but add also FW_BUG print just to be aware of
chips that report zero values.

/Jarkko

      reply	other threads:[~2017-01-13 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 18:08 Maciej S. Szmigiero
2017-01-12 18:42 ` Jason Gunthorpe
2017-01-12 20:09   ` Maciej S. Szmigiero
2017-01-12 20:19     ` Jason Gunthorpe
2017-01-12 20:20     ` Jarkko Sakkinen
2017-01-12 21:37       ` Maciej S. Szmigiero
2017-01-13 15:50         ` 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=20170113155045.ncqgiioezajgelhp@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=christophe.ricard@gmail.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@maciej.szmigiero.name \
    --cc=peterhuewe@gmx.de \
    --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

all inboxes | Powered by JetHome®