From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Kevin Hilman <khilman@ti.com>, Jean Pihet <j-pihet@ti.com>,
markgross <markgross@thegnar.org>,
kyungmin.park@samsung.com
Subject: Re: [RFC PATCH] PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency
Date: Wed, 15 Feb 2012 19:44:26 +0900 [thread overview]
Message-ID: <CAJ0PZbSODSJvV-_Gje9Hm9Ek22Z9m+PAcsf071OCmAOtsnKzyg@mail.gmail.com> (raw)
In-Reply-To: <201202142311.41483.rjw@sisk.pl>
2012/2/15 Rafael J. Wysocki <rjw@sisk.pl>:
> Hi,
>
> On Tuesday, February 14, 2012, MyungJoo Ham wrote:
>> 1. CPU_DMA_THROUGHPUT
>> 2. DVFS_LATENCY
> Who's going to use the new classes?
>
> Rafael
>
Hello,
1. CPU_DMA_THROUGHPUT:
QoS-request handler: bus/memory devfreq driver.
QoS-requester: multimedia block device drivers (MFC decoder, MFC
endoder, TV-out, Camera, ...)
2. DVFS_LATENCY:
QoS-request handler: devfreq framework and cpufreq governors
(ondemand/conservative).
QoS-requester: those who need faster DVFS reactions temporarily as
mentioned in the thread of pm_qos_update_request_timeout().
Cheers!
MyungJoo.
>
>> ---
>> include/linux/pm_qos.h | 6 +++++-
>> kernel/power/qos.c | 31 ++++++++++++++++++++++++++++++-
>> 2 files changed, 35 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/pm_qos.h b/include/linux/pm_qos.h
>> index e5bbcba..f8ccb7b 100644
>> --- a/include/linux/pm_qos.h
>> +++ b/include/linux/pm_qos.h
>> @@ -13,13 +13,17 @@
>> #define PM_QOS_CPU_DMA_LATENCY 1
>> #define PM_QOS_NETWORK_LATENCY 2
>> #define PM_QOS_NETWORK_THROUGHPUT 3
>> +#define PM_QOS_CPU_DMA_THROUGHPUT 4
>> +#define PM_QOS_DVFS_RESPONSE_LATENCY 5
>>
>> -#define PM_QOS_NUM_CLASSES 4
>> +#define PM_QOS_NUM_CLASSES 6
>> #define PM_QOS_DEFAULT_VALUE -1
>>
>> #define PM_QOS_CPU_DMA_LAT_DEFAULT_VALUE (2000 * USEC_PER_SEC)
>> #define PM_QOS_NETWORK_LAT_DEFAULT_VALUE (2000 * USEC_PER_SEC)
>> #define PM_QOS_NETWORK_THROUGHPUT_DEFAULT_VALUE 0
>> +#define PM_QOS_CPU_DMA_THROUGHPUT_DEFAULT_VALUE 0
>> +#define PM_QOS_DVFS_LAT_DEFAULT_VALUE (2000 * USEC_PER_SEC)
>> #define PM_QOS_DEV_LAT_DEFAULT_VALUE 0
>>
>> struct pm_qos_request {
>> diff --git a/kernel/power/qos.c b/kernel/power/qos.c
>> index 995e3bd..b15e0b7 100644
>> --- a/kernel/power/qos.c
>> +++ b/kernel/power/qos.c
>> @@ -101,11 +101,40 @@ static struct pm_qos_object network_throughput_pm_qos = {
>> };
>>
>>
>> +static BLOCKING_NOTIFIER_HEAD(cpu_dma_throughput_notifier);
>> +static struct pm_qos_constraints cpu_dma_tput_constraints = {
>> + .list = PLIST_HEAD_INIT(cpu_dma_tput_constraints.list),
>> + .target_value = PM_QOS_CPU_DMA_THROUGHPUT_DEFAULT_VALUE,
>> + .default_value = PM_QOS_CPU_DMA_THROUGHPUT_DEFAULT_VALUE,
>> + .type = PM_QOS_MAX,
>> + .notifiers = &cpu_dma_throughput_notifier,
>> +};
>> +static struct pm_qos_object cpu_dma_throughput_pm_qos = {
>> + .constraints = &cpu_dma_tput_constraints,
>> + .name = "cpu_dma_throughput",
>> +};
>> +
>> +
>> +static BLOCKING_NOTIFIER_HEAD(dvfs_lat_notifier);
>> +static struct pm_qos_constraints dvfs_lat_constraints = {
>> + .list = PLIST_HEAD_INIT(dvfs_lat_constraints.list),
>> + .target_value = PM_QOS_DVFS_LAT_DEFAULT_VALUE,
>> + .default_value = PM_QOS_DVFS_LAT_DEFAULT_VALUE,
>> + .type = PM_QOS_MIN,
>> + .notifiers = &dvfs_lat_notifier,
>> +};
>> +static struct pm_qos_object dvfs_lat_pm_qos = {
>> + .constraints = &dvfs_lat_constraints,
>> + .name = "dvfs_latency",
>> +};
>> +
>> static struct pm_qos_object *pm_qos_array[] = {
>> &null_pm_qos,
>> &cpu_dma_pm_qos,
>> &network_lat_pm_qos,
>> - &network_throughput_pm_qos
>> + &network_throughput_pm_qos,
>> + &cpu_dma_throughput_pm_qos,
>> + &dvfs_lat_pm_qos,
>> };
>>
>> static ssize_t pm_qos_power_write(struct file *filp, const char __user *buf,
>>
>
--
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
next prev parent reply other threads:[~2012-02-15 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 2:26 [RFC PATCH] PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency MyungJoo Ham
2012-02-14 5:04 ` MyungJoo Ham
2012-02-25 23:43 ` Rafael J. Wysocki
2012-02-27 6:14 ` MyungJoo Ham
2012-02-27 6:22 ` [PATCH v2] " MyungJoo Ham
2012-02-14 22:11 ` [RFC PATCH] " Rafael J. Wysocki
2012-02-15 10:44 ` MyungJoo Ham [this message]
2012-02-22 8:03 ` [RFC PATCH 0/2] CPUFreq / Ondemand update MyungJoo Ham
2012-02-22 8:03 ` [RFC PATCH 1/2] CPUfreq ondemand: update sampling rate without waiting for next sampling MyungJoo Ham
2012-02-25 23:59 ` Rafael J. Wysocki
2012-02-28 2:19 ` MyungJoo Ham
2012-02-22 8:03 ` [RFC PATCH 2/2] CPUfreq ondemand: handle QoS request on DVFS response latency MyungJoo Ham
2012-02-25 11:30 ` Pavel Machek
2012-02-25 23:47 ` Rafael J. Wysocki
2012-02-28 0:39 ` MyungJoo Ham
2012-02-29 8:54 ` [PATCH v2 0/2] CPUFreq / Ondemand update MyungJoo Ham
2012-02-29 8:54 ` [PATCH v2 1/2] CPUfreq ondemand: update sampling rate without waiting for next sampling MyungJoo Ham
2012-02-29 8:54 ` [PATCH v2 2/2] CPUfreq ondemand: handle QoS request on DVFS response latency MyungJoo Ham
2012-02-25 17:59 ` [RFC PATCH] PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency mark gross
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=CAJ0PZbSODSJvV-_Gje9Hm9Ek22Z9m+PAcsf071OCmAOtsnKzyg@mail.gmail.com \
--to=myungjoo.ham@samsung.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=markgross@thegnar.org \
--cc=myungjoo.ham@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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).