the code.
Cc: Vaibhav Hiremath hvaib...@ti.com
Cc: Jon Hunter jon-hun...@ti.com
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 877
arch/arm/plat-omap/include/plat/gpmc.h | 93 +++-
2 files changed, 872 insertions
Hi Afzal,
On 05/01/2012 07:19 AM, Afzal Mohammed wrote:
Create API for platforms to adapt gpmc to HWMOD
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 52
+++-
arch/arm/plat-omap/include/plat/gpmc.h |1 +
2
Hi Afzal,
On 05/01/2012 07:20 AM, Afzal Mohammed wrote:
Some boards depend on bootloader to update chip select value for NAND.
It is felt that Kernel should not depend on bootloader to get CS, as
for a particular board CS is hardwired and is fixed, hence this can
directly be updated in
Hi Shubhrajyoti,
On 12/2/2011 3:21, Shubhrajyoti D wrote:
- The reset in the driver at init is not needed anymore as the
hwmod framework takes care of reseting it.
- Reset is removed from omap_i2c_init, which was called
not only during probe, but also after time out and error
Hi Shubhrajyoti,
On 12/2/2011 15:37, Jon Hunter wrote:
[snip]
@@ -594,6 +545,11 @@ static int omap_i2c_xfer_msg(struct i2c_adapter
*adap,
return r;
if (r == 0) {
dev_err(dev-dev, controller timed out\n);
+ if (dev-device_reset) {
+ r = dev-device_reset(dev-dev);
+ if (r 0)
+ dev_err(dev-dev
Hi Kevin,
On 12/8/2011 12:12, Kevin Hilman wrote:
Alexander Aringa.ar...@phytec.de writes:
Correct OMAP_I2C_SYSC_REG offset in omap4 register map.
Offset 0x20 is reserved and OMAP_I2C_SYSC_REG has 0x10 as offset.
Signed-off-by: Alexander Aringa.ar...@phytec.de
Thanks for the patch!
A
On 11/06/2012 03:05 AM, Federico Fuga wrote:
Hi Jon,
Il giorno 06/nov/2012, alle ore 00:21, Jon Hunter jon-hun...@ti.com ha
scritto:
I wanted to check the HDMI registers, but I didn't find the hdmi registers
table on the TRM.
Does someone have some hint, comment or previous
On 11/06/2012 01:32 AM, Bedia, Vaibhav wrote:
Hi Jon,
On Tue, Nov 06, 2012 at 02:34:05, Hunter, Jon wrote:
[...]
static struct clock_event_device clockevent_gpt = {
.name = gp_timer,
.features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT,
@@ -142,6 +171,8
On 11/06/2012 03:38 AM, Bedia, Vaibhav wrote:
Hi Jon,
On Tue, Nov 06, 2012 at 02:50:50, Hunter, Jon wrote:
[...]
Why is this? How is the dmtimer TIOCP_CFG register configured on AM33xx?
Is it using smart-idle?
Yes, it is set to smart-idle with wakeup capable mode. (this needs a fixup
On 11/06/2012 10:44 AM, Matthieu CASTET wrote:
Signed-off-by: Matthieu CASTET matthieu.cas...@parrot.com
I think you need to have something in the changelog for the patch
describing why this change is needed and what device this has been
tested on.
---
arch/arm/mach-omap2/gpmc.c
On 11/06/2012 12:00 PM, Matthieu CASTET wrote:
Jon Hunter a écrit :
On 11/06/2012 10:44 AM, Matthieu CASTET wrote:
/* caller is expected to have initialized CONFIG1 to cover
* at least sync vs async
diff --git a/arch/arm/plat-omap/include/plat/gpmc.h
b/arch/arm/plat-omap
On 11/04/2012 08:46 PM, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc4.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc4/20121104142910/
Passing tests
-
Boot to userspace: 2420n800, 3517evm, 3530es3beagle,
On 11/07/2012 11:32 AM, Paul Walmsley wrote:
On Wed, 7 Nov 2012, Jon Hunter wrote:
On 11/04/2012 08:46 PM, Paul Walmsley wrote:
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
Are you still
on boot. By locking the ABE DPLL, when clocks from the ABE DPLL
are not being requested the DPLL will transition into a low-power stop
mode.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c | 22 ++
1 file changed, 22 insertions(+)
diff --git
clock of timers 5-7 to the sys_clk_div_ck. Therefore, update
the clock aliases for timer 5-7 to reflect the updated device-tree name
for the timers.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
This change is needed for v3.8 as the patch [1] to update the default
timer addresses is queued
and validated that all timers are working.
- Suspend testing on OMAP3430 Beagle and OMAP4430 Panda (suspend not
functional on OMAP4460 Panda prior to this series and so could not
be tested).
- Core retention validated on OMAP3430 Beagle.
Jon Hunter (3):
ARM: OMAP4: Update timer clock aliases
updated to avoid
passing the calculated values for the multiplier (M) and divider (N) as
these are stored in the clk structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c|2 +
arch/arm/mach-omap2/dpll3xxx.c | 46 +++---
arch
. To make it
clear that posted mode is being used add some definitions so that it is more
readable.
Add separate definitions for the clock-events and clock-source timers so that
we can change the posted mode of clock-events and clock-source independently.
Signed-off-by: Jon Hunter jon-hun...@ti.com
test overnight that continually runs test #3 and #4 for
each available timer
This has also been boot tested on the AM335x Beagle Bone.
[1] http://marc.info/?l=linux-omapm=135065875808614w=2
[2] http://marc.info/?l=linux-omapm=135119308123513w=2
Jon Hunter (14):
ARM: OMAP: Add DMTIMER
. Although this is a
regression from the original code it only impacts performance and so is not
needed for stable.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/arch/arm/plat-omap
() for enabling posted mode. Hence, call
omap_dm_timer_enable_posted() where ever we are calling __omap_dm_timer_reset().
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c | 28
arch/arm/plat-omap/dmtimer.c | 23
. Therefore, remove one of the SYSC register definitions for the
DMTIMERs and ensure the appropriate register fields are defined for all
DMTIMERs.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 27 ++-
1 file changed, 6
of the DMTIMER
TISTAT register (referred to as the SYSS register in HWMOD). Add the
appropriate HWMOD definitions so that HWMOD will check the software reset
status when performing a software reset of the DMTIMER.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2
by this errata. Therefore, for system-timers
check to see if the intended posted mode matches the actual. If it does not then
there is a configuration error in the system timers posted configuration.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c | 15
timer, the function omap_dm_timer_reset() is now only being called for OMAP1
devices and OMAP1 does not use timer1 as a system timer. Therefore, remove the
check in omap_dm_timer_reset() so that timer1 is reset for OMAP1 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap
.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c |3 ---
arch/arm/plat-omap/include/plat/dmtimer.h |1 -
2 files changed, 4 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index 5a9f29b..a350f12 100644
it's
context will not be lost. Users should take care to service all interrupts
before disabling the timer.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c |5 +
arch/arm/plat-omap/include/plat/dmtimer.h |1 -
2 files changed, 1 insertion(+), 5
the match value must be loaded before the compare logic is enable.
The reset value for the timer counter and match registers is 0 and hence,
by enabling the compare logic before the actual match value is loaded a
spurious interrupt can be generated as the reset values match.
Signed-off-by: Jon Hunter
H4, OMAP3430 Beagle and OMAP4430 Panda that HWMOD is
configuring the dmtimer OCP_CFG register as expected for clock-events timer.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 13 +
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
that the interrupt disable function has been written so that it
can be used by all OMAP devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 31 +
arch/arm/plat-omap/include/plat/dmtimer.h |3 ++-
2 files changed, 33
structure. So instead of looking up the clock again used the clock handle
that stored in the omap_dm_timer structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/arch/arm/plat-omap
. CONFIG_OMAP_32K_TIMER=y
2. CONFIG_OMAP_32K_TIMER=y and boot parameter clocksource=gp_timer
3. CONFIG_OMAP_32K_TIMER not set
4. CONFIG_OMAP_32K_TIMER not set and boot parameter clocksource=gp_timer
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/timer.c |9
On 11/07/2012 11:32 AM, Paul Walmsley wrote:
On Wed, 7 Nov 2012, Jon Hunter wrote:
On 11/04/2012 08:46 PM, Paul Walmsley wrote:
* 4460pandaes: boot fails early
- Appears to be due to X-loader problems here
- Need to note the X-loader version so we know it's broken
Are you still
is unavailable (namely on AM33xx), we no
longer need the #ifdef around __omap2_sync32k_clocksource_init()
function. Remove the #ifdef CONFIG_OMAP_32K_TIMER around the
__omap2_sync32k_clocksource_init() function.
Signed-off-by: Igor Grinberg grinb...@compulab.co.il
Cc: Jon Hunter jon-hun
On 11/07/2012 03:22 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121107 11:03]:
This series includes several fixes for the OMAP DMTIMER driver. This is
based upon 3.7-rc4 with the two series adding device-tree support for
DMTIMERs [1] and the 32kHz Counter [2]
These look OK
On 10/31/2012 06:11 PM, Tony Lindgren wrote:
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121031 16:03]:
Hi Tony,
On Wednesday 31 October 2012 13:58:50 Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [121030 16:55]:
This code should be private to mach-omap2.
The only use
On 11/07/2012 04:04 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 01:01 PM, Jon Hunter wrote:
For OMAP2+ devices, when using DMTIMERs for system timers
(clock-events and
clock-source) the posted mode configuration of the timers is used. To
allow
the compiler to optimise
On 11/07/2012 04:10 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 01:01 PM, Jon Hunter wrote:
When using a DMTIMER as the clock-source timer, posted mode
configuration of
the DMTIMER is used. Posted mode is only benefical when configuring
timers as
it allows writes to be posted
On 11/07/2012 04:18 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 04:11 PM, Jon Hunter wrote:
On 11/07/2012 04:04 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 01:01 PM, Jon Hunter wrote:
For OMAP2+ devices, when using DMTIMERs for system timers
(clock-events
Mon Sep 17 00:00:00 2001
From: Jon Hunter jon-hun...@ti.com
Date: Thu, 27 Sep 2012 12:47:43 -0500
Subject: [PATCH] ARM: OMAP3+: Implement timer workaround for errata i103 and
i767
Errata Titles:
i103: Delay needed to read some GP timer, WD timer and sync timer
registers after wakeup (OMAP3/4
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove
On 11/07/2012 04:04 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 01:01 PM, Jon Hunter wrote:
For OMAP2+ devices, when using DMTIMERs for system timers
(clock-events and
clock-source) the posted mode configuration of the timers is used. To
allow
the compiler to optimise
On 11/07/2012 05:43 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 05:28 PM, Jon Hunter wrote:
On 11/07/2012 04:14 PM, Santosh Shilimkar wrote:
Looks sensible considering alternative WAs.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Thanks. With further thought I
On 11/07/2012 05:44 PM, Tony Lindgren wrote:
Hi Jon,
* Tony Lindgren t...@atomide.com [121106 16:48]:
* Jon Hunter jon-hun...@ti.com [121102 12:01]:
g...@github.com:jonhunter/linux.git dev-dt-timer
Thanks pulling into omap-for-v3.8/dt branch.
Looks like omap-for-v3.8/dt boots OK
On 11/08/2012 11:08 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure Igor is referring to the AM3517/3505
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main external clock sources which are the 32kHz clock and the sys_clk
(can be a range of frequencies from
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support
On 11/08/2012 12:28 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:43:31, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57,
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So thinking about this some more and given that we are moving away from
board files, if a board does not
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So
On 11/08/2012 11:38 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121108 09:21]:
On 11/07/2012 05:44 PM, Tony Lindgren wrote:
That's a bugger. I completely missed your patch last week sorry (I will
blame the Danish
beer) and had clearly not folded in to my testing!
:)
I
On 11/02/2012 07:32 AM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP domain can keep
running in suspend from a 32K clock
under the else clause.
This regression was introduced while integrating commit ARM: OMAP: Add
DT support for timer driver to add device-tree support to the DMTIMER
driver and commit ARM: OMAP: Move omap-pm-noop.c local to mach-omap2
to prepare for single zImage support.
Signed-off-by: Jon Hunter
On 11/08/2012 01:47 PM, Jon Hunter wrote:
Do you want to generate the patch or me?
Patch posted here ...
http://marc.info/?l=linux-omapm=135242025202171w=2
Cheers
Jon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
On 11/08/2012 06:17 PM, Jon Hunter wrote:
When booting with device-tree the kernel is panicing in the probe of the
DMTIMER driver. The panic is caused because the pointer to platform_data
structure is NULL when booting with device-tree and the driver is
attempting to access the structure
.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Please note that I ran into this problem when rebasing my dmtimer fixes
series [1] on Tony's Linux-OMAP master branch. I am including plat/cpu.h
in dmtimer.h and I found several other files including dmtimer.h are also
including soc.h and so generate
On 11/09/2012 10:22 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 08:21]:
If the header soc.h is included more than once in a source (for example
once directly by the source file and once indirectly by another header
file), then the compiler will generate redefintion errors
On 11/08/2012 10:55 AM, Jon Hunter wrote:
On 11/07/2012 05:43 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 05:28 PM, Jon Hunter wrote:
On 11/07/2012 04:14 PM, Santosh Shilimkar wrote:
Looks sensible considering alternative WAs.
Acked-by: Santosh Shilimkar santosh.shilim
On 10/15/2012 09:39 PM, Vinod Koul wrote:
On Tue, 2012-10-16 at 10:43 +0800, Shawn Guo wrote:
On Tue, Sep 25, 2012 at 10:05:01AM +0530, Vinod Koul wrote:
On Mon, 2012-09-24 at 17:25 -0500, Jon Hunter wrote:
For DT bindings, I think the binding itself shouldn't change based on my
work but I
On 11/09/2012 03:10 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 08:31]:
On 11/09/2012 10:22 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 08:21]:
If the header soc.h is included more than once in a source (for example
once directly by the source file
On 11/09/2012 05:50 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 15:44]:
On 11/09/2012 03:10 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 08:31]:
On 11/09/2012 10:22 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 08:21]:
If the header
On 11/09/2012 06:21 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121109 15:59]:
Sorry, I meant in the fixes series I have posted for dmtimer, I am
adding a new function called omap_dm_timer_populate_errata() that is
using cpu_is_() [1]. I had done this a while back, but now I
driver.
[1] http://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
Jon Hunter (13):
ARM: OMAP: Add DMTIMER definitions for posted mode
ARM: OMAP3+: Implement timer workaround for errata i103 and i767
ARM: OMAP: Fix timer posted mode support
ARM: OMAP3: Correct HWMOD DMTIMER
impacts AM33xx
devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/timer.c | 49 ++-
arch/arm/plat-omap/dmtimer.c |3 +-
arch/arm/plat-omap/include/plat/dmtimer.h
. To make it
clear that posted mode is being used add some definitions so that it is more
readable.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/timer.c | 17 ++---
arch/arm/plat-omap/include/plat
. Although this is a
regression from the original code it only impacts performance and so is not
needed for stable.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 13 +
1 file changed, 5 insertions
. Therefore, remove one of the SYSC register definitions for the
DMTIMERs and ensure the appropriate register fields are defined for all
DMTIMERs.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 27
of the DMTIMER
TISTAT register (referred to as the SYSS register in HWMOD). Add the
appropriate HWMOD definitions so that HWMOD will check the software reset
status when performing a software reset of the DMTIMER.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim
.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/dmtimer.c |3 ---
arch/arm/plat-omap/include/plat/dmtimer.h |1 -
2 files changed, 4 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat
H4, OMAP3430 Beagle and OMAP4430 Panda that HWMOD is
configuring the dmtimer OCP_CFG register as expected for clock-events timer.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 13
it's
context will not be lost. Users should take care to service all interrupts
before disabling the timer.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/dmtimer.c |5 +
arch/arm/plat-omap/include/plat
. CONFIG_OMAP_32K_TIMER=y
2. CONFIG_OMAP_32K_TIMER=y and boot parameter clocksource=gp_timer
3. CONFIG_OMAP_32K_TIMER not set
4. CONFIG_OMAP_32K_TIMER not set and boot parameter clocksource=gp_timer
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm
that the interrupt disable function has been written so that it
can be used by all OMAP devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 31 +
arch/arm/plat-omap
timer, the function omap_dm_timer_reset() is now only being called for OMAP1
devices and OMAP1 does not use timer1 as a system timer. Therefore, remove the
check in omap_dm_timer_reset() so that timer1 is reset for OMAP1 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh
the match value must be loaded before the compare logic is enable.
The reset value for the timer counter and match registers is 0 and hence,
by enabling the compare logic before the actual match value is loaded a
spurious interrupt can be generated as the reset values match.
Signed-off-by: Jon Hunter
structure. So instead of looking up the clock again used the clock handle
that stored in the omap_dm_timer structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 14 --
1 file changed, 4 insertions(+), 10
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
On 11/08/12 18:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which
On 11/12/2012 02:34 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121112 10:22]:
This series includes several fixes for the OMAP DMTIMER driver. This is
based upon Tony Lindgren's current master branch [1].
You should be able to use omap-for-v3.8/dt as the base now
On 11/13/2012 03:14 AM, Igor Grinberg wrote:
On 11/12/12 21:15, Jon Hunter wrote:
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59
Jon Hunter (13):
ARM: OMAP: Add DMTIMER definitions for posted mode
ARM: OMAP3+: Implement timer workaround for errata i103 and i767
ARM: OMAP: Fix timer posted mode support
ARM: OMAP3: Correct HWMOD DMTIMER SYSC register declarations
ARM
://marc.info/?l=linux-omapm=135275633628412w=2
Jon Hunter (8):
ARM: OMAP: Clean-up dmtimer reset code
ARM: OMAP: Define omap_dm_timer_prepare function as static
ARM: OMAP: Don't store timers physical address
ARM: OMAP2+: Remove unnecessary local variable in timer code
ARM: OMAP: Remove
that for OMAP1 devices, the TIOCP_CFG register does not have the
clock-activity field and so when we reset the timer for an OMAP1 device we
only need to configure the idle-mode field in the TIOCP_CFG register.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c
The function omap_dm_timer_init_one() declares two local variables of
type int that are used to store the return value of functions called.
One such local variable is sufficient and so remove one of these local
variables.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2
The omap_dm_timer_prepare function is a local function only used in the
dmtimer.c file. Therefore, make this a static function and remove its
declaration from the dmtimer.h file.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c |2 +-
arch/arm/plat
The OMAP2+ system timer code stores the physical address of the timer
but never uses it. Remove this and clean-up the code by removing the
local variable size and changing the names of the local variables
mem_rsrc and irq_rsrc to mem and irq, respectively.
Signed-off-by: Jon Hunter jon-hun
Some source files are including dmtimer.h but not actually using any dmtimer
definitions or functions. Therefore, remove the inclusion dmtimer.h from these
source files.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap1/timer32k.c |1 -
arch/arm/mach-omap2
Move definition of dmtimer platform data structure in to its own header
under linux/platform_data.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap1/timer.c|1 +
arch/arm/mach-omap2/timer.c|2 ++
arch/arm/plat-omap/dmtimer.c
Move plat/dmtimer.h to plat-omap/dmtimer.h in order to support a single
zImage for ARM devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap1/pm.c |2 +-
arch/arm/mach-omap1/timer.c|2 +-
arch/arm/mach-omap2
Remove unnecessary declaration of structure omap_dm_timer from dmtimer.h and
move the actual declaration of structure omap_dm_timer towards top of dmtimer.h
to avoid any compilation errors.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/include/plat/dmtimer.h | 52
Fix ethernet support for OMAP2420 and remove legacy code for ethernet
configuration.
Jon Hunter (2):
ARM: OMAP2420: Fix ethernet support for OMAP2420 H4
ARM: OMAP: Remove debug-devices.c
arch/arm/mach-omap2/board-h4.c | 80 +++---
arch/arm/mach-omap2/debug
.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/debug-devices.h |9
arch/arm/plat-omap/Makefile |1 -
arch/arm/plat-omap/debug-devices.c | 93 ---
3 files changed, 103 deletions(-)
delete mode 100644 arch/arm/mach-omap2
to h4_init_debug() fixes ethernet support, however,
instead of using the legacy H4 code migrate the H4 to use the
gpmc_smc91x_init() function instead and remove the legacy H4 code.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/board-h4.c | 80
On 11/13/2012 04:26 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121113 10:15]:
Move plat/dmtimer.h to plat-omap/dmtimer.h in order to support a single
zImage for ARM devices.
Let's skip this one for now as it turns out this solution won't
work either for multiplatform without
On 11/13/2012 12:13 PM, Jon Hunter wrote:
Some source files are including dmtimer.h but not actually using any dmtimer
definitions or functions. Therefore, remove the inclusion dmtimer.h from these
source files.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap1
On 11/14/2012 12:53 PM, Tony Lindgren wrote:
Looks like enabling CONFIG_ARM_ERRATA_751472 causes omap4 blaze
to not boot when enabled. The ARM core on it is an earlier r1p2:
CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7d
Unfortunately I don't have the details of errata
On 11/15/2012 11:07 AM, Igor Mazanov wrote:
Remove inline from clock framework function definitions to
build the kernel with GCC 4.7
Adding Mike to the party ...
May be good to add some details about the exact problem seen.
I am seeing the same problem today with GCC 4.7 and Tony's master
601 - 700 of 1153 matches
Mail list logo
