From: Johannes Stezenbach <js@sig21.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
David Cohen <david.a.cohen@linux.intel.com>
Subject: Re: Cherryview wake up events
Date: Fri, 23 Sep 2016 11:59:53 +0200 [thread overview]
Message-ID: <20160923095953.gkzzblbipye3ogft@sig21.net> (raw)
In-Reply-To: <20160923081904.GM1218@lahna.fi.intel.com>
On Fri, Sep 23, 2016 at 11:19:04AM +0300, Mika Westerberg wrote:
> On Wed, Sep 21, 2016 at 11:16:35AM +0200, Johannes Stezenbach wrote:
> > There is an ADBG ("TI_DCOVE") in PMI2._STA, so Dollar Cove
> > sounds like a good guess.
>
> David (CC'd) is working on getting the Dollar Cove PMIC driver
> upstreamed to the mainline kernel.
Excellent news! Repeating essential info to avoid any
confusion, the PMIC is
Device (PMI2)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "INT33F5" /* TI PMIC Controller */) // _HID: Hardware ID
Name (_CID, "INT33F5" /* TI PMIC Controller */) // _CID: Compatible ID
Name (_DDN, "TI PMIC Controller") // _DDN: DOS Device Name
(Because the INT33F4 XPOWER PMIC also has ADBG ("XPWR_DCOVE")
so I'm not sure "Dollar Cove" is a unique name.)
I put the Asus E200HA DSDT at
https://linuxtv.org/~js/e200ha/
Thanks,
Johannes
next prev parent reply other threads:[~2016-09-23 10:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:21 Cherryview wake up events 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
2016-09-21 9:16 ` Johannes Stezenbach
2016-09-23 8:19 ` Mika Westerberg
2016-09-23 9:59 ` Johannes Stezenbach [this message]
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=20160923095953.gkzzblbipye3ogft@sig21.net \
--to=js@sig21.net \
--cc=david.a.cohen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).