On 02/05/2013 10:16 AM, Mark Jackson wrote:
On 01/02/13 19:39, Mark Jackson wrote:
On 01/02/13 17:12, Jon Hunter wrote:
Hi Mark,
On 02/01/2013 10:56 AM, Mark Jackson wrote:
There's plenty of DT support going in for NAND flash, but is there any
work going on to support NOR
flash ?
What
On 02/05/2013 02:39 AM, Igor Grinberg wrote:
On 02/04/13 21:46, Jon Hunter wrote:
When booting with device-tree for OMAP3 and AM335x devices and a gptimer
is used as the clocksource (which is always the case for AM335x), a
gptimer located in a power domain that is not always-on is selected
On 02/05/2013 10:48 AM, Mark Jackson wrote:
On 05/02/13 16:35, Jon Hunter wrote:
On 02/05/2013 10:16 AM, Mark Jackson wrote:
On 01/02/13 19:39, Mark Jackson wrote:
On 01/02/13 17:12, Jon Hunter wrote:
Hi Mark,
On 02/01/2013 10:56 AM, Mark Jackson wrote:
There's plenty of DT support going
is working on my omap4430 panda, sdp and
omap4460 panda. Let me know what you think ...
Cheers
Jon
From 3bfe708af8e91564bc78c79111f9080a35fb5b88 Mon Sep 17 00:00:00 2001
From: Jon Hunter jon-hun...@ti.com
Date: Tue, 5 Feb 2013 13:27:57 -0600
Subject: [PATCH] ARM: OMAP4: Fix low power in kernel suspend
On 02/05/2013 05:34 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130204 14:49]:
On 02/04/2013 04:12 PM, Jon Hunter wrote:
On 02/01/2013 03:51 PM, Tony Lindgren wrote:
How about let's fix this properly to start with so we don't add
more blockers moving this code to drivers/bus
On 02/02/2013 12:11 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130201 17:25]:
On 02/01/2013 03:51 PM, Tony Lindgren wrote:
How about let's fix this properly to start with so we don't add
more blockers moving this code to drivers/bus?
Looks like gpmc_mem_init() gets called
On 01/30/2013 11:04 AM, Jon Hunter wrote:
There is a lot of redundancy in the definitions for the various system
timers for OMAP2+ devices. For example, the omap3_am33xx_gptimer_timer_init()
function is the same as the omap3_gp_gptimer_timer_init() function and the
function
://patchwork.kernel.org/patch/1921421/
Jon Hunter (7):
ARM: OMAP2+: Fix selection of clockevent timer when using device-tree
ARM: OMAP2+: Display correct system timer name
ARM: OMAP2+: Remove hard-coded test on timer ID
ARM: OMAP2+: Simplify system timer clock definitions
ARM: OMAP2+: Simplify system
selected as expected. Fix this problem
by ensuring the timer property is passed to omap_get_timer_dt().
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2
if the timer's current
parent clock is the desired parent clock and only call clk_set_parent()
if this is not the case.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/timer.c | 25 +
1 file changed
with device-tree does not match the ID shown.
Therefore, instead display the HWMOD name of the gptimer and use
the HWMOD name as the name of clockevent and clocksource timer (if a
gptimer is used).
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch
.
Therefore, consolidate the definitions to simplify the code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Igor Grinberg grinb...@compulab.co.il
---
arch/arm/mach-omap2/board-cm-t3517.c |2 +-
arch/arm/mach-omap2/board-generic.c |2
' was not declared. Should it be static?
The function omap4_sync32k_timer_init() is not referenced outside of the
file timer.c and so make this function static.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Currently, the timer ID is being passed to the function
omap_dm_timer_init_one(). Instead of passing the ID separately, store it
in the omap_dm_timer structure, that is also passed, and access the ID
from this structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c
/5 devices (unlike OMAP2/3 devices), there is
no clock alias for timer_sys_ck with NULL as the device name. Therefore
we still need to use the alias sys_clkin_ck for these devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach
On 02/04/2013 11:42 AM, Jon Hunter wrote:
This series consists mainly of clean-ups for clockevents and
clocksource timers on OMAP2+ devices. The most significant change
in functionality comes from the 5th patch which is changing the
selection of the clocksource timer for OMAP3 and AM335x
On 02/04/2013 11:46 AM, Russell King - ARM Linux wrote:
On Mon, Feb 04, 2013 at 11:43:02AM -0600, Jon Hunter wrote:
@@ -280,22 +281,22 @@ static int __init omap_dm_timer_init_one(struct
omap_dm_timer *timer,
if (IS_ERR(timer-fclk))
return -ENODEV;
-/* FIXME: Need
On 02/04/2013 11:45 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130204 07:09]:
On 02/02/2013 12:11 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130201 17:25]:
On 02/01/2013 03:51 PM, Tony Lindgren wrote:
How about let's fix this properly to start with so we don't
On 02/04/2013 01:15 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130204 10:49]:
On 02/04/2013 11:45 AM, Tony Lindgren wrote:
AFAIK SYSBOOT_n values reflect the boot time values of the actual SYSBOOT
pins, so using generic pinconf there makes sense. But this of course should
with device-tree does not match the ID shown.
Therefore, instead display the HWMOD name of the gptimer and use
the HWMOD name as the name of clockevent and clocksource timer (if a
gptimer is used).
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch
in the omap_dm_timer structure
to clean-up the code.
- Added new patch to fix a sparse warning seen in ARM-SOC next.
[1] https://patchwork.kernel.org/patch/1921421/
Jon Hunter (7):
ARM: OMAP2+: Display correct system timer name
ARM: OMAP2+: Remove hard-coded test on timer ID
ARM: OMAP2+: Simplify system
if the timer's current
parent clock is the desired parent clock and only call clk_set_parent()
if this is not the case.
Also if clk_get() fails, then use PTR_ERR() to return the error code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm
/5 devices (unlike OMAP2/3 devices), there is
no clock alias for timer_sys_ck with NULL as the device name. Therefore
we still need to use the alias sys_clkin_ck for these devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach
.
Therefore, consolidate the definitions to simplify the code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Igor Grinberg grinb...@compulab.co.il
---
arch/arm/mach-omap2/board-cm-t3517.c |2 +-
arch/arm/mach-omap2/board-generic.c |2
Currently, the timer ID is being passed to the function
omap_dm_timer_init_one(). Instead of passing the ID separately, store it
in the omap_dm_timer structure, that is also passed, and access the ID
from this structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c
' was not declared. Should it be static?
The function omap4_sync32k_timer_init() is not referenced outside of the
file timer.c and so make this function static.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
the clocksource
and clockevent timers will be active and this will keep additional power
domains on. During kernel suspend, only the clocksource timer is active
and therefore, it is better to use a gptimer in a power domain that is
always-on for clocksource.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch
On 02/04/2013 01:47 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130204 11:37]:
On 02/04/2013 01:15 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130204 10:49]:
On 02/04/2013 11:45 AM, Tony Lindgren wrote:
AFAIK SYSBOOT_n values reflect the boot time values
/gmane.linux.kernel.commits.head/95931
Heres what I have now ...
From df2eebd3580f478f569241d294c2f810359fab6a Mon Sep 17 00:00:00 2001
From: Jon Hunter jon-hun...@ti.com
Date: Thu, 31 Jan 2013 15:56:08 -0600
Subject: [PATCH] ARM: OMAP2: Fix GPMC memory initialisation
OMAP2+ devices have an internal ROM
On 02/04/2013 04:12 PM, Jon Hunter wrote:
On 02/01/2013 03:51 PM, Tony Lindgren wrote:
How about let's fix this properly to start with so we don't add
more blockers moving this code to drivers/bus?
Looks like gpmc_mem_init() gets called from gpmc_probe() so
we can pass that information
(if a
gptimer is used).no
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c | 44
+--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c
index 72c2ca1
On 02/01/2013 02:41 AM, Bedia, Vaibhav wrote:
Hi Jon,
On Wed, Jan 30, 2013 at 22:34:31, Hunter, Jon wrote:
When booting with device-tree for OMAP3 and AM335x devices and a gptimer
is used as the clocksource (which is always the case for AM335x), a
gptimer located in a power domain that is
On 02/01/2013 02:59 AM, Jon Hunter wrote:
On 02/01/2013 02:41 AM, Bedia, Vaibhav wrote:
Hi Jon,
On Wed, Jan 30, 2013 at 22:34:31, Hunter, Jon wrote:
When booting with device-tree for OMAP3 and AM335x devices and a gptimer
is used as the clocksource (which is always the case for AM335x
On 02/01/2013 03:31 AM, Bedia, Vaibhav wrote:
On Fri, Feb 01, 2013 at 14:23:43, Hunter, Jon wrote:
[...]
+/* Timer name needs to be big enough to store a string of timerXX */
+static char timer_name[10];
+
Why not move this inside omap_dm_timer_init_one()?
In the non-DT case, the name
. Prevent this by marking all the chip-selects as
reserved by default and only make them available for devices to request
if the GPMC probe succeeds.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
, when booting from NOR or NAND
memories connected to CS0, these memories are always mapped to address
0x0800 and so reserving this memory range does not present any
problems for these devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 25
.
Boot tested on OMAP2420 H4, OMAP3430 SDP, OMAP4430 SDP and AM335x EVM.
Jon Hunter (2):
ARM: OMAP2+: Prevent potential crash if GPMC probe fails
ARM: OMAP2: Fix GPMC memory initialisation
arch/arm/mach-omap2/gpmc.c | 31 ++-
1 file changed, 22 insertions(+), 9
Hi Mark,
On 02/01/2013 10:56 AM, Mark Jackson wrote:
There's plenty of DT support going in for NAND flash, but is there any work
going on to support NOR
flash ?
What board and device are you working that is using NOR? I have a
OMAP2420 H4 with NOR that I have been doing a bit of maintenance
On 02/01/2013 03:51 PM, Tony Lindgren wrote:
Hi Jon,
* Jon Hunter jon-hun...@ti.com [130201 08:42]:
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2/gpmc.c
@@ -32,6 +32,7 @@
#include soc.h
#include common.h
+#include control.h
#include omap_device.h
#include gpmc.h
On 01/31/2013 03:08 AM, Igor Grinberg wrote:
On 01/30/13 19:04, Jon Hunter wrote:
When booting with device-tree for OMAP3 and AM335x devices and a gptimer
is used as the clocksource (which is always the case for AM335x), a
gptimer located in a power domain that is not always-on is selected
).
This series is based upon ARM-SoC next branch.
[1] https://patchwork.kernel.org/patch/1921421/
Jon Hunter (5):
ARM: OMAP2+: Display correct system timer name
ARM: OMAP2+: Remove hard-coded test on timer ID
ARM: OMAP2+: Simplify system timer clock definitions
ARM: OMAP2+: Simplify system timers
if the timer's current
parent clock is the desired parent clock and only call clk_set_parent()
if this is not the case.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c | 26 --
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/arch
with device-tree does not match the ID shown.
Therefore, instead display the HWMOD name of the gptimer and use
the HWMOD name as the name of clockevent and clocksource timer (if a
gptimer is used).
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c | 44
In commit c59b537 (ARM: OMAP2+: Simplify dmtimer clock aliases), new
clock aliases for dmtimers were added to simplify the code. These clock
aliases can also be used when configuring the system timers and allow us
to remove the current definitions, simplifying the code.
Signed-off-by: Jon Hunter
.
Therefore, consolidate the definitions to simplify the code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/board-cm-t3517.c |2 +-
arch/arm/mach-omap2/board-generic.c |2 +-
arch/arm/mach-omap2/common.h |3 +--
arch/arm/mach-omap2/timer.c | 23
the clocksource
and clockevent timers will be active and this will keep additional power
domains on. During kernel suspend, only the clocksource timer is active
and therefore, it is better to use a gptimer in a power domain that is
always-on for clocksource.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch
On 01/18/2013 09:27 AM, Santosh Shilimkar wrote:
From: Rajendra Nayak rna...@ti.com
Add the clock tree related data for OMAP54xx platforms.
[snip]
+ CLK(omap_timer.1, 32k_ck, sys_32k_ck,
CK_54XX),
+ CLK(omap_timer.2, 32k_ck, sys_32k_ck,
On 01/18/2013 09:32 AM, Santosh Shilimkar wrote:
OMAP5 clockdata has different sys clock clock node name. Fix the timer code
to take care of it.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/timer.c |5 +++--
1 file changed, 3 insertions(+), 2
On 01/21/2013 01:22 AM, Bedia, Vaibhav wrote:
On Fri, Jan 18, 2013 at 10:55:43, Shilimkar, Santosh wrote:
On Friday 18 January 2013 12:15 AM, Jon Hunter wrote:
On 01/10/2013 10:37 PM, Bedia, Vaibhav wrote:
On Tue, Jan 08, 2013 at 20:45:10, Shilimkar, Santosh wrote:
On Monday 31 December
On 01/24/2013 04:30 PM, Jon Hunter wrote:
Hi Vaibhav,
On 12/31/2012 07:07 AM, Vaibhav Bedia wrote:
AM33XX has two timers (DTIMER0/1) in the WKUP domain.
On GP devices the source of DMTIMER0 is fixed to an
inaccurate internal 32k RC oscillator and this makes
the DMTIMER0 practically either
On 01/30/2013 11:48 AM, Jon Hunter wrote:
On 01/24/2013 04:30 PM, Jon Hunter wrote:
Hi Vaibhav,
On 12/31/2012 07:07 AM, Vaibhav Bedia wrote:
AM33XX has two timers (DTIMER0/1) in the WKUP domain.
On GP devices the source of DMTIMER0 is fixed to an
inaccurate internal 32k RC oscillator
On 01/30/2013 01:18 AM, Bedia, Vaibhav wrote:
On Wed, Jan 30, 2013 at 01:53:11, Hunter, Jon wrote:
Commit 9725f44 (ARM: OMAP: Add DT support for timer driver) added
device-tree support for selecting a clockevent timer by property.
However, the code is currently ignoring the property passed
On 01/29/2013 03:53 AM, Łukasz Góralczyk wrote:
Hello,
Some background:
Recently I've ported Linux to some custom omap1 based (5940 or 1510)
hardware. I've had some initial problems, but after a dirty fix I
have a running kernel and I can boot using NFS.
Do you mean 5910? I am not
selected as expected. Fix this problem
by ensuring the timer property is passed to omap_get_timer_dt().
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2
);
return ret;
+ }
}
return 0;
Acked-by: Jon Hunter jon-hun...@ti.com
Thanks!
Jon
--
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://vger.kernel.org
Hi Vaibhav,
On 12/31/2012 07:07 AM, Vaibhav Bedia wrote:
AM33XX has two timers (DTIMER0/1) in the WKUP domain.
On GP devices the source of DMTIMER0 is fixed to an
inaccurate internal 32k RC oscillator and this makes
the DMTIMER0 practically either as a clocksource or
as clockevent.
: serial
Hit any key to stop autoboot: 0
... etc. ...
- Paul
From: Jon Hunter jon-hun...@ti.com
Date: Thu, 10 Jan 2013 14:53:29 -0600
Subject: [PATCH] ARM: OMAP2: Fix missing omap2xxx_clkt_vps_late_init function
calls
During the migration to the common clock framework, calls
-by: Vaibhav Bedia vaibhav.be...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Vaibhav Hiremath hvaib...@ti.com
Cc: Jon Hunter jon-hun...@ti.com
---
v1-v2:
Get rid
...@deeprootsystems.com
Cc: Vaibhav Hiremath hvaib...@ti.com
Cc: Jon Hunter jon-hun...@ti.com
---
v1-v2:
Get rid of harcoded timer id.
Note: since a platform device is not created for these timer
instances and because there's very minimal change needed for
restarting the timer
...@ti.com
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Tony Lingren t...@atomide.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Jon Hunter jon-hun...@ti.com
Hi Paul,
On 01/17/2013 12:51 PM, Paul Walmsley wrote:
Hi Jon
On Thu, 10 Jan 2013, Jon Hunter wrote:
During the migration to the common clock framework, calls to the
functions omap2xxx_clkt_vps_late_init() and
omap2xxx_clkt_vps_check_bootloader_rates() were not preserved for
OMAP2420
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
of RAM and uses the TWL4030 power management IC.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3430-sdp.dts | 46
2
() in the OMAP2420 and OMAP2430
clock initialisation code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Tested on OMAP2420 H4 board only.
arch/arm/mach-omap2/cclock2420_data.c |5 +
arch/arm/mach-omap2/cclock2430_data.c |5 +
2 files changed, 10 insertions(+)
diff --git a/arch/arm/mach-omap2
);
return np;
Otherwise ...
Acked-by: Jon Hunter jon-hun...@ti.com
Cheers
Jon
--
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://vger.kernel.org/majordomo-info.html
On 01/06/2013 03:12 PM, NeilBrown wrote:
[snip]
I've been playing with off-mode and discovered that the first attempt to set
the PWM after resume didn't work, but subsequent ones did.
I did some digging and came up with the following patch.
With this in place, the omap_pwm_suspend() above
-by: Jon Hunter jon-hun...@ti.com
Cheers
Jon
--
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://vger.kernel.org/majordomo-info.html
Hi Peter,
On 01/03/2013 07:46 AM, Peter Ujfalusi wrote:
We need to lock ABE DPPL on al OMAP4 revisions, not only for OMAP446x
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/cclock44xx_data.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
On 12/21/2012 04:35 PM, Pratik Patel wrote:
On Fri, Dec 21, 2012 at 02:27:03PM -0800, Pratik Patel wrote:
On Wed, Dec 12, 2012 at 03:43:06PM -0600, Jon Hunter wrote:
+
+/**
+ * cti_irq_ack - acknowledges the CTI trigger output
+ * @cti: CTI instance
+ *
+ * Acknowledges the CTI trigger
On 12/21/2012 04:27 PM, Pratik Patel wrote:
On Wed, Dec 12, 2012 at 03:43:06PM -0600, Jon Hunter wrote:
+
+/**
+ * cti_irq_ack - acknowledges the CTI trigger output
+ * @cti: CTI instance
+ *
+ * Acknowledges the CTI trigger output by writting to the appropriate
+ * bit in the CTI
On 12/19/2012 11:59 PM, Santosh Shilimkar wrote:
On Monday 17 December 2012 02:57 PM, Andreas Fenkart wrote:
Please add some changelog here too.
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
---
Patch seems straight forward thought will be interesting where you found
/ETB drivers are failing. Add enable/disable
clock functions to enable the EMU clock domain when enabling the
emu_src_ck.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/cclock3xxx_data.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-omap2
Hi Vinod,
On 11/15/2012 07:37 PM, Vinod Koul wrote:
On Fri, 2012-11-09 at 14:01 -0600, Jon Hunter wrote:
Hi Vinod,
A few people have been asking me if getting device-tree support for DMA
engine is plan for record for v3.8. I know that you were working through
implementing a common interface
Hi Paul,
On 12/09/2012 02:03 PM, Paul Walmsley wrote:
There's no need to determine the current power state for powerdomains
that must be on while the kernel is running. We mark these
powerdomains with a new flag, PWRDM_ACTIVE_WITH_KERNEL. Any
powerdomain marked with that flag is reported as
On 12/17/2012 02:16 AM, Benoit Cousson wrote:
Hi Jon,
On 12/14/2012 10:18 PM, Jon Hunter wrote:
Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate
header file for OMAP4460, because the node is not compatible
On 12/17/2012 10:20 AM, Mark Rutland wrote:
On Thu, Dec 13, 2012 at 07:21:30PM +, Jon Hunter wrote:
On 12/13/2012 11:41 AM, Will Deacon wrote:
On Wed, Dec 12, 2012 at 09:43:05PM +, Jon Hunter wrote:
Adds a device-tree binding for the ARM Cross Trigger Interface (CTI).
The ARM Cross
On 12/17/2012 10:38 AM, Mark Rutland wrote:
On Fri, Dec 14, 2012 at 09:26:37PM +, Jon Hunter wrote:
Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate
header file for OMAP4460, because the node is not compatible
Add device-tree PMU support for OMAP2, OMAP3 and OMAP4460. OMAP4430
is not included because PMU is not currently supported on this device
due to absence of a cross-trigger interface driver.
Tested with PERF on OMAP3430 Beagle Board and OMAP4460 Panda Board.
Boot tested only on OMAP2420 H4.
Jon
to the absence of a cross-trigger
interface driver.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |5 +
arch/arm/boot/dts/omap3.dtsi |6 ++
arch/arm/boot/dts/omap4-panda-es.dts |2 ++
arch/arm/boot/dts/omap4460.dtsi | 18
driver) and so ensure that this
indicated on boot with or without device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/pmu.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/pmu.c b/arch/arm/mach-omap2/pmu.c
index
On 12/17/2012 11:49 AM, Jon Hunter wrote:
Add device-tree PMU support for OMAP2, OMAP3 and OMAP4460. OMAP4430
is not included because PMU is not currently supported on this device
due to absence of a cross-trigger interface driver.
Tested with PERF on OMAP3430 Beagle Board and OMAP4460
On 12/17/2012 04:14 PM, Carlos Hernandez wrote:
Just an fyi... am335x mainline compilation is broken due to invalid
references to vram.h
| CC arch/arm/mach-omap2/common.o
| arch/arm/mach-omap2/common.c:19:23: fatal error: plat/vram.h: No such
file or directory
Test run against
+ devices.
I have dropped the patch to fix a build error for OMAP4 in the
timer code as Olof already has this fix merged.
Jon Hunter (2):
ARM: OMAP2+: Fix realtime_counter_init warning in timer.c
ARM: AM335x: Fix warning
+ PMU code and so remove it.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/pmu.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-omap2/pmu.c b/arch/arm/mach-omap2/pmu.c
index 250d909..eb78ae7 100644
--- a/arch/arm/mach-omap2/pmu.c
+++ b/arch/arm/mach
The system memory node for the OMAP2420 H4 was incorrectly defined as
start address followed by end address, instead of start address and
size. No noticable side-effects were observed but fix this for
correctness.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420-h4.dts
Add device-tree PMU support for OMAP2, OMAP3 and OMAP4460.
Tested with PERF on OMAP3430 Beagle Board and OMAP4460 Panda Board.
Boot tested only on OMAP2420 H4.
Jon Hunter (2):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
arch/arm/boot/dts/omap2.dtsi
driver) and so ensure that this
indicated on boot with or without device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/pmu.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/pmu.c b/arch/arm/mach-omap2/pmu.c
index
Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate
header file for OMAP4460, because the node is not compatible with
OMAP4430.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |5
On 12/14/2012 03:18 PM, Jon Hunter wrote:
Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate
header file for OMAP4460, because the node is not compatible with
OMAP4430.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Add device-tree PMU support for OMAP2, OMAP3 and OMAP4460.
Tested with PERF on OMAP3430 Beagle Board and OMAP4460 Panda Board.
Boot tested only on OMAP2420 H4.
Jon Hunter (2):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
arch/arm/boot/dts/omap2.dtsi
driver) and so ensure that this
indicated on boot with or without device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/pmu.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/pmu.c b/arch/arm/mach-omap2/pmu.c
index
Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate
header file for OMAP4460, because the node is not compatible with
OMAP4430.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |5
Commit 0d9250c (ARM: dts: omap4-panda: Add pinmux configuration for
HDMI) added a new device-tree source file for Rev A4 of the OMAP4430
Panda board but it did not add this version to the makefile. Hence,
add this file to the makefile.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm
On 12/12/2012 09:06 PM, NeilBrown wrote:
[Thierry: question for you near the end - thanks]
On Wed, 12 Dec 2012 10:08:28 -0600 Jon Hunter jon-hun...@ti.com wrote:
Hi Neil,
On 12/12/2012 02:24 AM, NeilBrown wrote:
This patch is based on an earlier patch by Grant Erickson
which
On 12/12/2012 10:33 PM, NeilBrown wrote:
On Thu, 13 Dec 2012 14:06:35 +1100 NeilBrown ne...@suse.de wrote:
+ omap_dm_timer_enable(omap-dm_timer);
Do you need to call omap_dm_timer_enable here? _set_load and _set_match
will enable the timer. So this should not be necessary.
True. That
On 12/13/2012 08:58 AM, Will Deacon wrote:
Hi Jon,
On Wed, Dec 12, 2012 at 09:43:04PM +, Jon Hunter wrote:
The Cross Trigger Interface (CTI) helpers in cti.h include definitions
for the Coresight Lock Access Register (LAR) and Lock Status Register
(LSR). These registers are already
On 12/13/2012 11:41 AM, Will Deacon wrote:
On Wed, Dec 12, 2012 at 09:43:05PM +, Jon Hunter wrote:
Adds a device-tree binding for the ARM Cross Trigger Interface (CTI).
The ARM Cross Trigger Interface provides a way to route events between
processor modules. For example, on OMAP4430 we
On 12/13/2012 09:08 AM, Will Deacon wrote:
On Wed, Dec 12, 2012 at 09:43:06PM +, Jon Hunter wrote:
Convert the Cross Trigger Interface (CTI) helpers in cti.h into a
AMBA bus driver so that we can use device-tree to look-up the hardware
specific information such as base address
Hi Neil,
On 12/12/2012 02:24 AM, NeilBrown wrote:
This patch is based on an earlier patch by Grant Erickson
which provided pwm devices using the 'legacy' interface.
This driver instead uses the new framework interface.
Cc: Grant Erickson maratho...@gmail.com
Signed-off-by: NeilBrown
On 12/12/2012 05:31 AM, Thierry Reding wrote:
On Wed, Dec 12, 2012 at 07:24:30PM +1100, NeilBrown wrote:
[snip]
+static int omap_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
+{
+struct omap_chip *omap = to_omap_chip(chip);
+int status = 0;
+
+/* Enable the
these frameworks only support platform devices and not AMBA
devices. Therefore, add a clock alias for the AMBA APB clock for OMAP4
devices to turn on the DEBUGSS power and clock domain.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/cclock44xx_data.c |1 +
1 file changed, 1
301 - 400 of 1153 matches
Mail list logo
