[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ0PZbSODSJvV-_Gje9Hm9Ek22Z9m+PAcsf071OCmAOtsnKzyg@mail.gmail.com>
Date: Wed, 15 Feb 2012 19:44:26 +0900
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Kevin Hilman <khilman@...com>, Jean Pihet <j-pihet@...com>,
markgross <markgross@...gnar.org>, kyungmin.park@...sung.com
Subject: Re: [RFC PATCH] PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency
2012/2/15 Rafael J. Wysocki <rjw@...k.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists