All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: debora@linux.vnet.ibm.com, m.selhorst@sirrix.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: Autodetect itpm devices
Date: Tue, 26 Oct 2010 11:14:40 -0200	[thread overview]
Message-ID: <4CC6D440.10604@linux.vnet.ibm.com> (raw)
In-Reply-To: <1287697360-31273-1-git-send-email-mjg@redhat.com>

On 21/10/10 19:42, Matthew Garrett wrote:
> Some Lenovos have TPMs that require a quirk to function correctly. This can
> be autodetected by checking whether the device has a _HID of INTC0102. This
> is an invalid PNPid, and as such is discarded by the pnp layer - however
> it's still present in the ACPI code, so we can pull it out that way. This
> means that the quirk won't be automatically applied on non-ACPI systems,
> but without ACPI we don't have any way to identify the chip anyway so I
> don't think that's a great concern.
>
> Signed-off-by: Matthew Garrett<mjg@redhat.com>
Thanks Matthew,

I'd be glad to remove the module option after this patch, but the 
non-ACPI case wouldn't
remain covered indeed.

Acked-by: Rajiv Andrade <srajiv@linux.vnet.ibm.com>


  reply	other threads:[~2010-10-26 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 21:42 [PATCH] tpm: Autodetect itpm devices Matthew Garrett
2010-10-26 13:14 ` Rajiv Andrade [this message]
2010-11-01 21:19 ` [2.6.37-rc1 REGRESSION] suspend fails on x200 (was Re: [PATCH] tpm: Autodetect itpm devices) Andy Isaacson
2010-11-01 21:32   ` Matthew Garrett
2010-11-02  1:31     ` Andy Isaacson
2010-11-02  2:36       ` Andy Isaacson
2010-11-02  3:47         ` Rafael J. Wysocki
2010-11-02  4:24           ` Andy Isaacson
2010-11-29 15:54 ` [PATCH] tpm: Autodetect itpm devices Jiri Kosina
2010-11-29 22:08   ` James Morris
2010-11-29 23:06     ` Rajiv Andrade

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=4CC6D440.10604@linux.vnet.ibm.com \
    --to=srajiv@linux.vnet.ibm.com \
    --cc=debora@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.selhorst@sirrix.com \
    --cc=mjg@redhat.com \
    /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.