On 12 March 2013 17:15, Sanjay Singh Rawat wrote:
> add a window to display the stats of thermal, cooling zones and also
> information given by the hwmon sensor.
Nice window displaying thermal/hwmon sysfs information. Good enough to
start with. Any plans to process sysfs information and display m
On 5 February 2013 12:21, MyungJoo Ham wrote:
> On Tue, Jan 15, 2013 at 8:21 PM, Rajagopal Venkat
> wrote:
>> On 14 January 2013 20:06, MyungJoo Ham wrote:
>>> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
>>> wrote:
>>>> Set devfreq device min an
MyungJoo, Ping.
On 15 January 2013 17:16, Rajagopal Venkat wrote:
> On 14 January 2013 20:18, MyungJoo Ham wrote:
>> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
>> wrote:
>>> devfreq stats is not taking device suspend and resume into
>>> account. Fix it.
MyungJoo, Ping.
On 15 January 2013 16:51, Rajagopal Venkat wrote:
> On 14 January 2013 20:06, MyungJoo Ham wrote:
>> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
>> wrote:
>>> Set devfreq device min and max frequency limits when device
>>> is added to dev
Allow reparenting of a clock(multiple and single parent)
to the orphan list when new parent clock is NULL.
Signed-off-by: Rajagopal Venkat
---
drivers/clk/clk.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index
On 16 January 2013 04:15, Mike Turquette wrote:
> Quoting Rajagopal Venkat (2013-01-08 22:29:48)
>> while reparenting a clock, NULL check is done for clock in
>> consideration and its new parent. So re-check is not required.
>> If done, else part becomes unreachable
On 14 January 2013 20:18, MyungJoo Ham wrote:
> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
> wrote:
>> devfreq stats is not taking device suspend and resume into
>> account. Fix it.
>>
>> Signed-off-by: Rajagopal Venkat
>
> With monitor_suspend(), we ar
On 14 January 2013 20:12, MyungJoo Ham wrote:
> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
> wrote:
>> Mark the stats start time stamp when actual load monitoring is
>> started for accuracy.
>>
>
> It appears that you are changing the semantics of the infor
On 14 January 2013 20:06, MyungJoo Ham wrote:
> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
> wrote:
>> Set devfreq device min and max frequency limits when device
>> is added to devfreq, provided frequency table is supplied.
>> This helps governors to suggest
while reparenting a clock, NULL check is done for clock in
consideration and its new parent. So re-check is not required.
If done, else part becomes unreachable.
Signed-off-by: Rajagopal Venkat
---
drivers/clk/clk.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff
On 9 January 2013 11:20, Tushar Behera wrote:
> On 01/08/2013 06:33 PM, Rajagopal Venkat wrote:
>> while reparenting a clock, NULL check is done for clock in
>> consideration and its new parent. So re-check is not required.
>> If done, else part becomes unreachable.
>>
while reparenting a clock, NULL check is done for clock in
consideration and its new parent. So re-check is not required.
If done, else part becomes unreachable.
Signed-off-by: Rajagopal Venkat
---
drivers/clk/clk.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a
suspend the devfreq
and pm_runtime_resume() will resume the devfreq.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 89 ++---
include/linux/devfreq.h | 12 --
2 files changed, 76 insertions(+), 25 deletions(-)
diff --git a/drivers
Mark the stats start time stamp when actual load monitoring is
started for accuracy.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 5782c9b
Set devfreq device min and max frequency limits when device
is added to devfreq, provided frequency table is supplied.
This helps governors to suggest target frequency with in
limits.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 24
1 file changed
devfreq stats is not taking device suspend and resume into
account. Fix it.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 2843a22
Hi,
The Powertop Linaro-2012.12 release is available[1] based on upstream
v2.2 version. The upstream v2.2 minor release mainly includes bug fixes
and new report generator facility. Detailed notes available at [2].
Powertop Linaro-2012.12 release highlights
- Bug fix to display freq stats when cpu
Powertop fails to display frequency stats when cpuidle subsystem
is not enabled. Fix it.
Signed-off-by: Rajagopal Venkat
---
src/cpu/cpu.h | 7 ++-
src/cpu/cpu_linux.cpp | 36 +++-
2 files changed, 33 insertions(+), 10 deletions(-)
diff --git a/src
suspend the devfreq
and pm_runtime_resume() will resume the devfreq.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 145 --
include/linux/devfreq.h | 12
2 files changed, 102 insertions(+), 55 deletions(-)
diff --git a/drivers
On 15 October 2012 14:20, Amit Kucheria wrote:
> On Mon, Oct 15, 2012 at 1:51 PM, Rajagopal Venkat
> wrote:
>> This patch adds devfreq support for Mali driver. Though mali driver
>> has its own mechanism for load monitoring, this patch makes use of
>> devfreq f
/2012/10/4/95
Patch is based on git://git.linaro.org/people/chunsangjeong/mali-dev.git
tree.
Signed-off-by: Rajagopal Venkat
---
drivers/gpu/arm/mali/Kconfig | 7 +
drivers/gpu/arm/mali/Makefile | 11 ++
drivers/gpu/arm/mali/linux/mali_kernel_devfreq.c
based monitoring functions or to implement their own mechanism.
>> - devfreq core interacts with governors via events to perform
>> specific actions. These events include start/stop devfreq.
>> This sets ground for adding suspend/resume events.
>>
>> The devfreq apis are no
On 8 October 2012 03:31, Rafael J. Wysocki wrote:
> On Thursday 04 of October 2012 14:58:33 Rajagopal Venkat wrote:
>> Add devfreq suspend/resume apis for devfreq users. This patch
>> supports suspend and resume of devfreq load monitoring, required
>> for devices which can i
based monitoring functions or to implement their own mechanism.
>> - devfreq core interacts with governors via events to perform
>> specific actions. These events include start/stop devfreq.
>> This sets ground for adding suspend/resume events.
>>
>> The devfreq apis are no
ince v2:
>> - added new helper function for polling interval update
>> - handled work suspend/resume contention between devfreq driver
>> and sysfs
>>
>> Changes since v3:
>> - added additonal checks in suspend/resume to avoid invalid usage of apis
>> - ad
sets ground for adding suspend/resume events.
The devfreq apis are not modified and are kept intact.
Signed-off-by: Rajagopal Venkat
---
Documentation/ABI/testing/sysfs-class-devfreq | 8 -
drivers/devfreq/devfreq.c | 443 +++---
drivers/devfreq/governor.h
- handled work suspend/resume contention between devfreq driver
and sysfs
Changes since v3:
- added additonal checks in suspend/resume to avoid invalid usage of apis
- added check in devfreq_monitor_start, not to start monitoring when
polling_ms is set to zero.
--
Rajagopal Venkat (3):
devfreq
Add devfreq suspend/resume apis for devfreq users. This patch
supports suspend and resume of devfreq load monitoring, required
for devices which can idle.
Signed-off-by: Rajagopal Venkat
Acked-by: MyungJoo Ham
---
drivers/devfreq/devfreq.c | 28
frequency.
Signed-off-by: Rajagopal Venkat
Acked-by: MyungJoo Ham
---
Documentation/ABI/testing/sysfs-class-devfreq | 11 ++-
drivers/devfreq/devfreq.c | 14 ++
include/linux/devfreq.h | 3 +++
3 files changed, 27 insertions(+), 1 deletion
s with governors via events to perform
>> >> specific actions. These events include start/stop devfreq.
>> >> This sets ground for adding suspend/resume events.
>> >>
>> >> The devfreq apis are not modified and are kept intact.
>> >>
&g
based monitoring functions or to implement their own mechanism.
>> - devfreq core interacts with governors via events to perform
>> specific actions. These events include start/stop devfreq.
>> This sets ground for adding suspend/resume events.
>>
>> The devfreq apis are
On 24 September 2012 21:27, Chris Ferron wrote:
> On 09/24/2012 06:28 AM, Rajagopal Venkat wrote:
>>
>> This patch adds following minor changes to prepare powertop
>> to support Android platform.
>>
>> - Add missing HAVE_CONFIG_H conditional check.
>> - r
affect powertop functionality.
Signed-off-by: Rajagopal Venkat
---
src/devices/ahci.cpp| 4 ++--
src/devices/alsa.cpp| 4 ++--
src/devices/network.cpp | 16
src/main.cpp| 2 ++
4 files changed, 6 insertions(+), 20 deletions(-)
diff --git a/src/devices/ahci.cpp
This patch adds stubs for features that are not supported
by Andriod. An header file which defines all stubs is
included only for Android builds.
Signed-off-by: Rajagopal Venkat
---
Android.mk | 33 ++-
src/android_stubs.h | 65
sets ground for adding suspend/resume events.
The devfreq apis are not modified and are kept intact.
Signed-off-by: Rajagopal Venkat
---
Documentation/ABI/testing/sysfs-class-devfreq | 8 -
drivers/devfreq/devfreq.c | 431 +++---
drivers/devfreq/governor.h
- Handled work suspend/resume contention between devfreq driver
and sysfs
--
Rajagopal Venkat (3):
devfreq: Core updates to support devices which can idle
devfreq: Add suspend and resume apis
devfreq: Add current freq callback in device profile
Documentation/ABI/testing/sysfs-class-devfreq
Add devfreq suspend/resume apis for devfreq users. This patch
supports suspend and resume of devfreq load monitoring, required
for devices which can idle.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 28
drivers/devfreq/governor.h
frequency.
Signed-off-by: Rajagopal Venkat
Signed-off-by: MyungJoo Ham
---
Documentation/ABI/testing/sysfs-class-devfreq | 11 ++-
drivers/devfreq/devfreq.c | 14 ++
include/linux/devfreq.h | 3 +++
3 files changed, 27 insertions(+), 1
el and it won't happen
> often. However, it may behave incorrectly.
>
> Why don't we simply let the all the struct devfreq protected
> when the external code (governors) is probably reading/writing the
> protected values?
>
> This also guarantees that th
affect powertop functionality.
Signed-off-by: Rajagopal Venkat
---
src/devices/ahci.cpp |4 ++--
src/devices/alsa.cpp |4 ++--
src/devices/network.cpp| 16
src/lib.cpp|2 +-
src/main.cpp |2 ++
src/process/do_process.cpp
This patch adds stubs for features that are not supported
by Andriod. An header file which defines all stubs is
included only for Android builds.
Signed-off-by: Rajagopal Venkat
---
Android.mk | 33 +++--
src/android_stubs.h | 47
From: Rajagopal Venkat
Devfreq returns governor predicted frequency as current frequency
via sysfs interface. But device may not support all frequencies
that governor predicts. So add a callback in device profile to get
current freq from driver. Also add a new sysfs node to expose
governor
From: Rajagopal Venkat
Prepare devfreq core framework to support devices which
can idle. When device idleness is detected perhaps through
runtime-pm, need some mechanism to suspend devfreq load
monitoring and resume back when device is online. Present
code continues monitoring unless device is
From: Rajagopal Venkat
Add devfreq suspend/resume apis for devfreq users. This patch
supports suspend and resume of devfreq load monitoring, required
for devices which can idle.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 26
From: Rajagopal Venkat
This patchset updates devfreq core to add support for devices
which can idle. When device idleness is detected perhaps
through runtime-pm, need some mechanism to suspend devfreq
load monitoring and resume when device is back online.
patch 1 introduce core design changes
d locking for these functions?
> Event_handler callback won't want the properties in devfreq to be changed
> externally during its execution.
Agree.
>
> Plus, please edit Documentation/ABI entry (central_polling is being removed)
Done.
>
> Other than that, it looks
On 10 September 2012 03:30, Rafael J. Wysocki wrote:
> On Monday, September 03, 2012, Rajagopal Venkat wrote:
>> Devfreq returns governor predicted frequency as current
>> frequency via sysfs interface. But device may not support
>> all frequencies that governor predicts
On 10 September 2012 03:21, Rafael J. Wysocki wrote:
> On Monday, September 03, 2012, Rajagopal Venkat wrote:
>> Add devfreq suspend/resume apis for devfreq users. This patch
>> supports suspend and resume of devfreq load monitoring, required
>> for devices which can idle
On 10 September 2012 03:16, Rafael J. Wysocki wrote:
> On Monday, September 03, 2012, Rajagopal Venkat wrote:
>> Prepare devfreq core framework to support devices which
>> can idle. When device idleness is detected perhaps through
>> runtime-pm, need some mechanism to
On 5 September 2012 23:36, Arjan van de Ven wrote:
> On 9/5/2012 10:45 AM, Rajagopal Venkat wrote:
>> On 5 September 2012 22:52, Arjan van de Ven wrote:
>>> On 9/5/2012 10:19 AM, Rajagopal Venkat wrote:
>>>> On 5 September 2012 22:39, Arjan van de Ven wrote:
>&g
event timestamps from global map at the end of each
measurement to avoid collision with earlier recorded timestamps.
Signed-off-by: Rajagopal Venkat
---
src/process/do_process.cpp | 12
src/process/timer.cpp | 4
src/process/work.cpp | 4
3 files changed, 20
On 5 September 2012 22:52, Arjan van de Ven wrote:
> On 9/5/2012 10:19 AM, Rajagopal Venkat wrote:
>> On 5 September 2012 22:39, Arjan van de Ven wrote:
>>> On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
>>>>> measure1:
>>>>> ev3.start
>>
On 5 September 2012 22:39, Arjan van de Ven wrote:
> On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
>>> measure1:
>>> ev3.start
>>> ev1.end <<<<<
>>
>> evX.end <<<<<
>> These events are causing numbers to go wrong.
On 5 September 2012 18:14, Sergey Senozhatsky
wrote:
> Hi,
>
> On (09/05/12 15:52), Rajagopal Venkat wrote:
>> Incorrect timer and work perf events timestamp tracing is one
>> of the reason for reporting usage over 100%. This patch will
>> resolve the issue by
>>
over 100% usage.
- clearing event timestamps from global map at the end of each
measurement to avoid collision with earlier recorded timestamps.
Signed-off-by: Rajagopal Venkat
---
src/process/timer.cpp | 5 -
src/process/work.cpp | 5 -
2 files changed, 8 insertions(+), 2 deletions
new sysfs node to expose governor predicted next
target frequency.
Signed-off-by: Rajagopal Venkat
---
Documentation/ABI/testing/sysfs-class-devfreq | 7 +++
drivers/devfreq/devfreq.c | 14 ++
include/linux/devfreq.h | 3 +++
3 files
sets ground for adding suspend/resume events.
The devfreq apis are not modified and are kept intact.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 376 ++
drivers/devfreq/governor.h| 9 +
drivers/devfreq
Add devfreq suspend/resume apis for devfreq users. This patch
supports suspend and resume of devfreq load monitoring, required
for devices which can idle.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 26 ++
drivers/devfreq/governor.h
devfreq_resume_device() are
added to support suspend/resume of device devfreq.
--
Rajagopal Venkat (3):
devfreq: core updates to support devices which can idle
devfreq: Add suspend and resume apis
devfreq: Add current freq callback in device profile
Documentation/ABI/testing/sysfs-class-devfreq
driver.
>> Rather it would help in recommending freq with in limits.
>>
>> This information also helps user space to know the device operating limits.
>
> With the optional frequency statistics support proposed by Jonghwa Lee,
> devfreq.c is going to be accepting the list of operable freq
edicts. As per the design
>> >> its driver responsibility to maintain current frequency
>> >> at which device is operating. So add a callback in device
>> >> profile to fix this.
>> >>
>> >> Signed-off-by: Rajagopal Venkat
>> >
>
t it properly. Whenever we can,
> it's better to remove device specific information from governors
> and cores as long as it does not significantly increase the
> complexity of drivers.
>
Sorry, but I disagree on this point. Devfreq core should not consider user
input for granted
On 20 August 2012 15:49, MyungJoo Ham wrote:
>
> > This patch adds suspend and resume apis needed
> > for devices which can idle. Suspend/resume apis
> > are called from driver to suspend/resume devfreq
> > load monitoring of that device.
> >
> > Signe
ere ever needed. Never assume UINT_MAX as max frequency.
>
>
> >
> > The devfreq apis are not modified and are kept intact.
>
> The ABIs are not.
>
> You can no longer do "# echo 0 > ABI_path" in order to deactivate.
Only relevant for ondemand gover
cy
>> at which device is operating. So add a callback in device
>> profile to fix this.
>>
>> Signed-off-by: Rajagopal Venkat
>
> We still need to support "intended frequency".
>
> The "cur_freq" node is to show the intended frequency.
>
-- Forwarded message --
From: Rajagopal Venkat
Date: 17 August 2012 23:50
Subject: [PATCH 0/3][RFC] devfreq: Add support for devices which can idle
To: mturque...@linaro.org, myungjoo@samsung.com,
kyungmin.p...@samsung.com, r...@sisk.pl
Cc: patc...@linaro.org, linaro-dev
On 20 August 2012 15:49, MyungJoo Ham wrote:
> > This patch adds suspend and resume apis needed
> > for devices which can idle. Suspend/resume apis
> > are called from driver to suspend/resume devfreq
> > load monitoring of that device.
> >
> > Signed-o
ever needed. Never assume UINT_MAX as max frequency.
>
> >
> > The devfreq apis are not modified and are kept intact.
>
> The ABIs are not.
>
> You can no longer do "# echo 0 > ABI_path" in order to deactivate.
>
Only relevant for ondemand governo
help governors to predict target frequecy
with in limits.
The devfreq apis are not modified and are kept intact.
Signed-off-by: Rajagopal Venkat
---
Documentation/ABI/testing/sysfs-class-devfreq | 33 +-
drivers/devfreq/devfreq.c | 418 --
drivers
fix this.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 14 --
include/linux/devfreq.h | 6 +++---
2 files changed, 15 insertions(+), 5 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 375b5aa1..798e8ca 100644
--- a/drivers
This patch adds suspend and resume apis needed
for devices which can idle. Suspend/resume apis
are called from driver to suspend/resume devfreq
load monitoring of that device.
Signed-off-by: Rajagopal Venkat
---
drivers/devfreq/devfreq.c | 30
added to support suspend/resume of device devfreq.
--
Rajagopal Venkat (3):
devfreq: core updates to support devices which can idle
devfreq: Add suspend and resume apis
devfreq: Add current freq callback in device profile
Documentation/ABI/testing/sysfs-class-devfreq | 33 +-
drivers/devfreq
From: Rajagopal Venkat
Update all manifest files to include new
powertop-2.0 version.
Signed-off-by: Rajagopal Venkat
---
default.xml | 2 +-
landing-snowball.xml | 2 +-
linaro-default.xml| 2 +-
staging-galaxynexus.xml | 2 +-
staging-origen.xml
b0701b458ece1396e;hb=HEAD>
What is your test platform, kernel version, etc.
> By your comment of what fields contents, I am betting there is more work
> to be done here
> then just what you sent regardless.
> Im not going to take this patch at this time, until I understand the ful
This patch fixes powertop to display cpuidle states on platforms
where cpuidle stateX directory name field does not contain
"CX" string. On some platforms, the name field contains meaningful
strings like WFI, Sleep, DeepSleep.
Please review the patch.
On 23 June 2012 00:08, Rajago
On 26 July 2012 08:45, kejun.zhou wrote:
> From: "kejun.zhou"
>
> Signed-off-by: kejun.zhou
> ---
> Android.mk |4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Android.mk b/Android.mk
> index c82cd95..fa1c225 100644
> --- a/Android.mk
> +++ b/Android.mk
> @@ -28,7
On 13 July 2012 11:03, Ricardo Salveti wrote:
> On Fri, Jul 13, 2012 at 2:02 AM, Rajagopal Venkat
> wrote:
> > Can someone consider this patch for merge?
>
> As we will have libpci available at most distros by default, isn't
> there a way of doing run-time detection
Can someone consider this patch for merge?
On 23 June 2012 00:08, Rajagopal Venkat wrote:
> parse cpuidle C state based on sysfs file entry(stateX)
> instead of state name/description
>
> Signed-off-by: Rajagopal Venkat
> ---
> src/cpu/abstract_cpu.cpp |2 +-
> 1 file
Can someone consider this patch for merge?
On 25 June 2012 22:44, Rajagopal Venkat wrote:
> disable pci if not supported by host platform. When
> libpci is not found, define a macro which will be
> used for conditional compilation.
>
> Signed-off-by: Rajagopal Venkat
> -
add powertop test cases into pm-qa. Run
the powertop sanity test to check if tool
is available. If yes, then run powertop in
report generation mode and validate the output.
Signed-off-by: Rajagopal Venkat
---
Makefile |1 +
powertop/Makefile| 25
add powertop test cases into pm-qa. Run
the powertop sanity test to check if tool
is available. If yes, then run powertop in
report generation mode and validate the output.
Signed-off-by: Rajagopal Venkat
---
Makefile |1 +
powertop/Makefile| 25
add powertop test cases into pm-qa. Run the powertop sanity
test to check if tool is available. If yes, then run
powertop in report generation mode and validate the output.
Signed-off-by: Rajagopal Venkat
---
Makefile |1 +
powertop/Makefile| 25
On 2 July 2012 23:40, Amit Kucheria wrote:
> On Mon, Jul 2, 2012 at 9:13 PM, Rajagopal Venkat
> wrote:
> > add powertop test cases into pm-qa. Run the powertop sanity
> > test to check if tool is available. If yes, then run
> > powertop in report generation mode
add powertop test cases into pm-qa. Run the powertop sanity
test to check if tool is available. If yes, then run
powertop in report generation mode and validate the output.
Signed-off-by: Rajagopal Venkat
---
Makefile |1 +
powertop/Makefile| 25
run sanity test for each functionality if present.
If functionality enabled, then run all respective
test cases. This patch also adds sanity checks for
cpuidle and sched_mc.
Signed-off-by: Rajagopal Venkat
---
Test.mk| 17 ++---
cpuidle/cpuidle_sanity.sh
On 2 July 2012 13:20, Hongbo Zhang wrote:
>
>
> On 28 June 2012 00:55, Rajagopal Venkat wrote:
>
>> From: root
>>
> It seems that you did this work on the snowball.
> the git is not completely configed?
>
> Yes. Thanks for pointing this out. I will submit th
From: root
run sanity test for each functionality if present.
If functionality enabled, then run all respective
test cases. This patch also adds sanity checks for
cpuidle and sched_mc.
Signed-off-by: Rajagopal Venkat
---
Test.mk| 17 ++---
cpuidle
disable pci if not supported by host platform. When
libpci is not found, define a macro which will be
used for conditional compilation.
Signed-off-by: Rajagopal Venkat
---
configure.ac |5 +++--
src/lib.cpp | 20 ++--
src/lib.h|5 +
3 files changed, 26
On 25 June 2012 21:34, Arjan van de Ven wrote:
> On 6/25/2012 9:00 AM, Rajagopal Venkat wrote:
>
>
>
> Ok. Taken care.
>
> >
> > diff --git a/src/lib.h b/src/lib.h
> > index 588c023..d354151 100644
> > --- a/src/lib.h
> > +++ b/src/lib.h
Signed-off-by: Rajagopal Venkat
---
configure.ac |5 +++--
src/lib.cpp | 20 ++--
src/lib.h|4
3 files changed, 25 insertions(+), 4 deletions(-)
diff --git a/configure.ac b/configure.ac
index 4da4eea..3cbc7b0 100644
--- a/configure.ac
+++ b/configure.ac
On 23 June 2012 01:31, Arjan van de Ven wrote:
> On 6/22/2012 11:42 AM, Rajagopal Venkat wrote:
> > +case "$host" in
> > +arm*)
> > + AC_DEFINE([HAVE_NO_PCI],[1],[Define if host platform is ARM])
> > + ;;
> > +*)
>
Signed-off-by: Rajagopal Venkat
---
configure.ac | 16 +---
src/lib.cpp | 20 ++--
src/lib.h|4
3 files changed, 35 insertions(+), 5 deletions(-)
diff --git a/configure.ac b/configure.ac
index 4da4eea..c2ff430 100644
--- a/configure.ac
+++ b
parse cpuidle C state based on sysfs file entry(stateX)
instead of state name/description
Signed-off-by: Rajagopal Venkat
---
src/cpu/abstract_cpu.cpp |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/cpu/abstract_cpu.cpp b/src/cpu/abstract_cpu.cpp
index cd4eba0
From: Rajagopal Venkat
The updated version of these test scripts are
available in their respective directories.
Signed-off-by: Rajagopal Venkat
---
run_template |7 --
testcases.awk | 40 --
testcases/Makefile
94 matches
Mail list logo
