To: Jean Pihet
Cc: linux-omap@vger.kernel.org; Jean Pihet-XID
Subject: RE: [RFC/PATCH] OMAP3: run the ASM sleep code from DDR
-Original Message-
From: Jean Pihet [mailto:jean.pi...@newoldbits.com]
Sent: Tuesday, February 01, 2011 4:53 PM
To: Santosh Shilimkar
Cc: linux-omap
is not loaded and the user attempts to
suspend?
In that case suspend_ops is NULL and suspending has no effect
(pm_suspend returns -ENODEV).
Note that this also happens after the module unload.
Is that the expected behavior?
Rafael
Regards,
Jean
Reported-by: Jean Pihet j-pi...@ti.com
Signed
code as well.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Agree!
Acked-by: Jean Pihet j-pi...@ti.com
Regards
Santosh
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
changed, 2 insertions(+), 127 deletions(-)
...
OK for this change. Is it the intention to use the omapconf tool as
the replacement for the regs dump code?
Acked-by: Jean Pihet j-pi...@ti.com
Regards,
Jean
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body
+
- userspace /dev/mem-based tools (like omapconf) can do this much better
Fully agree and indeed it doesn't scale for OMAP4.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Ok. Same comment about the use of omaconf as a debug/investigation tool.
Acked-by: Jean Pihet j-pi...@ti.com
are eventually converted to be a driver, the wakeup
timer feature can be made to be a driver-specific feature using the
driver's suspend method.
Excellent idea and patch. Never crossed my mind that we could
have used CLOCK_EVT_MODE_SHUTDOWN instead of our long old
hack.
Great!
Acked-by: Jean
On Fri, May 27, 2011 at 1:02 AM, Kevin Hilman khil...@ti.com wrote:
Inspired by Jean's work to move PM code to modules, I decided it's
time to remove a bunch of ugly and difficult to maintain code from PM
debug.
Indeed this code is a spaghetti mess and makes pm-debug difficult to
be
On Fri, May 27, 2011 at 1:02 AM, Kevin Hilman khil...@ti.com wrote:
Remove the OMAP-specific PM debug 'sleep_while_idle' feature which is
currently available as an OMAP-specific debugfs entry.
This duplicates existing ARM-generic functionality available as a
boot-time option using the boot
On Fri, May 27, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Provide omap_pm_tick_nohz_get_sleep_length_us so that the code
from the OMAP PM modules can use it.
Signed-off-by: Jean Pihet j-pi...@ti.com
This patch
On Fri, May 27, 2011 at 1:09 AM, Kevin Hilman khil...@ti.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Export the suspend_set_ops API as omap_pm_suspend_set_ops in the pm
generic code, under CONFIG_SUSPEND.
Note -hack warning-: since
On Fri, May 27, 2011 at 5:26 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
On Fri, May 27, 2011 at 1:02 AM, Kevin Hilman khil...@ti.com wrote:
Remove the OMAP-specific PM debug 'sleep_while_idle' feature which is
currently available as an OMAP-specific
Hi Santosh,
On Thu, May 19, 2011 at 10:04 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On 5/18/2011 11:02 PM, jean.pi...@newoldbits.com wrote:
From: Jean Pihetj-pi...@ti.com
Provide the the assembly function v7_flush_dcache_all to the
OMAP3 PM module, under CONFIG_CPU_V7.
Hi Santosh,
On Thu, May 19, 2011 at 9:59 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Jean,
On 5/18/2011 11:02 PM, jean.pi...@newoldbits.com wrote:
From: Jean Pihetj-pi...@ti.com
Provide omap_pm_tick_nohz_get_sleep_length_us so that the code
from the OMAP PM modules can use it.
From: Jean Pihet j-pi...@ti.com
First attempt at isolation of the OMAP2+ PM code
RFC quality code but successfully tested on board as a proof
of concept
1) provide PM functionality as modules
To allow for the PM functionality to be built and used as modules a
clean-up and isolation task first
From: Jean Pihet j-pi...@ti.com
If used in a module both tracepoints need to be exported by the
kernel.
Fixed a typo in CONFIG_EVENT_POWER_TRACING_DEPRECATED to really
export the tracepoints.
Signed-off-by: Jean Pihet j-pi...@ti.com
Acked-by: Ingo Molnar mi...@elte.hu
Cc: Thomas Renninger tr
From: Jean Pihet j-pi...@ti.com
Isolate the PM code under CONFIG_PM. This includes the following:
- core PM,
- powerdomain,
- clockdomain,
- smartreflex,
- voltagedomain,
- OPP.
This cleans up the PM code in order to allow it to be built as a
module.
Signed-off-by: Jean Pihet j-pi...@ti.com
From: Jean Pihet j-pi...@ti.com
Clean-up SRAM functions usage to better isolate PM code, in order
to allow it to be used as a module.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/pm34xx.c |1 +
arch/arm/plat-omap/sram.c|2 --
2 files changed, 1 insertions(+), 2
From: Jean Pihet j-pi...@ti.com
Register the board specific cpuidle C-states table for the cpuidle driver
to use it later at cpuidle init time.
This also cleans up the cpuidle code, in order to allow it to be used
as a module.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2
From: Jean Pihet j-pi...@ti.com
This patch provides the omap3_save_scratchpad_contents function as
a service from the common control code.
The PM code calls the service to store the appropriate data in the
scratchpad area, including the restore pointer from OFF/OSWR modes
and the secure RAM
From: Jean Pihet j-pi...@ti.com
Move the powerdomains time accounting code from in pm-debug to the
powerdomain code. The pm-debug code only displays the information on
request.
This also cleans up the core PM code, in order to allow it to be used
as a module.
Signed-off-by: Jean Pihet j-pi
From: Jean Pihet j-pi...@ti.com
Move variables and functions that are by the arch code to the common
pm.c code.
Moved:
. PM knobs variables:
- enable_off_mode
- omap2_pm_debug
- sleep_while_idle
- wakeup_timer_seconds
- wakeup_timer_milliseconds
. omap2_pm_wakeup_on_timer function
From: Jean Pihet j-pi...@ti.com
Provide omap_pm_tick_nohz_get_sleep_length_us so that the code
from the OMAP PM modules can use it.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/pm-debug.c |7 ---
arch/arm/mach-omap2/pm.c | 15 +++
arch/arm/mach
From: Jean Pihet j-pi...@ti.com
Export the suspend_set_ops API as omap_pm_suspend_set_ops in the pm
generic code, under CONFIG_SUSPEND.
Note -hack warning-: since the 'suspend_valid_only_mem' function is
not exported to modules, fill the 'valid' field value of
'struct platform_suspend_ops
From: Jean Pihet j-pi...@ti.com
Provide the the assembly function v7_flush_dcache_all to the
OMAP3 PM module, under CONFIG_CPU_V7.
v7_flush_dcache_all is used by the low level sleep code.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/pm.c |4
arch/arm/mach-omap2/pm.h
From: Jean Pihet j-pi...@ti.com
Addition of EXPORT_SYMBOL for functions and variables used by
the code in PM modules.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/kernel/setup.c|1 +
arch/arm/kernel/smp_tlb.c |2 ++
arch/arm/mach-omap2/clockdomain.c |7
From: Jean Pihet j-pi...@ti.com
Clean-up of used resources to allow clean insertion and removal
of the PM modules.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/cpuidle34xx.c | 14 +-
arch/arm/mach-omap2/pm-debug.c| 22 +-
arch/arm/mach
From: Jean Pihet j-pi...@ti.com
A new config option CONFIG_OMAP_PM is defined. This option allows
for the whole OMAP2+ PM to completely enabled, disabled or be built
as modules.
The PM functionality is split into the following modules:
- omap_pm_debug
- omap2_pm
- omap3_pm
- omap4_pm
On Thu, May 12, 2011 at 7:45 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
This version fixes the davinci pm free, and adds updates for the
davinci pcm driver. As I don't know what's happening with Jean's
patch tweaking the genpool allocator, I've kept my version.
Sorry
On Fri, May 13, 2011 at 11:11 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, May 13, 2011 at 09:30:14AM +0200, Jean Pihet wrote:
On Thu, May 12, 2011 at 7:45 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
This version fixes the davinci pm free, and adds
Adding l-o and linux-pm MLs. The original post is at
http://www.spinics.net/lists/kernel/msg1186554.html
On Fri, May 13, 2011 at 4:48 PM, Ingo Molnar mi...@elte.hu wrote:
* jean.pi...@newoldbits.com jean.pi...@newoldbits.com wrote:
From: Jean Pihet j-pi...@ti.com
If used in a module both
From: Jean Pihet j-pi...@ti.com
Rework of the OMAP2+ cpuidle code
v3: rework after comments on linux-omap ML:
- renamed the C-state driver data variables as 'cx',
- retain C1 as the only always valid state and safe state,
- rework of the C-states definition.
v2: rework after comments on linux
From: Jean Pihet j-pi...@ti.com
- sleep_latency and wake_latency are not used, replace them by
exit_latency which is used by cpuidle. exit_latency simply is
the sum of sleep_latency and wake_latency,
- replace threshold by target_residency,
- changed the OMAP3 specific cpuidle code
From: Jean Pihet j-pi...@ti.com
The current implementation defines an internal structure and a
C-states array. Using those structures is redundant to the
structs used by the cpuidle framework.
This patch provides a clean-up of the internal struct, removes the
internal C-states array, stores
From: Jean Pihet j-pi...@ti.com
- fix single and multi-lines comments format
- removed the omap3_idle_bm_check function and replaced the test
in omap3_enter_idle_bm by the equivalent code
- re-organize omap3_enter_idle_bm code path, assign local variables
only when needed
- reword some
From: Jean Pihet j-pi...@ti.com
The achievable power modes of the power domains in cpuidle
depends on the system wide 'enable_off_mode' knob in debugfs.
Upon changing enable_off_mode, do not change the C-states
'valid' field but instead dynamically restrict the power modes
when entering idle
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed.
OMAP_PM_NOOP is enabled by default by Kconfig.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/plat-omap/Kconfig
Please note that this code is based on khilman's for_2.6.40/pm-cleanup branch.
Jean
On Fri, May 6, 2011 at 11:11 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer
Hi Paul,
On Fri, May 6, 2011 at 6:16 PM, Paul Walmsley p...@pwsan.com wrote:
Salut Jean
On Fri, 6 May 2011, Jean Pihet wrote:
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed
From: Jean Pihet j-pi...@ti.com
Rework of the OMAP2+ cpuidle code
v2: rework after comments on linux-omap ML:
- remove useless macros,
- replace the C-state common data fill-in helper macro by an inline
function, for better readability,
- update commits description.
v1:
- optimize
From: Jean Pihet j-pi...@ti.com
- sleep_latency and wake_latency are not used, replace them by
exit_latency which is used by cpuidle. exit_latency simply is
the sum of sleep_latency and wake_latency,
- replace threshold by target_residency,
- changed the OMAP3 specific cpuidle code
From: Jean Pihet j-pi...@ti.com
The current implementation defines an internal structure and a
C-states array. Using those structures is redundant to the
structs used by the cpuidle framework.
This patch provides a clean-up of the internal struct, removes the
internal C-states array, stores
From: Jean Pihet j-pi...@ti.com
- fix single and multi-lines comments format
- removed the omap3_idle_bm_check function and replaced the test
in omap3_enter_idle_bm by the equivalent code
- re-organize omap3_enter_idle_bm code path, assign local variables
only when needed
- reword some
From: Jean Pihet j-pi...@ti.com
The achievable power modes of the power domains in cpuidle
depends on the system wide 'enable_off_mode' knob in debugfs.
Upon changing enable_off_mode, do not change the C-states
'valid' field but instead dynamically restrict the power modes
when entering idle
From: Jean Pihet j-pi...@ti.com
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API by
creating a unified API which calls omap_device_set_dev_constraint
for all classes of constraints (devices wake-up latency, devices
throughput...).
The implementation of the constraints framework
From: Jean Pihet j-pi...@ti.com
When a wake-up latency constraint is requested or removed the omap device
layer dispatches the updated strongest constraint value to the
corresponding power domain.
The power domains get the next power state programmed directly in the
registers via
From: Jean Pihet j-pi...@ti.com
Hwmod is queried from the omap device layer to manage the power domains
wake-up latency constraints. Hwmod retrieves the correct power domain
and if it exists it calls the corresponding power domain function.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up
From: Jean Pihet j-pi...@ti.com
Defined values in the enum:
- OMAP_PM_CONSTRAINT_WKUP_LAT
- OMAP_PM_CONSTRAINT_THROUGHPUT
More classes can be added later if needed.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean Pihet j-pi
From: Jean Pihet j-pi...@ti.com
Created arch/arm/plat-omap/omap-pm-constraints.c file from
arch/arm/plat-omap/omap-pm-noop.c and the associated Kconfig option
OMAP_PM_CONSTRAINTS.
Based on the original patch from Vishwanath,
cf. https://patchwork.kernel.org/patch/327312/
Cc: Vishwanath BS
From: Jean Pihet j-pi...@ti.com
Figures are added to the power domains structs.
Note: the figures are preliminary figures. More accurate measurements
are needed. Also the conditions of measurements shall be investigated
and described.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency
From: Jean Pihet j-pi...@ti.com
The code at omap device level manages the constraints: storage,
tracking of requesters and dispatching to the low level
code (e.g. powerdomain for the wake-up latency constraints).
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU
From: Jean Pihet j-pi...@ti.com
Implement the wake-up latency constraints using an internal
unified function _set_dev_constraint at OMAP PM level,
which calls the corresponding function at omap device level.
The actual constraints management code is at the omap device level.
Note: the bus
From: Jean Pihet j-pi...@ti.com
The powerdomains next states are initialized in pwrdms_setup as a
late_initcall. Because the wake-up constraint can be requested
early in the boot sequence, the power domains next states can be
overwritten by pwrdms_setup.
This patch fixes it by initializing
On Thu, Apr 14, 2011 at 2:27 PM, Lesly A M lesl...@ti.com wrote:
Patch series for TWL4030 power scripts and workaround for TWL erratum 27.
Changes for implementing TWL4030 power scripts recommended by hardware team.
Introduced a new TWL4030 power script file, which can be used by different
From: Jean Pihet j-pi...@ti.com
Rework the cpuidle code:
- optimize the cpuidle C-states data registration and storage,
- change the interaction with the debugfs 'enable_off_mode' knob
and the use of the C-states 'valid' internal field,
- remove dead code,
- improve code readability.
Tested
From: Jean Pihet j-pi...@ti.com
- sleep_latency and wake_latency are not used, replace them by
exit_latency which is used by cpuidle. exit_latency simply is
the sum of sleep_latency and wake_latency,
- replace threshold by target_residency,
- changed the OMAP3 specific cpuidle code
From: Jean Pihet j-pi...@ti.com
The achievable power modes of the power domains in cpuidle
depends on the system wide 'enable_off_mode' knob in debugfs.
Upon changing enable_off_mode, do not change the C-states
'valid' field but instead dynamically restrict the power modes
when entering idle
From: Jean Pihet j-pi...@ti.com
The current implementation defines an internal structure and a
C-states array. Using those structures is redundant to the
structs used by the cpuidle framework.
This patch provides a clean-up of the internal struct, removes the
internal C-states array, stores
From: Jean Pihet j-pi...@ti.com
The cpuidle states settings can be overriden by some board-
specific settings, by calling omap3_pm_init_cpuidle.
Remove the 3430SDP specific states settings registration
since the figures are identical to the default ones (in cpuidle34xx.c).
Signed-off-by: Jean
From: Jean Pihet j-pi...@ti.com
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/cpuidle34xx.c | 52 +---
1 files changed, 19 insertions(+), 33 deletions(-)
diff --git a/arch/arm/mach-omap2/cpuidle34xx.c
b/arch/arm/mach-omap2/cpuidle34xx.c
Hi Santosh,
On Fri, Apr 29, 2011 at 1:29 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On 4/29/2011 2:56 PM, jean.pi...@newoldbits.com wrote:
From: Jean Pihetj-pi...@ti.com
The achievable power modes of the power domains in cpuidle
depends on the system wide 'enable_off_mode' knob
From: Jean Pihet j-pi...@ti.com
Created arch/arm/plat-omap/omap-pm-constraints.c file from
arch/arm/plat-omap/omap-pm-noop.c and the associated Kconfig option
OMAP_PM_CONSTRAINTS.
Based on the original patch from Vishwanath,
cf. https://patchwork.kernel.org/patch/327312/
Cc: Vishwanath BS
From: Jean Pihet j-pi...@ti.com
When a wake-up latency constraint is requested or removed the omap device
layer dispatches the updated strongest constraint value to the
corresponding power domain.
The power domains get the next power state programmed directly in the
registers via
From: Jean Pihet j-pi...@ti.com
Figures are added to the power domains structs.
Note: the figures are preliminary figures. More accurate measurements
are needed. Also the conditions of measurements shall be investigated
and described.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency
From: Jean Pihet j-pi...@ti.com
Hwmod is queried from the omap device layer to manage the power domains
wake-up latency constraints. Hwmod retrieves the correct power domain
and if it exists it calls the corresponding power domain function.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up
From: Jean Pihet j-pi...@ti.com
The code at omap device level manages the constraints: storage,
tracking of requesters and dispatching to the low level
code (e.g. powerdomain for the wake-up latency constraints).
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU
From: Jean Pihet j-pi...@ti.com
Implement the wake-up latency constraints using an internal
unified function _set_dev_constraint at OMAP PM level,
which calls the corresponding function at omap device level.
The actual constraints management code is at the omap device level.
Note: the bus
From: Jean Pihet j-pi...@ti.com
Defined values in the enum:
- OMAP_PM_CONSTRAINT_WKUP_LAT
- OMAP_PM_CONSTRAINT_THROUGHPUT
More classes can be added later if needed.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean Pihet j-pi
From: Jean Pihet j-pi...@ti.com
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API by
creating a unified API which calls omap_device_set_dev_constraint
for all classes of constraints (devices wake-up latency, devices
throughput...).
The implementation of the constraints framework
From: Jean Pihet j-pi...@ti.com
The powerdomains next states are initialized in pwrdms_setup as a
late_initcall. Because the wake-up constraint can be requested
early in the boot sequence, the power domains next states can be
overwritten by pwrdms_setup.
This patch fixes it by initializing
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
This series is the begining of a voltage layer cleanup and restruture
with the primary goal of splitting up voltage domain, voltage
processor (VP) and voltage controller (VC) code.
It would be nice to give a bit more detail on
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
The voltage domain pointer currently in struct omap_hwmod is not used
and does not belong here. Instead, voltage domains will be associated
Extra space
with powerdomains in forthcoming patches.
Acked-by: Paul Walmsley
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
Start cleaning up the voltage layer to have a voltage domain layer
that resembles thae structure of the existing clock and power domain
s/thae/the
layers. To that end:
Extra space
- move the 'struct voltagedomain' out of
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
Add voltage domain name to indicate which voltagedomain each
powerdomain is in. A missing voltage domain name means that that
powerdomain is not in one of the currently scalable voltage domains.
Is that the role of the
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
When a powerdomain is registered, lookup the voltage domain by name
and keep a pointer to the containing voltagedomain in the powerdomain
structure.
Modeled after similar method between powerdomain and clockdomain layers.
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
When a powerdomain is registered and it has an associated voltage domain,
add the powerdomain to the voltagedomain using voltdm_add_pwrdm().
Also add voltagedomain iterator helper functions to iterate over all
registered
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
As part of the voltage layer cleanup, split out VC specific code into
a dedicated VC layer. This patch primarily just moves VC code from
voltage.c into vc.c, and adds prototypes to vc.h.
No functional changes.
For
On Fri, Mar 25, 2011 at 4:48 PM, Kevin Hilman khil...@ti.com wrote:
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
Start cleaning up the voltage layer to have a voltage domain layer
that resembles thae structure
On Fri, Mar 25, 2011 at 4:51 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
On Thu, Mar 24, 2011 at 1:00 AM, Kevin Hilman khil...@ti.com wrote:
Add voltage domain name to indicate which voltagedomain each
powerdomain is in. A missing voltage domain name
On Fri, Mar 25, 2011 at 4:56 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
[...]
+
+/**
+ * voltdm_for_each - call function on each registered voltagedomain
+ * @fn: callback function *
+ *
+ * Call the supplied function @fn for each registered
finding this one David.
Great!
Acked-by: Jean Pihet j-pi...@ti.com
Thanks,
Jean
---
arch/arm/mach-omap2/board-omap4panda.c | 28
1 files changed, 0 insertions(+), 28 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
b/arch/arm/mach-omap2/board
Hi Kevin,
On Fri, Mar 11, 2011 at 1:59 AM, Kevin Hilman khil...@ti.com wrote:
Tony,
Please pull the following OMAP PM related changes for the upcoming
2.6.39 merge window.
Kevin
The following changes since commit a5abba989deceb731047425812d268daf7536575:
Linux 2.6.38-rc8 (2011-03-07
On Fri, Mar 11, 2011 at 5:32 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
Hi Kevin,
On Fri, Mar 11, 2011 at 1:59 AM, Kevin Hilman khil...@ti.com wrote:
Tony,
Please pull the following OMAP PM related changes for the upcoming
2.6.39 merge window
Hi Paul,
On Thu, Mar 10, 2011 at 2:04 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 3 Mar 2011, Jean Pihet wrote:
The patch adds the new power management trace points for
the OMAP architecture.
The trace points are for:
- default idle handler. Since the cpuidle framework
Hi Paul,
On Thu, Mar 10, 2011 at 5:03 AM, Paul Walmsley p...@pwsan.com wrote:
Hello Jean
Thanks for working on this stuff. Some comments based on a quick look...
On Wed, 9 Mar 2011, Jean Pihet wrote:
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API by
creating a unified API
constraints.
Jean Pihet (7):
OMAP PM: create a PM layer plugin for per-device constraints
OMAP: PM CONSTRAINTS: add an enum for the classes of constraint
OMAP: PM CONSTRAINTS: implement wake-up latency constraints
OMAP: PM CONSTRAINTS: implement the constraints management code
OMAP: PM
-by: Jean Pihet j-pi...@ti.com
---
arch/arm/plat-omap/Kconfig |7 +
arch/arm/plat-omap/Makefile |1 +
arch/arm/plat-omap/omap-pm-constraints.c | 363 ++
3 files changed, 371 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/plat
but currently is
a no-op.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/plat-omap/omap-pm-constraints.c | 174 --
1 files changed, 91 insertions(+), 83 deletions
The code at omap device level manages the constraints: storage,
tracking of requesters and dispatching to the low level
code (e.g. powerdomain for the wake-up latency constraints).
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean
.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/omap_hwmod.c | 29 +-
arch/arm/plat-omap/include/plat/omap_hwmod.h |1 +
2 files changed, 29 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2
.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/powerdomains3xxx_data.c | 63 +++
1 files changed, 63 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/powerdomains3xxx_data.c
b/arch/arm/mach-omap2/powerdomains3xxx_data.c
index e1bec56
the next power
state via cpuidle, which get the strongest wake-up latency constraint
by querying PM QOS. The usage of PM QOS is temporary, until a generic
solution is in place.
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean Pihet j-pi
constraint
by querying PM QOS. The usage of PM QOS is temporary, until a generic
solution is in place.
Based on Vibhore's original patch, adapted to omap_device, omap_hwmod
and PM QOS frameworks.
Signed-off-by: Jean Pihet j-pi...@ti.com
Cc: Vibhore Vardhan vvard...@ti.com
---
arch/arm/mach-omap2
Hi,
This patch is sent as en early review request, the testing is still on-going.
I will post the updated series (with a new revision number) as soon as possible.
I have some inlined comments, questions and concerns about it.
Can you please check?
On Wed, Mar 9, 2011 at 8:19 PM, Jean Pihet
On Tue, Mar 8, 2011 at 3:15 AM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat API by
creating similar APIs at the omap_device and omap_hwmod levels. The
omap_hwmod level call is the layer with access
---
Looks good.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Great!
Acked-by: Jean Pihet j-pi...@ti.com
Thanks,
Jean
arch/arm/mach-omap2/devices.c | 82
+++-
arch/arm/plat-omap/include/plat/omap44xx.h | 2 +
2 files changed, 81 insertions
-by: Jean Pihet j-pi...@ti.com
---
Based on khilman's pm-core branch
arch/arm/plat-omap/Kconfig |7 +
arch/arm/plat-omap/Makefile |1 +
arch/arm/plat-omap/omap-pm-constraints.c | 363 ++
3 files changed, 371 insertions(+), 0 deletions
to omap_device, omap_hwmod
and PM QOS frameworks.
Signed-off-by: Jean Pihet j-pi...@ti.com
Cc: Vibhore Vardhan vvard...@ti.com
---
Based on khilman's pm-core branch
arch/arm/mach-omap2/omap_hwmod.c | 62 -
arch/arm/mach-omap2/powerdomain.c | 197
pwrdm_wakeuplat_update_pwrst.
Note about PM QOS: the MPU and CORE power domains get the next power
state via cpuidle, which get the strongest wake-up latency constraint
by querying PM QOS. The usage of PM QOS is temporary, until a generic
solution is in place.
Jean Pihet (2):
OMAP PM: create a PM layer
clocks changes (enable, disable, set_rate),
- power domain states: the desired target state and -if different-
the actually hit state.
Because of the generic nature of the changes, OMAP3 and OMAP4 are supported.
Tested on OMAP3 with suspend/resume, cpuidle, basic DVFS.
Signed-off-by: Jean Pihet
Message-
From: Jean Pihet [mailto:jean.pi...@newoldbits.com]
Sent: Monday, February 21, 2011 2:14 PM
To: Santosh Shilimkar
Cc: Kevin Hilman; Thomas Renninger; linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Jean Pihet-XID
Subject: Re: [PATCH] perf: add OMAP support
601 - 700 of 931 matches
Mail list logo
