From: Kevin Hilman <khilman@ti.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux MMC list <linux-mmc@vger.kernel.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Chris Ball <cjb@laptop.org>,
Ulf Hansson <ulf.hansson@stericsson.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 1/3] PM / QoS: Make it possible to expose PM QoS latency constraints
Date: Fri, 09 Mar 2012 13:34:52 -0800 [thread overview]
Message-ID: <87eht131c3.fsf@ti.com> (raw)
In-Reply-To: <201203092159.40409.rjw@sisk.pl> (Rafael J. Wysocki's message of "Fri, 9 Mar 2012 21:59:40 +0100")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Friday, March 09, 2012, Kevin Hilman wrote:
>> Alan Stern <stern@rowland.harvard.edu> writes:
>>
>> [...]
>>
>> > How about calling it "runtime latency"? Or "runtime wakeup latency" in
>> > case people think there might be some other sort of latency associated
>> > with runtime power management.
>>
>> Either is better than just latency, but I would vote for runtime wakeup
>> latency.
>
> Well, that would be pm_qos_runtime_wakeup_latency_us. Kind of long, IMHO.
Yeah, the long names are why I initially suggested having a 'qos'
subdir.
> Apart from this "wakeup" may be thought to refer to "remote wakeup", which
> is when a device is resumed as a result of an external signal.
>
> pm_qos_resume_latency_us is shorter and since it is referred to in the
> documentation as "resume latency", I don't see any problems with that name.
OK
Kevin
next prev parent reply other threads:[~2012-03-09 21:34 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 0:01 [PATCH 0/3] MMC / PM: Make it possible to use PM QoS latency constraints Rafael J. Wysocki
2012-03-04 0:02 ` [PATCH 1/3] " Rafael J. Wysocki
2012-03-04 10:59 ` Linus Walleij
2012-03-04 19:47 ` Rafael J. Wysocki
2012-03-04 0:04 ` [PATCH 2/3] tmio_mmc / PM: Use PM QoS requests Rafael J. Wysocki
2012-03-04 0:04 ` [PATCH 3/3] sh_mmcif " Rafael J. Wysocki
2012-03-04 19:53 ` [PATCH 0/3] MMC / PM: Make it possible to use PM QoS latency constraints Rafael J. Wysocki
2012-03-04 19:55 ` [PATCH 1/3] MMC / PM: Make it possible to use PM QoS latency constraints, v2 Rafael J. Wysocki
2012-03-05 7:02 ` Linus Walleij
2012-03-06 9:34 ` Guennadi Liakhovetski
2012-03-06 21:06 ` Rafael J. Wysocki
2012-03-04 19:56 ` [PATCH 2/3] tmio_mmc / PM: Use PM QoS requests, v2 Rafael J. Wysocki
2012-03-06 9:40 ` Guennadi Liakhovetski
2012-03-06 21:07 ` Rafael J. Wysocki
2012-03-06 22:33 ` Guennadi Liakhovetski
2012-03-06 23:41 ` Rafael J. Wysocki
2012-03-04 19:56 ` [PATCH 3/3] sh_mmcif " Rafael J. Wysocki
2012-03-06 9:40 ` Guennadi Liakhovetski
2012-03-06 21:09 ` Rafael J. Wysocki
2012-03-07 23:27 ` [PATCH 0/3] PM: Make it possible to expose PM QoS latency constraints Rafael J. Wysocki
2012-03-07 23:28 ` [PATCH 1/3] PM / QoS: " Rafael J. Wysocki
2012-03-08 17:49 ` Kevin Hilman
2012-03-08 18:01 ` Mark Brown
2012-03-08 21:28 ` Rafael J. Wysocki
2012-03-08 21:23 ` Guennadi Liakhovetski
2012-03-08 21:27 ` Rafael J. Wysocki
2012-03-08 22:05 ` Kevin Hilman
2012-03-08 22:37 ` Rafael J. Wysocki
2012-03-08 23:18 ` Kevin Hilman
2012-03-08 23:30 ` Rafael J. Wysocki
2012-03-09 1:02 ` Kevin Hilman
2012-03-09 15:17 ` Alan Stern
2012-03-09 17:10 ` Kevin Hilman
2012-03-09 20:59 ` Rafael J. Wysocki
2012-03-09 21:34 ` Kevin Hilman [this message]
2012-03-07 23:29 ` [PATCH 2/3] tmio_mmc / PM: Use PM QoS latency constraint Rafael J. Wysocki
2012-03-08 8:02 ` Adrian Hunter
2012-03-08 21:29 ` Rafael J. Wysocki
2012-03-07 23:30 ` [PATCH 3/3] sh_mmcif " Rafael J. Wysocki
2012-03-08 11:03 ` Mark Brown
2012-03-08 21:29 ` Rafael J. Wysocki
2012-03-08 23:00 ` [Update][PATCH 0/3] PM: Make it possible to expose PM QoS latency constraints Rafael J. Wysocki
2012-03-08 23:01 ` [Update][PATCH 1/3] PM / QoS: " Rafael J. Wysocki
2012-03-12 19:32 ` Linus Walleij
2012-03-13 0:02 ` Rafael J. Wysocki
2012-03-08 23:03 ` [Update][PATCH 2/3] tmio_mmc / PM: Use PM QoS latency constraint Rafael J. Wysocki
2012-03-08 23:03 ` [Update][PATCH 3/3] sh_mmcif " Rafael J. Wysocki
2012-03-10 21:14 ` [Update][PATCH 0/3] PM: Make it possible to expose PM QoS latency constraints Rafael J. Wysocki
2012-03-06 10:30 ` [PATCH 0/3] MMC / PM: Make it possible to use " Adrian Hunter
2012-03-06 13:39 ` Guennadi Liakhovetski
2012-03-06 21:14 ` Rafael J. Wysocki
2012-03-07 8:31 ` Adrian Hunter
2012-03-07 9:05 ` Rafael J. Wysocki
2012-03-07 19:38 ` Mark Brown
2012-03-07 20:38 ` Kevin Hilman
2012-03-07 20:51 ` Rafael J. Wysocki
2012-03-07 20:54 ` Mark Brown
2012-03-07 21:31 ` Rafael J. Wysocki
2012-03-06 21:47 ` Rafael J. Wysocki
2012-03-07 7:06 ` Adrian Hunter
2012-03-07 9:05 ` Rafael J. Wysocki
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=87eht131c3.fsf@ti.com \
--to=khilman@ti.com \
--cc=adrian.hunter@intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=ulf.hansson@stericsson.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).