From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: ACPI errors from TPM PPI Date: Mon, 8 Jul 2013 17:13:01 +0100 Message-ID: <20130708161301.GA611@srcf.ucam.org> References: <10172565.WQexNecTHe@vostro.rjw.lan> <20130706111025.GZ4898@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:51557 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751740Ab3GHQNZ (ORCPT ); Mon, 8 Jul 2013 12:13:25 -0400 Content-Disposition: inline In-Reply-To: <20130706111025.GZ4898@intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Mika Westerberg Cc: Adam Langley , "Rafael J. Wysocki" , xiaoyan.zhang@intel.com, Bob Moore , Lv Zheng , ACPI Devel Maling List On Sat, Jul 06, 2013 at 02:10:25PM +0300, Mika Westerberg wrote: > I wonder whether there is a real PNP Id associated with that device? You'd really hope so - it's certainly completely bogus to rely on the device name. On the other hand, this is basically re-probing for a device that the kernel already knows about. Just exporting the device from tpm_tis would make more sense. -- Matthew Garrett | mjg59@srcf.ucam.org