Patch to bind devfreq to runtime pm framework. The device
devfreq is automatically suspended with pm_runtime_suspend()
and resumed with pm_runtime_resume().
Discussed at http://comments.gmane.org/gmane.linux.linaro.devel/13787
Rajagopal Venkat (2):
PM / devfreq: Fix compiler warnings
PM
Fix compiler warnings generated when devfreq is not enabled
(CONFIG_PM_DEVFREQ is not set).
Signed-off-by: Rajagopal Venkat
---
include/linux/devfreq.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
index
.
pm_runtime_resume(dev) will resume device devfreq(if available) after
device is resumed from runtime pm core.
Signed-off-by: Rajagopal Venkat
---
drivers/base/power/runtime.c | 18 ++-
drivers/devfreq/devfreq.c| 51 ++
include/linux/devfreq.h
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
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.
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
On 5 February 2013 15:15, MyungJoo Ham wrote:
> - Added missing ABI documents
> - Added comments to clarify the objectives of functions
>
> Signed-off-by: MyungJoo Ham
Acked-by: Rajagopal Venkat
> ---
> Documentation/ABI/testing/sysfs-class-devfreq | 20 +
On 3 April 2013 23:46, Kevin Hilman wrote:
> Rajagopal Venkat writes:
>
>> Devfreq core suspend/resume of a device is explicitly handled
>> by devfreq driver through devfreq_suspend_device() and
>> devfreq_resume_device() apis typically called from runtime
>> suspen
On 3 April 2013 23:46, Kevin Hilman wrote:
> Rajagopal Venkat writes:
>
>> Devfreq core suspend/resume of a device is explicitly handled
>> by devfreq driver through devfreq_suspend_device() and
>> devfreq_resume_device() apis typically called from runtime
>> suspen
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
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
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
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
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
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
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
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
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
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
- 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
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
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
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
- 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
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
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
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
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 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: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
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
me is done automatically from runtime
core, this patch removes the existing devfreq_suspend_device() and
devfreq_resume_device() apis.
Signed-off-by: Rajagopal Venkat
Changes from V2:
Updated change log to clarify patch deals with runtime suspend/resume
Changes from v1:
Improved change lo
On 21 March 2013 20:32, Alan Stern wrote:
> On Thu, 21 Mar 2013, Rajagopal Venkat wrote:
>
>> Allow device devfreq to be suspend/resume automatically with
>> runtime pm suspend/resume. The devfreq drivers should be least
>> cared when to suspend/resume the devfreq.
>
On 22 March 2013 23:04, Kevin Hilman wrote:
> Hi Rajagopal,
>
> Rajagopal Venkat writes:
>
>> Allow device devfreq to be suspend/resume automatically with
>> runtime pm suspend/resume. The devfreq drivers should be least
>> cared when to suspend/resume the devfre
Fix compiler warnings generated when devfreq is not enabled
(CONFIG_PM_DEVFREQ is not set).
Signed-off-by: Rajagopal Venkat
---
include/linux/devfreq.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
index
me-pm,
this patch removes the existing devfreq_suspend_device() and
devfreq_resume_device() apis.
Signed-off-by: Rajagopal Venkat
---
drivers/base/power/runtime.c | 21 -
drivers/devfreq/devfreq.c| 69 +++---
include/linux/devfreq.h |
on pm_runtime_resume().
Discussed at http://comments.gmane.org/gmane.linux.linaro.devel/13787
Changes from v1:
- improved change log and code comments
- added NULL check for devfreq runtime-pm callbacks
-
Rajagopal Venkat (2):
PM / devfreq: Fix compiler warnings
PM / devfreq: tie suspend
On 1 April 2013 12:06, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> Add pm_runtime support to the TI Davinci VPIF driver.
>
> Signed-off-by: Lad, Prabhakar
> Cc: Mauro Carvalho Chehab
> Cc: Hans Verkuil
> Cc: Laurent Pinchart
> Cc: Sakari Ailus
> Cc: Sekhar Nori
> ---
> Changes for v2:
On 1 April 2013 13:53, Prabhakar Lad wrote:
> On Mon, Apr 1, 2013 at 12:47 PM, Rajagopal Venkat
> wrote:
>> On 1 April 2013 12:06, Prabhakar lad wrote:
>>> From: Lad, Prabhakar
>>>
>>> Add pm_runtime support to the TI Davinci VPIF driver.
>>>
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
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
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 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
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: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
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 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
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
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
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
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
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
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 | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff
On 9 January 2013 17:36, Abhilash Kesavan wrote:
> Exynos5-bus device devfreq driver monitors PPMU counters and
> adjusts operating frequencies and voltages with OPP. ASV should
> be used to provide appropriate voltages as per the speed group
> of the SoC rather than using a constant 1.025V.
>
> S
58 matches
Mail list logo
