Kevin,
On Tue, Dec 14, 2010 at 5:12 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Clean up of the ASM code:
- reorganized the code in logical sections: defines, API
functions, internal functions and variables
,
- changed the hardcoded values in favor of existing macros
from include files,
- clean up of non used symbols.
Tested on OMAP3EVM and Beagleboard with full RET and OFF modes,
using cpuidle and suspend.
Based on original patch from Vishwa.
Signed-off-by: Jean Pihet j-pi...@ti.com
Cc: Vishwanath BS
From: Jean Pihet j-pi...@ti.com
This patch only contains clean-ups and cosmetic changes,
no functional change.
Clean up of the ASM code:
- reorganized the code in logical sections: defines, API
functions, internal functions and variables,
- reworked and simplified the execution paths
: Jean Pihet [mailto:jean.pi...@newoldbits.com]
Sent: Tuesday, December 14, 2010 2:53 PM
To: Kevin Hilman; Vishwanath BS
Cc: linux-omap@vger.kernel.org; Jean Pihet
Subject: Re: [PATCH] OMAP3: clean up ASM idle code
Kevin,
On Tue, Dec 14, 2010 at 5:12 AM, Kevin Hilman
khil
On Sat, Dec 11, 2010 at 10:14 PM, Peter Barada pet...@logicpd.com wrote:
I'm trying to add code to a 2.6.32 kernel to extract the OMAP core
temperature for thermal testing, and section 7.4.6 of the OMAP3 TRM
(spug98g.pdf) explains the CONTROL_TEMP_SENSOR register.
I have not look at it further
From: Jean Pihet j-pi...@ti.com
Provides:
. calls to machine_suspend trace point,
. OMAP support,
. API Documentation
Applies on top of Thomas's 8 latest power trace API patches, cf.
http://marc.info/?l=linux-kernelm=129130827309354w=2
Jean Pihet (3):
perf: add calls to suspend trace point
From: Jean Pihet j-pi...@ti.com
Provides documentation for the following:
- the new power trace API,
- the old (legacy) power trace API,
- the DEPRECATED Kconfig option usage..
Signed-off-by: Jean Pihet j-pi...@ti.com
---
Documentation/trace/events-power.txt | 90
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the calls to disable_hlt at the very
Kevin,
On Thu, Dec 9, 2010 at 12:01 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the calls to disable_hlt at the very
On Thu, Dec 9, 2010 at 7:00 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the calls to disable_hlt at the very
On Wed, Dec 8, 2010 at 2:11 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
sequences. This could
From: Jean Pihet j-pi...@ti.com
Clean up of the ASM code:
- reorganized the code in logical sections: defines, API
functions, internal functions and variables,
- reworked and simplified the execution paths, for better
readability and to avoid duplication of code,
- added comments
Hi Dave,
On Tue, Dec 7, 2010 at 11:16 AM, Dave Martin dave.mar...@linaro.org wrote:
On Tue, Dec 7, 2010 at 6:31 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Dave,
-Original Message-
From: linaro-dev-boun...@lists.linaro.org [mailto:linaro-dev-
boun...@lists.linaro.org] On
during idle, and not during suspend.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Tested OK on Beagleboard with suspend and idle with RET and OFF modes
Tested-by: Jean Pihet j-pi...@ti.com
Thanks,
Jean
---
Applies to Tony's omap-fixes branch
Hello Paul,
On Thu, Dec 2, 2010 at 8:23 AM, Paul Walmsley p...@pwsan.com wrote:
Hello Jean
On Thu, 25 Nov 2010, Jean Pihet wrote:
On Thu, Nov 25, 2010 at 6:35 PM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 25 Nov 2010, Jean Pihet wrote:
On Thu, Nov 25, 2010 at 12:49 AM, Paul Walmsley p
Hi,
On Thu, Nov 25, 2010 at 12:49 AM, Paul Walmsley p...@pwsan.com wrote:
The console semaphore must be held while the OMAP UART devices are
disabled, lest a console write cause an ARM abort (and a kernel crash)
when the underlying console device is inaccessible. These crashes
only occur
On Thu, Nov 25, 2010 at 6:35 PM, Paul Walmsley p...@pwsan.com wrote:
Hello Jean
On Thu, 25 Nov 2010, Jean Pihet wrote:
On Thu, Nov 25, 2010 at 12:49 AM, Paul Walmsley p...@pwsan.com wrote:
The console semaphore must be held while the OMAP UART devices are
disabled, lest a console write
Paul,
On Thu, Nov 25, 2010 at 7:15 PM, Paul Walmsley p...@pwsan.com wrote:
Hi
On Thu, 25 Nov 2010, Jean Pihet wrote:
On Thu, Nov 25, 2010 at 12:49 AM, Paul Walmsley p...@pwsan.com wrote:
The console semaphore must be held while the OMAP UART devices are
disabled, lest a console write
Hilman'
Cc: Nishanth Menon; 'linux-omap'; 'Jean Pihet'; Vishwanath Sripathy;
'Tony'
Subject: RE: [PATCH 00/13] OMAP3: OFF mode fixes
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Kevin Hilman
Sent: Wednesday
(in omap3_pm_begin instead of omap3_pm_prepare),
and the call to enable_hlt at the very end of the suspend sequence
(in omap3_pm_end instead of omap3_pm_finish).
Tested with RET and OFF on Beagle and OMAP3EVM.
Signed-off-by: Jean Pihet j-pi...@ti.com
Cc: Kevin Hilman khil...@deeprootsystems.com
On Mon, Nov 22, 2010 at 11:53 AM, Rajendra Nayak rna...@ti.com wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Jean Pihet
Sent: Monday, November 22, 2010 4:15 PM
To: linux-omap@vger.kernel.org
Cc: Jean Pihet
Hi,
On Mon, Nov 22, 2010 at 12:11 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Nov 22, 2010 at 11:44:57AM +0100, Jean Pihet wrote:
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
sequences
On Mon, Nov 22, 2010 at 5:03 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Peter 'p2' De Schrijver peter.de-schrij...@nokia.com writes:
On Fri, Nov 19, 2010 at 05:14:15PM +0100, ext Derrick, David wrote:
-Original Message-
From: Jean Pihet [mailto:jean.pi...@newoldbits.com
From: Jean Pihet j-pi...@ti.com
Idle path should be disabled during the entire suspend/resume sequence.
Currently it is disabled in -prepare() and re-enabled in -finish(),
but the suspend sequence starts with -begin() and ends with -end(),
leaving windows where the suspend/resume sequence
On Mon, Nov 22, 2010 at 6:51 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
sequences. This could cause
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
From: Richard Woodruff r-woodru...@ti.com
Analysis in TI kernel with ETM showed that using cache mapped flush
in kernel instead of SO mapped flush cost drops by 65% (3.39mS down
to 1.17mS) for clean_l2 which is used during
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
Errata id: i608
RTA (Retention Till Access) feature is not supported and leads to device
stability issues when enabled. This impacts modules with embedded memories
on OMAP3630
Workaround is to disable RTA on boot and coming
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
From: Eduardo Valentin eduardo.valen...@nokia.com
Limitation i583: Self_Refresh Exit issue after OFF mode
Issue:
When device is waking up from OFF mode, then SDRC state machine sends
inappropriate sequence violating JEDEC
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
From: Eduardo Valentin eduardo.valen...@nokia.com
We need to disable the autoidle bit from MPU INTC,
otherwise INTC would get stall, and we would never
come out of WFI. This must be done before save secure ram
as well because
Hi Peter,
On Fri, Nov 19, 2010 at 10:57 AM, Peter 'p2' De Schrijver
peter.de-schrij...@nokia.com wrote:
On Fri, Nov 19, 2010 at 10:46:19AM +0100, ext Jean Pihet wrote:
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
From: Richard Woodruff r-woodru...@ti.com
Analysis
Hi,
On Fri, Nov 19, 2010 at 2:54 AM, Nishanth Menon n...@ti.com wrote:
Bunch of fixes as part of phase 1 targetting mainly OMAP3630 HS devices
for OFF mode logic.
It is important to note - for proper functionality of HS OFF mode on OMAP3630,
CONFIG_OMAP3_L2_AUX_SECURE_SAVE_RESTORE=y and
On Fri, Nov 19, 2010 at 1:12 PM, Nishanth Menon n...@ti.com wrote:
Jean Pihet wrote, on 11/19/2010 04:09 AM:
[...]
diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
index f520b38..c7e2db0 100644
--- a/arch/arm/mach-omap2/pm34xx.c
+++ b/arch/arm/mach-omap2/pm34xx.c
HI Tony,
On Thu, Nov 18, 2010 at 7:34 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
On Thu, Nov 18, 2010 at 7:27 PM, Tony Lindgren t...@atomide.com wrote:
* Jean Pihet jean.pi...@newoldbits.com [101118 10:06]:
On Thu, Nov 18, 2010 at 6:52 PM, Tony Lindgren t...@atomide.com wrote:
About
On Fri, Nov 19, 2010 at 5:14 PM, Derrick, David dderr...@ti.com wrote:
-Original Message-
From: Jean Pihet [mailto:jean.pi...@newoldbits.com]
Sent: Friday, November 19, 2010 9:37 AM
On Thu, Nov 18, 2010 at 7:34 PM, Jean Pihet jean.pi...@newoldbits.com
wrote:
On Thu, Nov 18, 2010 at 7:27
Vishwanath BS vishwanath...@ti.com, Jean Pihet j-pi...@ti.com:
[PATCH 1/2]: OMAP3 PM: move omap3 sleep to ddr
For historical reasons the OMAP3 sleep code is run from SRAM.
This code can run from DDR which provides better performance and
leaves the SRAM available for other uses
-by: Vishwanath BS vishwanath...@ti.com
Cc: Kevin Hillman khil...@deeprootsystems.com
Changed the commit comments.
Cc: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/pm34xx.c |9 +
1 files changed, 1 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm
-by: Vishwanath BS vishwanath...@ti.com
Heavily reworked from Vishwa's original patch.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/control.h |2 +
arch/arm/mach-omap2/pm.h|6 +-
arch/arm/mach-omap2/pm34xx.c|4 +-
arch/arm/mach-omap2/sleep34xx.S | 354
Hi Nishant,
On Thu, Nov 18, 2010 at 4:11 PM, Nishanth Menon n...@ti.com wrote:
-Original Message-
From: Sripathy, Vishwanath [mailto:vishwanath...@ti.com]
Sent: Thursday, November 18, 2010 9:09 AM
To: Nishanth Menon
Cc: Jean Pihet; linux-omap@vger.kernel.org; Kevin Hillman; Jean
On Thu, Nov 18, 2010 at 6:52 PM, Tony Lindgren t...@atomide.com wrote:
* Nishanth Menon n...@ti.com [101118 08:46]:
But after wfi in wait_sdrc_ok as part of the code executing in SRAM
today omap34xx_cpu_suspend - we are waiting for DPLL3 lock prior to
accessing DDR - how do we execute that
On Thu, Nov 18, 2010 at 6:41 PM, Tony Lindgren t...@atomide.com wrote:
* Jean Pihet jean.pi...@newoldbits.com [101118 06:43]:
From: Vishwanath BS vishwanath...@ti.com
Clean up of the ASM code:
- reworked and simplified the execution paths, for better
readability and to avoid duplication
On Thu, Nov 18, 2010 at 7:27 PM, Tony Lindgren t...@atomide.com wrote:
* Jean Pihet jean.pi...@newoldbits.com [101118 10:06]:
On Thu, Nov 18, 2010 at 6:52 PM, Tony Lindgren t...@atomide.com wrote:
About the DPLL lock:
1) wait_sdrc_ok is only called when back from the non-OFF modes,
2) I
From: Jean Pihet jean.pi...@newoldbits.com
Add comments and IDs for the following erratas:
- i540: MPU cannot exit from Standby,
- i478: Unexpected Cold-Reset is generated when device is coming
back from OFF mode
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/irq.c
From: Jean Pihet jean.pi...@newoldbits.com
Add comments and IDs for the following erratas:
- i540: MPU cannot exit from Standby,
- i478: Unexpected Cold-Reset is generated when device is coming
back from OFF mode
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/irq.c
Hi Thomas,
l-o is currently broken wrt to suspend and idle.
Solutions are being worked on for the moment.
Kevin, are there solutions available yet?
Regards,
Jean
On Wed, Nov 10, 2010 at 4:44 PM, Thomas Petazzoni
thomas.petazz...@free-electrons.com wrote:
Hello,
I've updated my tree to the
Hi Kevin,
On Tue, Nov 2, 2010 at 2:38 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
The low power mode on the latest l-o master branch is broken, so I
investigated a bit. Here are the results. This has been tested on
OMAP3EVM and Beagleboard
Hi,
The low power mode on the latest l-o master branch is broken, so I
investigated a bit. Here are the results. This has been tested on
OMAP3EVM and Beagleboard.
The problem is that the CORE does not reach the desired mode (RET,
OFF). It is caused by the I2C1 fclk that is left enabled at
On Tue, Oct 26, 2010 at 1:33 AM, Thomas Renninger tr...@suse.de wrote:
Changes in V2:
- Introduce PWR_EVENT_EXIT instead of 0 to mark non-power state
- Use u32 instead of u64 for cpuid, state which is by far enough
New power trace events:
power:processor_idle
power:processor_frequency
Ingo,
On Tue, Oct 26, 2010 at 9:10 AM, Ingo Molnar mi...@elte.hu wrote:
* Thomas Renninger tr...@suse.de wrote:
Changes in V2:
- Introduce PWR_EVENT_EXIT instead of 0 to mark non-power state
- Use u32 instead of u64 for cpuid, state which is by far enough
...
+#define PWR_EVENT_EXIT
On Sat, Oct 9, 2010 at 8:36 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sat, Oct 9, 2010 at 1:14 AM, Pierre Tardy tar...@gmail.com wrote:
On Sat, Oct 9, 2010 at 8:28 AM, Ingo Molnar mi...@elte.hu wrote:
The thing is, Arjan is 100% right that a library for this is not a
On Sat, Oct 9, 2010 at 8:55 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
Kevin,
On Sat, Oct 9, 2010 at 12:47 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Kevin Hilman khil...@deeprootsystems.com writes:
...
Since only one part of the original patch introduced a bug, I decided
Kevin,
On Sat, Oct 9, 2010 at 12:47 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Kevin Hilman khil...@deeprootsystems.com writes:
Jean Pihet jean.pi...@newoldbits.com writes:
This patch reverts commit 914bab936fe0388a529079679e2f137aa4ff548d, which
breaks the OFF mode on the OMAP3
and config used?
Jean
---
From ec85bc90978cf0f257e73eaad593ffb774595863 Mon Sep 17 00:00:00 2001
From: Jean Pihet jean.pi...@newoldbits.com
Date: Fri, 8 Oct 2010 18:36:48 +0200
Subject: [PATCH] Revert OMAP: mach-omap2: Fix incorrect assignment warnings
This reverts commit
Hi,
On Thu, Oct 7, 2010 at 2:33 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
Hi,
Latest linux-omap/master branch is not booting up on OMAP3EVM board, I am
using omap2plus_defcofnig without any changes.
I tried enableing early_printk option then found that it is hanging
immediately after
2010 17:20:57 Jean Pihet wrote:
Here is a re-spin of the patches after discussion.
what is going to happen here now?
Is this supposed to go through Ingo's tree?
Ingo: do you mind commenting on this.
Meanwhile, here are some ideas...
I see 3 possibilities:
1) Power (or all) perf
Thomas,
On Thu, Oct 7, 2010 at 5:49 PM, Thomas Renninger tr...@suse.de wrote:
On Thursday 07 October 2010 17:08:25 Mathieu Desnoyers wrote:
[ Adding a few more CCs, since this discussion is about a tracepoint
userspace ABI policy, which is a topic of general interest. ]
...
Yes, sadly
Here is a re-spin of the patches after discussion.
It includes:
- clean-up of the API,
- a deprecation process for backward compatibility,
- support for x86 and OMAP processors,
- support for the following tracepoints: cpuidle, cpufreq,
system suspend, clocks power domains
ToDO:
-
userspace tool gets adjusted in a separate patch.
Signed-off-by: Thomas Renninger tr...@suse.de
CC: Jean Pihet jean.pi...@newoldbits.com
CC: Arjan van de Ven ar...@linux.intel.com
CC: Peter Zijlstra pet...@infradead.org
CC: Ingo Molnar mi...@elte.hu
CC: linux-perf-us...@vger.kernel.org
CC: linux
The patch adds the new power management trace points for
the OMAP architecture.
The trace points are for cpuidle, cpufreq (DVFS), the clocks
changes (enable, disable, set_rate) and the power domains
transitions.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/mach-omap2/cpuidle34xx.c
Uses the machine_suspend trace point, from the
generic kernel suspend_enter function.
Signed-off-by: Jean Pihet j-pi...@ti.com
CC: Thomas Renninger tr...@suse.de
---
kernel/power/suspend.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/power/suspend.c b/kernel
Provide a CONFIG_DEPRECATED_POWER_EVENT_TRACING option in order
to provide backward compatibility with the user space tracing tools.
To be removed as soon as the tools are in sync with the new API.
Note: only the old events are mapped to.
Signed-off-by: Jean Pihet j-pi...@ti.com
CC: Thomas
Hi,
On Mon, Oct 4, 2010 at 6:10 PM, Frank Ch. Eigler f...@redhat.com wrote:
Hi -
Provide a CONFIG_DEPRECATED_POWER_EVENT_TRACING option in order
to provide backward compatibility with the user space tracing tools.
This is clever:
+/* Map new events trace points calls to old ones */
Hi,
On Wed, Sep 29, 2010 at 9:49 AM, Thomas Renninger tr...@suse.de wrote:
On Tuesday 28 September 2010 23:45:24 Arjan van de Ven wrote:
On 9/28/2010 2:22 PM, Rafael J. Wysocki wrote:
On Tuesday, September 28, 2010, Jean Pihet wrote:
Hi,
Hi,
Here is what I am proposing, in reply
Hi,
Here is what I am proposing, in reply to all your comments:
1) rename the events to match Thomas's proposal:
power:power_cpu_cstate
power:power_cpu_pstate
power:power_cpu_sstate
...
2) introduce a new Kconfig option CONFIG_DEPRECATED_POWER_EVENTS and
conditionally map a subset
Hi,
On Tue, Sep 28, 2010 at 11:22 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Tuesday, September 28, 2010, Jean Pihet wrote:
Hi,
Hi,
Here is what I am proposing, in reply to all your comments:
1) rename the events to match Thomas's proposal:
power:power_cpu_cstate
: Jean Pihet jean.pi...@newoldbits.com
Date: Wed, 22 Sep 2010 17:10:47 +0200
Subject: [PATCH] tools, perf: redefine the power events API
Redefine the API with:
- power_switch_state for C-, P- and S-states,
- clock and power_domain events
The new API allows easier maintainance of the kernel
On Wed, Sep 22, 2010 at 5:33 PM, Arjan van de Ven ar...@linux.intel.com wrote:
On 9/22/2010 8:31 AM, Jean Pihet wrote:
Hi,
Here is a patch that redefines the power events API. The advantages
are: easier maintainance of the kernel and the
user space tools, a cleaner and more generic
Hi Thomas,
On Fri, Sep 17, 2010 at 3:08 PM, Thomas Renninger tr...@suse.de wrote:
Hi,
I had a quick look at this and it's amazing how broken
the whole power event tracing interfaces are.
It's not your fault, Jean, they always were and adding your stuff is
fine.
That is the whole point! This
On Thu, Sep 9, 2010 at 9:54 AM, Ingo Molnar mi...@elte.hu wrote:
I think the ACPI tracepoints can be added on top of the proposed
patch. Is that ok?
Yeah - and the OMAP thing can be split up too if the OMAP folks prefer
it that way, but we still want to _see_ all the patches in this thread
Hi,
Here is a patch proposal for adding new trace events for power management.
Note: thread restarted after the initial discussions on LKML.
Jean
From 6768b88e8133129fa847dd7a95dc6dd17c0662d2 Mon Sep 17 00:00:00 2001
From: Jean Pihet jean.pi...@newoldbits.com
Date: Tue, 7 Sep 2010 09:12:48
, 2010 at 9:21 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
Hi,
Here is a patch proposal for adding new trace events for power management.
Note: thread restarted after the initial discussions on LKML.
Sorry the thread did not get restarted because I am using the same
e-mail subject.
Jean
Hi Vishwa,
On Mon, Sep 6, 2010 at 1:15 PM, Sripathy, Vishwanath
vishwanath...@ti.com wrote:
I did some profiling of assembly code on OMAP3630 board (ZOOM3). In worst
case it takes around 3.28ms and best case around 2.93ms for mpu off mode.
Can you give a bit more details? Which measurement has
Hi Amit, Santosh,
On Thu, Sep 2, 2010 at 10:11 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
...
The point is to keep the minimum possible in the kernel: just the
tracepoints we're interested in. The rest (calculations, averages,
analysis, etc.) does not need to be in the kernel
On Fri, Aug 27, 2010 at 2:01 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
Hi Kevin,
On Wed, Aug 25, 2010 at 8:22 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
...
Add
Hi,
On Sat, Aug 28, 2010 at 12:08 AM, vishwanath.sripa...@linaro.org wrote:
From: Vishwanath BS vishwanath.sripa...@linaro.org
This patch has instrumentation code for measuring latencies for
various CPUIdle C states for OMAP. Idea here is to capture the
timestamp at various phases of CPU
Benoit,
On Fri, Aug 27, 2010 at 12:25 PM, Cousson, Benoit b-cous...@ti.com wrote:
This patch has instrumentation code for measuring latencies for
various CPUIdle C states for OMAP. Idea here is to capture the
timestamp at various phases of CPU Idle and then compute the sw
latency for various
Hi Kevin,
On Wed, Aug 25, 2010 at 8:22 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
...
Add the cpuidle power_start and power_end events. The state
parameter of power_start has the following meaning:
- -1: from the suspend
From 28198d2d297216fd9fa3e00513e9470f50761c19 Mon Sep 17 00:00:00 2001
From: Jean Pihet jean.pi...@newoldbits.com
Date: Wed, 25 Aug 2010 17:05:48 +0200
Subject: [PATCH] OMAP2: add cpuidle and cpufreq events tracing
Add the cpuidle power_start and power_end events. The state
parameter
Hi,
On Wed, Jun 16, 2010 at 08:09, Michael Trimarchi
mich...@panicking.kicks-ass.org wrote:
Han Wang wrote:
Hi,
I am testing the 2.6.35-rc1 pm branch code on Overo. The system
boots ok. (I can provide booting log if that is necessary) However,
when I use echo mem /sys/power/state to send
Hi,
In addition to DEBUG_LL you need to append 'earlyprintk' to the cmdline.
Hope this helps,
Jean
On Friday 26 February 2010 16:02:36 Gadiyar, Anand wrote:
Wit the current master branch, I tried enabling DEBUG_LL, and
EARLY_PRINTK options, but I can't see the LL output as usual (#...
On Friday 11 December 2009 13:05:37 Reddy, Teerth wrote:
Reposting the patch with proper format
From: Teerth Reddy tee...@ti.com
This patch sets the dpll3 clock stabilization delay during
DVFS. The stabilization delay is calculated dynamically
using the ARM performance counter.
Currently
Hi Kevin,
On Friday 20 November 2009 19:29:02 Kevin Hilman wrote:
Maxime Petazzoni mpetazz...@mvista.com writes:
Hi,
* Premi, Sanjeev pr...@ti.com [2009-11-20 21:17:04]:
I am facing a strange problem on OMAP3EVM after resuming from idle.
When using OPP5, the VDD1 voltage ramps to
On Friday 20 November 2009 20:11:26 Kevin Hilman wrote:
Jean Pihet jpi...@mvista.com writes:
Hi Kevin,
On Friday 20 November 2009 19:29:02 Kevin Hilman wrote:
Maxime Petazzoni mpetazz...@mvista.com writes:
Hi,
* Premi, Sanjeev pr...@ti.com [2009-11-20 21:17:04]:
I am facing
Kevin,
On Friday 25 September 2009 01:35:48 Kevin Hilman wrote:
During suspend, the kernel timekeeping subsystem is shut down. Before
suspend and upon resume, it uses a weak function
read_persistent_clock() to determine the amount of time that elapsed
during suspend.
This function was not
On Wednesday 09 September 2009 00:17:42 Kevin Hilman wrote:
Reddy, Teerth tee...@ti.com writes:
This patch initializes the SDRC params for DVFS on Zoom2.
Signed-off-by: Teerth Reddy tee...@ti.com
---
arch/arm/mach-omap2/board-zoom2.c |6 --
1 files changed, 4 insertions(+), 2
Hi!
On Friday 21 August 2009 16:34:33 Peter Barada wrote:
On Fri, 2009-08-21 at 15:10 +0200, Kevin Hilman wrote:
Tim Bird tim.b...@am.sony.com writes:
Paul Walmsley wrote:
Hi Peter,
On Wed, 19 Aug 2009, Peter Barada wrote:
1) Does anyone have a URL of the format patches should
Hi Kevin,
On Friday 07 August 2009 19:11:20 Kevin Hilman wrote:
Jean Pihet jpi...@mvista.com writes:
On Thursday 06 August 2009 19:13:06 Kevin Hilman wrote:
Kevin Hilman wrote:
I just pushed an updated PM branch which was rebased to current
omap/master (which is based on v2.6.31-rc5
Hi,
I am trying to get the latest IRQ registers from a timer or a work queue but I
am running into problems:
- get_irq_regs() returns NULL in some cases, so it is unsuable and even causes
crash when trying to get the registers values from the returned ptr
- I never get user space registers,
On Monday 29 June 2009 17:19:31 Russell King - ARM Linux wrote:
On Mon, Jun 29, 2009 at 04:31:18PM +0200, Jean Pihet wrote:
I am trying to get the latest IRQ registers from a timer or a work queue
but I am running into problems:
- get_irq_regs() returns NULL in some cases,
It will always
On Monday 29 June 2009 18:07:44 Russell King - ARM Linux wrote:
On Mon, Jun 29, 2009 at 05:35:37PM +0200, Jean Pihet wrote:
On Monday 29 June 2009 17:19:31 Russell King - ARM Linux wrote:
It's one of these things that nests itself - when you have several IRQs
being processed on one CPU
Hi Siarhei Siamashka,
On Monday 29 June 2009 18:36:57 Siarhei Siamashka wrote:
On Monday 29 June 2009 17:31:18 ext Jean Pihet wrote:
Hi,
I am trying to get the latest IRQ registers from a timer or a work queue
but I am running into problems:
- get_irq_regs() returns NULL in some cases
On Monday 29 June 2009 19:37:57 Russell King - ARM Linux wrote:
On Mon, Jun 29, 2009 at 07:36:57PM +0300, Siarhei Siamashka wrote:
On Monday 29 June 2009 17:31:18 ext Jean Pihet wrote:
I am trying to get the latest IRQ registers from a timer or a work
queue but I am running into problems
On Monday 29 June 2009 19:46:33 Russell King - ARM Linux wrote:
On Mon, Jun 29, 2009 at 06:58:41PM +0200, Jean Pihet wrote:
I am trying to get a different approach, starting from the errata
description. The idea is to avoid the counters from overflowing,
which could cause a PMNC unit reset
On Monday 29 June 2009 19:54:23 Siarhei Siamashka wrote:
On Monday 29 June 2009 19:58:41 ext Jean Pihet wrote:
Hi Siarhei Siamashka,
On Monday 29 June 2009 18:36:57 Siarhei Siamashka wrote:
On Monday 29 June 2009 17:31:18 ext Jean Pihet wrote:
Hi,
I am trying to get
On Monday 29 June 2009 20:38:59 Siarhei Siamashka wrote:
On Monday 29 June 2009 20:37:57 ext Russell King - ARM Linux wrote:
On Mon, Jun 29, 2009 at 07:36:57PM +0300, Siarhei Siamashka wrote:
On Monday 29 June 2009 17:31:18 ext Jean Pihet wrote:
I am trying to get the latest IRQ
Hi Paul, Russell, Tony,
On Friday 19 June 2009 18:23:42 Russell King - ARM Linux wrote:
On Thu, Jun 18, 2009 at 08:48:47AM +0300, Tony Lindgren wrote:
Paul, can you please post a git pull request for Russell on these?
I think these should still go in if possible.
Russell, if you think
Hi,
Those 2 patches allow the self refresh to work in case of 2 chip selects are
in use by the SDRC.
It applies on top of the master branch.
Regards,
Jean
---
OMAP3-add-support-for-2-SDRAM-chip-selects.patch
OMAP3-Setup-MUX-settings-for-SDRC-CKE-signals.patch
rev C2 and B5, with
suspend/resume and frequency changes (cpufreq).
Signed-off-by: Jean Pihet jpi...@mvista.com
---
arch/arm/mach-omap2/board-2430sdp.c |2 +-
arch/arm/mach-omap2/board-3430sdp.c |2 +-
arch/arm/mach-omap2/board-4430sdp.c |2 +-
arch/arm/mach-omap2/board
and CONFIG_OMAP_MUX_WARNINGS options
must be enabled for the mux code to have effect.
Signed-off-by: Jean Pihet jpi...@mvista.com
---
arch/arm/mach-omap2/board-omap3beagle.c |4
arch/arm/mach-omap2/board-omap3pandora.c |5 +
arch/arm/mach-omap2/board-overo.c|5
801 - 900 of 931 matches
Mail list logo
