[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200811184902.2fm4eyprmpkfon2j@linutronix.de>
Date: Tue, 11 Aug 2020 20:49:02 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Stephen Berman <stephen.berman@....net>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Robert Moore <robert.moore@...el.com>,
Erik Kaneda <erik.kaneda@...el.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Len Brown <lenb@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
"open list:ACPI COMPONENT ARCHITECTURE (ACPICA)" <devel@...ica.org>
Subject: Re: power-off delay/hang due to commit 6d25be57 (mainline)
On 2020-08-11 19:22:19 [+0200], Stephen Berman wrote:
> Attached.
ssdt6.dsl:
| ThermalZone (TZ10)
| {
…
| Method (_TSP, 0, Serialized) // _TSP: Thermal Sampling Period
| {
| Return (0x0A)
| }
|
| Method (_TZP, 0, Serialized) // _TZP: Thermal Zone Polling
| {
| Return (0x0A)
| }
|
| Method (_TMP, 0, Serialized) // _TMP: Temperature
| {
| \GSA1.ZRC3 ()
| Sleep (0x03E8)
| Notify (\_TZ.TZ10, 0x81) // Thermal Trip Point Change
| Return (0x0B54)
| }
So if I read this correctly then TZ10 should be polled every second
(check) and the temperature function contains a `sleep(1 second)' (which
explains the mysteries delay) followed by the Notify() (which schedules
the worker).
Now I'm curious if Windows has the same ACPI tables and if so how they
behave here. And what the actual plan here was. And where is the border
when one is actual allowed to make fun of someone. So many questions.
> Done as Bug 208877.
Thank you.
> Steve Berman
Sebastian
Powered by blists - more mailing lists