From: Pavel Machek <pavel@ucw.cz>
To: Mark Salyzyn <salyzyn@android.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Todd Poynor <toddpoynor@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>
Subject: Re: PM / Suspend: Print wall time at suspend entry and exit
Date: Thu, 13 Jul 2017 10:54:08 +0200 [thread overview]
Message-ID: <20170713085407.GD1363@amd> (raw)
In-Reply-To: <e9c40b99-7fa7-71b2-5917-250d638a5162@android.com>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Hi!
> >And userspace should not really be parsing kernel logs for time
> >keeping, right?
> Post-mortem, armed with user space logs in CLOCK_REALTIME (a choice that
> most want on Android Logging) and kernel logs, these messages are
> _invaluable_ in order to merge the kernel activities with user space. At
> runtime they help too, as there is some post-mortem activities on user space
> logging daemon startup.
> >The devices you are talking about... is any of them running something
> >close to mainline kernel, or is planned for merge? I'd like to get a
> >phone that is supported by mainline...
>
> Android on hikey development board is running 4.9 kernel + Android patches
> (this is one of 'em), I _expect_ ToT will work. As for _real_ phones, you
> have to take that up with the vendors making the chips.
Well, there are real phones with mainline Linux: Nokia N900, N9, N950,
Motorola Droid 4.
Current kernel is 4.13, not v4.9.
Yes, Qualcomm is a problem. There are other vendors, you can get those
phones in retail. So no, I don't think android community is doing a
good job. I don't think it makes sense to merge patches that "help
debugging" when basic support is missing.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-07-13 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 19:31 PM / Suspend: Print wall time at suspend entry and exit Mark Salyzyn
2017-06-05 19:31 ` PM / Hibernation: Print wall time at hibernation " Mark Salyzyn
2017-06-05 20:07 ` PM / Suspend: Print wall time at suspend " Pavel Machek
2017-06-05 20:58 ` Rafael J. Wysocki
2017-06-05 21:18 ` Pavel Machek
2017-06-05 21:47 ` Mark Salyzyn
2017-06-05 22:10 ` Mark Salyzyn
2017-06-05 22:40 ` Pavel Machek
2017-06-06 18:05 ` Mark Salyzyn
2017-07-13 8:54 ` Pavel Machek [this message]
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=20170713085407.GD1363@amd \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=salyzyn@android.com \
--cc=toddpoynor@google.com \
/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).