Hi,
On 27-02-17 23:53, Takashi Iwai wrote:
On Mon, 27 Feb 2017 22:27:58 +0100,
Rafael J. Wysocki wrote:
On Mon, Feb 27, 2017 at 3:40 PM, Takashi Iwai <tiwai@xxxxxxx> wrote:
<snip>
Oh, this is interesting, please let me join to the party.
We've hit a similar problem, but for other one: namely, it's INT0002
that is found on a few CHT devices. It's never bound properly by a
similar reason, where _STA is always zero on Linux:
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (SOCS <= 0x04)
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
The device is supposed to be a "virtual GPIO" stuff, and the driver
hasn't been upstreamed from Intel. Due to the lack of this driver
(and it's binding), the machine gets spurious IRQ#9 after the PM
resume, and it locks up at the second time of PM.
Well, the solution here seems to be to acquire the missing driver
instead of adding quirks to the ACPI core.
The driver is available (not upstreamed, though), but it's not bound
due to _STA above. That's why I'm interested in this thread.
Takashi thanks for pointing me to the INT0002 device / driver to
fix the spurious IRQ#9 after the PM resume issue. I was seeing this
on the GPD-win too (when suspending with power-button + wakeup with
spacebar). I've added a patch to add the INT0002 device to the
always present device list + cleaned up the INT0002 driver. I plan
to submit this upstream soon.
If you want to test this on your device you need these patches:
https://github.com/jwrdegoede/linux-sunxi/commit/a1a6e92f2665376ed72f575553238a93e88bb037
https://github.com/jwrdegoede/linux-sunxi/commit/4946f68f8eaa300f42289bf767722d78cf7fa9e2
https://github.com/jwrdegoede/linux-sunxi/commit/32640c816dd60d17f003ae8306863da01c215afb
https://github.com/jwrdegoede/linux-sunxi/commit/abb6a9d69690bb2a1a00b184b06cdae43d6ad001
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
