From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Cohen <david.a.cohen@linux.intel.com>
Subject: Re: Cherryview wake up events
Date: Wed, 25 Jan 2017 11:29:26 +0200 [thread overview]
Message-ID: <20170125092926.GO17297@lahna.fi.intel.com> (raw)
In-Reply-To: <20170124192314.gw6njffcgwyfm2gp@sig21.net>
On Tue, Jan 24, 2017 at 08:23:14PM +0100, Johannes Stezenbach wrote:
> On Tue, Jan 24, 2017 at 04:28:29PM +0200, Andy Shevchenko wrote:
> > They probably release just almost all One Big Ugly patch from official
> > BSP, which by some reason, includes all Intel MID SoCs, Baytrail.
> > I think I know how Dollar Cove related code ended up there. But that
> > all stuff is a total mess.
>
> I agree. Probably it was a mistake to bring up this code here.
> Let me try to go back two steps: Could you please let me
> know if there is any progress in mainlining the TI Dollar Cove PMIC
> and related drivers? Is there a schedule?
David, can you please answer this!
> After waiting for four months I'm actually getting impatient
> because by now the Cherryview based hardware seems to go out
> of production and I fear the mainlining might never happen.
If we hear nothing from David soon, I think I'll just take it to my
growing todo list. Unless someone else wants to take it.
next prev parent reply other threads:[~2017-01-25 9:29 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
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 [this message]
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=20170125092926.GO17297@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=david.a.cohen@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;
as well as URLs for NNTP newsgroup(s).