From: Mark Salyzyn <salyzyn@android.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Linux PM <linux-pm@vger.kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit
Date: Wed, 19 Jul 2017 14:23:31 -0700 [thread overview]
Message-ID: <507dec5d-3beb-4dd8-0d5f-90f22fccccd2@android.com> (raw)
In-Reply-To: <CAJZ5v0iVwUy5fdvYu=6HEwLPpw7g6owbFuwNpUJcb_iJ3LCFMA@mail.gmail.com>
On 07/19/2017 01:40 PM, Rafael J. Wysocki wrote:
> On Wed, Jul 19, 2017 at 9:45 PM, Mark Salyzyn <salyzyn@android.com> wrote:
>> Permits power state and battery life diagnosis.
>>
>> Since one is not guaranteed to have a persistent hardware clock to
>> report Suspended for in milliseconds, we report at a higher level
>> at just the entry and exit points for suspend and hibernate.
>>
>> Feature activated by CONFIG_RTC_SHOW_TIME_*
>>
>> Signed-off-by: Mark Salyzyn <salyzyn@android.com>
>>
>> v2:
>> - merge suspend and hibernate into a single patch
> So now I guess you realize that this conflicts with
> https://patchwork.kernel.org/patch/9850217/ and it actually would make
> sense for it to go on top of that?
>
> Thanks,
> Rafael
I see. It would make sense to merge the concepts a bit since the prints
are at the same locations.
Optimization idea: rtc_show_time() in my patch series should be able to
support varargs, never be _disabled_ (CONFIG_RTC_SHOW_TIME_NONE idea is
dropped) and the function would be a drop-in replacement for pr_info,
but add the specified timestamp before the newline. Change it's name to
pr_info_show_time() instead to reflect this adjustment.
I would also prefer that the base messages in patch/980217 be "PM:
suspend entry" and "PM: suspend exit", only because I believe 1.6billion
Linux devices would not need to be retooled, and besides these messages
are shorter/sweeter.
Anyone disagree with some more over-engineering (pr_info_show_time() and
varargs)
-- Mark
next prev parent reply other threads:[~2017-07-19 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 19:45 [PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit Mark Salyzyn
2017-07-19 20:40 ` Rafael J. Wysocki
2017-07-19 21:23 ` Mark Salyzyn [this message]
2017-07-19 21:31 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2017-07-19 19:48 Mark Salyzyn
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=507dec5d-3beb-4dd8-0d5f-90f22fccccd2@android.com \
--to=salyzyn@android.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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