From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Cherryview wake up events
Date: Wed, 21 Sep 2016 12:06:14 +0300 [thread overview]
Message-ID: <20160921090614.GY1811@lahna.fi.intel.com> (raw)
In-Reply-To: <20160920211153.y7ntwwik2l6ppoqz@sig21.net>
On Tue, Sep 20, 2016 at 11:11:53PM +0200, Johannes Stezenbach wrote:
> On Tue, Sep 20, 2016 at 05:59:43PM +0200, Johannes Stezenbach wrote:
> > On Tue, Sep 20, 2016 at 01:40:14PM +0300, Mika Westerberg wrote:
> > > 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.
>
> Or it is because the PNP0C40 device depends on GpioInt from PMIC
> which isn't available...
>
> Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
> {
> Name (CBUF, ResourceTemplate ()
> {
> GpioInt (Edge, ActiveBoth, ExclusiveAndWake, PullUp, 0x0BB8,
> "\\_SB.PCI0.I2C7.PMI2", 0x00, ResourceConsumer, ,
> )
> { // Pin list
> 0x0016
> }
> })
> Return (CBUF) /* \_SB_.TBAD._CRS.CBUF */
> }
Most likely this is the reason. I'll try to find if we have an existing
driver for this PMIC somewhere. I guess this is the Dollar Cove which is
successor of Crystal Cove IIRC which is already supported by the
mainline kernel.
next prev parent reply other threads:[~2016-09-21 9:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:21 Johannes Stezenbach
2016-09-19 11:56 ` Mika Westerberg
2016-09-19 20:36 ` Johannes Stezenbach
2016-09-20 9:18 ` Mika Westerberg
2016-09-20 10:14 ` Johannes Stezenbach
2016-09-20 10:40 ` Mika Westerberg
2016-09-20 15:59 ` Johannes Stezenbach
2016-09-20 21:11 ` Johannes Stezenbach
2016-09-21 9:06 ` Mika Westerberg [this message]
2016-09-21 9:16 ` Johannes Stezenbach
2016-09-23 8:19 ` Mika Westerberg
2016-09-23 9:59 ` Johannes Stezenbach
2016-10-05 12:46 ` Johannes Stezenbach
2016-10-05 13:05 ` Mika Westerberg
2016-12-04 18:52 ` Johannes Stezenbach
2016-12-05 11:06 ` Mika Westerberg
2017-01-24 9:41 ` Johannes Stezenbach
2017-01-24 11:14 ` Andy Shevchenko
2017-01-24 13:52 ` Johannes Stezenbach
2017-01-24 14:28 ` Andy Shevchenko
2017-01-24 19:23 ` Johannes Stezenbach
2017-01-25 9:29 ` Mika Westerberg
2017-01-26 22:56 ` Andy Shevchenko
2017-01-27 11:38 ` Johannes Stezenbach
2017-01-27 13:21 ` Andy Shevchenko
2017-01-27 13:30 ` Johannes Stezenbach
2017-01-30 20:57 ` Johannes Stezenbach
2017-01-30 22:05 ` Andy Shevchenko
2017-01-31 14:37 ` Johannes Stezenbach
2017-01-31 14:44 ` Mika Westerberg
2017-02-02 9:52 ` Johannes Stezenbach
2017-02-02 10:31 ` Mika Westerberg
2017-02-02 11:12 ` Johannes Stezenbach
2017-02-02 11:35 ` Mika Westerberg
2017-02-02 12:16 ` Mika Westerberg
2017-02-02 13:52 ` Johannes Stezenbach
2017-02-02 14:26 ` Mika Westerberg
2017-02-02 14:31 ` Johannes Stezenbach
2017-02-02 15:02 ` Mika Westerberg
2017-02-02 15:42 ` Johannes Stezenbach
2017-02-02 15:58 ` Mika Westerberg
2017-02-02 17:32 ` Johannes Stezenbach
2017-02-03 10:00 ` Mika Westerberg
2017-02-03 13:16 ` Johannes Stezenbach
2017-02-09 9:24 ` Johannes Stezenbach
2017-02-09 9:38 ` Mika Westerberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160921090614.GY1811@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=js@sig21.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome