All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	jarkko@kernel.org, Peter Huewe <peterhuewe@gmx.de>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Hans de Goede <hdegoede@redhat.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] tpm_tis: Disable interrupts on ThinkPad T490s
Date: Mon, 19 Oct 2020 00:14:28 +0300	[thread overview]
Message-ID: <20201018211428.GD575510@kapsi.fi> (raw)
In-Reply-To: <20201018211143.GC575510@kapsi.fi>

On Mon, Oct 19, 2020 at 12:11:44AM +0300, Jarkko Sakkinen wrote:
> On Thu, Oct 15, 2020 at 02:44:30PM -0700, Jerry Snitselaar wrote:
> > There is a misconfiguration in the bios of the gpio pin used for the
> > interrupt in the T490s. When interrupts are enabled in the tpm_tis
> > driver code this results in an interrupt storm. This was initially
> > reported when we attempted to enable the interrupt code in the tpm_tis
> > driver, which previously wasn't setting a flag to enable it. Due to
> > the reports of the interrupt storm that code was reverted and we went back
> > to polling instead of using interrupts. Now that we know the T490s problem
> > is a firmware issue, add code to check if the system is a T490s and
> > disable interrupts if that is the case. This will allow us to enable
> > interrupts for everyone else. If the user has a fixed bios they can
> > force the enabling of interrupts with tpm_tis.interrupts=1 on the
> > kernel command line.
> > 
> > Cc: jarkko@kernel.org
> > Cc: Peter Huewe <peterhuewe@gmx.de>
> > Cc: Jason Gunthorpe <jgg@ziepe.ca>
> > Cc: Hans de Goede <hdegoede@redhat.com>
> > Reviewed-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> > Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> 
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> 
> I'll apply this and make it available in linux-next.

Applied.

Thank you.

/Jarkko

      reply	other threads:[~2020-10-18 21:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 21:44 [PATCH] tpm_tis: Disable interrupts on ThinkPad T490s Jerry Snitselaar
2020-10-15 22:01 ` Jerry Snitselaar
2020-10-15 22:39 ` Matthew Garrett
2020-10-16  6:12   ` Hans de Goede
2020-11-19  6:36   ` Jerry Snitselaar
2020-11-19 14:42     ` Hans de Goede
2020-11-19 17:05       ` Jerry Snitselaar
2020-11-23 12:19         ` Hans de Goede
2020-11-24  3:27       ` Jarkko Sakkinen
2020-11-24  3:29         ` Jarkko Sakkinen
2020-11-24  3:26     ` Jarkko Sakkinen
2020-11-24 17:52       ` Jerry Snitselaar
2020-11-24 18:10         ` James Bottomley
2020-11-29  3:21           ` Jarkko Sakkinen
2020-11-24 21:45         ` Hans de Goede
2020-11-29  3:23           ` Jarkko Sakkinen
2020-11-29 11:34             ` Hans de Goede
2020-12-02 16:07               ` Jarkko Sakkinen
2020-11-29  3:18         ` Jarkko Sakkinen
2020-10-16  6:10 ` Hans de Goede
2020-10-18 21:11 ` Jarkko Sakkinen
2020-10-18 21: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=20201018211428.GD575510@kapsi.fi \
    --to=jarkko.sakkinen@iki.fi \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hdegoede@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.