[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150930060455.GB7517@srcf.ucam.org>
Date: Wed, 30 Sep 2015 07:04:55 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
peterhuewe@....de, gregkh@...uxfoundation.org,
akpm@...ux-foundation.org, Marcel Selhorst <tpmdd@...horst.net>
Subject: Re: [PATCH 1/2] tpm, tpm_tis: use acpi_driver instead of pnp_driver
On Wed, Sep 30, 2015 at 08:56:12AM +0300, Jarkko Sakkinen wrote:
> I found at least all the IDs listed from drivers/acpi/acpi_pnp.c but you
> might be right that they might be (don't know) with pnpbios.
The entries in acpi_pnp.c mean "If this device is declared in an ACPI
table, create a PNP device". TPMs are kind of at the cutoff where some
vendors may have shipped non-ACPI systems with TPMs that were declared
via pnpbios, so there's a (small) risk that there are some people using
TPMs tied to PNP devices without a corresponding ACPI device.
> Maybe a better solution would to have two tables and have only MSFT0101
> in tpm_acpi_tbl in order to make sure that old functionality is not
> broken up because we want this also to the stable kernels.
I'd agree here.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists