[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D68E80B.90001@gmail.com>
Date: Sat, 26 Feb 2011 12:46:19 +0100
From: Jiri Slaby <jirislaby@...il.com>
To: Stefan Berger <stefanb@...ux.vnet.ibm.com>
CC: preining@...ic.at,
Linux kernel mailing list <linux-kernel@...r.kernel.org>,
Rajiv Andrade <srajiv@...ux.vnet.ibm.com>,
"debora@...ux.vnet.ibm.com" <debora@...ux.vnet.ibm.com>
Subject: Re: [PATCH] tpm_tis: Re-enable interrupts upon resume
On 02/22/2011 08:49 PM, Stefan Berger wrote:
> Below patch applies to the tip of the git tree.
>
> This patch makes sure that if the TPM TIS interface is run in interrupt
> mode (rather than polling mode) that the interrupts are enabled in the
> TPM's interrupt enable register which may either have been cleared by
> the TPM's TIS loosing its state during device sleep in ACPI S3 (suspend)
> or by the BIOS, which upon resume sends a TPM_Startup() command to the
> TPM, and may run the TPM in polling mode and leave the TIS interrupts
> disabled once it transfers control to the OS again.
>
> Problem is, I don't currently have a machine running the TPM in
> interrupt mode. I found this through a self-built TPM device model for
> Qemu and SeaBIOS patches, where this does resolve a problem upon resume.
>
> You may want to check if your TPM runs with interrupts by doing
>
> cat /proc/interrupts | grep -i tpm
No, this is empty output.
regards,
--
js
--
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