[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160920155943.zrj7wwgg7ugqyv6i@sig21.net>
Date: Tue, 20 Sep 2016 17:59:43 +0200
From: Johannes Stezenbach <js@...21.net>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: linux-acpi@...r.kernel.org, platform-driver-x86@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Cherryview wake up events
On Tue, Sep 20, 2016 at 01:40:14PM +0300, Mika Westerberg wrote:
> Can you check if you have:
>
> Hardware Reduced (V5) : 1
>
> in that FADT table?
Nope, it is "Hardware Reduced (V5) : 0". Now the FADT is also at
https://linuxtv.org/~js/e200ha/
> If yes, it probably does not have the normal Fixed power button but
> instead it has something called "Windows button array device" with
> _HID/_CID of PNP0C40. Looking at your dsdt.dsl, this looks to be the
> case.
>
> That device is driven by soc_button_array.c driver which can be enabled
> with CONFIG_KEYBOARD_GPIO=y and CONFIG_INPUT_SOC_BUTTON_ARRAY=y. Can you
> check if you have that enabled already?
>
> You should actually see it in /proc/interrupts with names like "power"
> and so on.
I added CONFIG_INPUT_SOC_BUTTON_ARRAY=y, but no joy.
Maybe because the _HID is INTCFD9, only _CID is PNP0C40?
It also has a _DSM with UUID dfbcf3c5-e7a5-44e6-9c1f-29c76f6e059c.
BTW, lsinput already lists two "Power Button" devices,
phys : "PNP0C0C/button/input0"
phys : "LNXPWRBN/button/input0"
None of them generates events in input-events.
Thanks,
Johannes
Powered by blists - more mailing lists