On 12/13/2012 09:08 AM, Will Deacon wrote:
> On Wed, Dec 12, 2012 at 09:43:06PM +0000, 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 suc
On 12/13/2012 11:41 AM, Will Deacon wrote:
> On Wed, Dec 12, 2012 at 09:43:05PM +0000, 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 mod
On 12/13/2012 08:58 AM, Will Deacon wrote:
> Hi Jon,
>
> On Wed, Dec 12, 2012 at 09:43:04PM +0000, 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
>>
On 12/12/2012 10:33 PM, NeilBrown wrote:
> On Thu, 13 Dec 2012 14:06:35 +1100 NeilBrown 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.
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 wrote:
>
>> Hi Neil,
>>
>> On 12/12/2012 02:24 AM, NeilBrown wrote:
>>>
>>>
>>> This pa
On 12/12/2012 04:12 PM, Rob Herring wrote:
> On 12/12/2012 03:43 PM, 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 OM
On 12/12/2012 03:13 AM, Daniel Mack wrote:
> On 06.12.2012 17:19, Jon Hunter wrote:
>>
>> On 12/05/2012 05:24 PM, Grant Likely wrote:
>>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>>>> Hi Grant,
>>>>
>>>> On 12/05/2012 04:2
Add device-tree nodes for the two Cross Trigger Interface (CTI) modules
in the OMAP4 devices.
Signed-off-by: Jon Hunter
---
arch/arm/boot/dts/omap4.dtsi | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
following coresight macros ...
- coresight_unlock() --> Unlocks coresight module
- coresight_lock() --> Locks coresight module
Use the above macros for ETB, ETM and CTI. The do-while(0) statement
has been removed from the macro as it is not a multi-line macro.
Signed-off-by: Jon
supports CTI modules that have a single
CPU interrupt, however, could be extended in the future to support more
interrupts if a device requires this.
Signed-off-by: Jon Hunter
---
arch/arm/include/asm/cti.h | 153
drivers/Kconfig|2 +
drivers/amba
-next branch and Will Deacon's
patch for the CTI lock registers [2].
[1]
http://article.gmane.org/gmane.linux.ports.arm.kernel/204591/match=coresight+bus
[2]
http://article.gmane.org/gmane.linux.ports.arm.kernel/200199/match=fix+manipulation+debug+lock+register
Jon Hunter (5):
ARM: CORE
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
---
arch/arm/mach-omap2/cclock44xx_data.c |1 +
1 file changed, 1 insertion(+)
diff
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 use the CTI module to
route PMU events to the GIC interrupt module.
Signed-off-by: Jon Hunter
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;
>> +
>> +/* Enabl
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
> Signed-off-by: NeilBrown
>
> diff -
sible that the clock domain can have
a non-zero use count when the actual clock has a use count of 0.
Therefore, we should only bypass the clock-domain handling when both the
clock-domain and clock in the clock-domain have a use count of 0 and
warn when the clock-domain has a zero use count and the
On 12/06/2012 10:54 AM, Daniel Mack wrote:
> On 06.12.2012 17:22, Jon Hunter wrote:
>>
>> On 12/05/2012 06:03 PM, Tony Lindgren wrote:
>>> * Grant Likely [121205 15:26]:
>>>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>>>
On 12/05/2012 06:03 PM, Tony Lindgren wrote:
> * Grant Likely [121205 15:26]:
>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>>> On 12/05/2012 04:22 PM, Grant Likely wrote:
>>>>
>>>> Please, be specific. Use something like "ti,am3340-g
On 12/05/2012 05:24 PM, Grant Likely wrote:
> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>> Hi Grant,
>>
>> On 12/05/2012 04:22 PM, Grant Likely wrote:
>>> On Wed, 5 Dec 2012 20:09:31 +0100, Daniel Mack wrote:
>>>> This patch adds basic DT bi
Hi Grant,
On 12/05/2012 04:22 PM, Grant Likely wrote:
> On Wed, 5 Dec 2012 20:09:31 +0100, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instantiated from child nodes within the GPMC
>> node, and the only type of device that is currently
master +
> omap-next (branch omap-for-v3.8/cleanup-headers-gpmc)
>
> Generated from linux-next as of today, resolving one trivial include
> file rebase conflict.
>
> The only supported peripheral for now is NAND, but other types would be
> easy to add.
>
> Version 2 addr
On 12/05/2012 12:40 PM, Daniel Mack wrote:
> On 05.12.2012 19:33, Tony Lindgren wrote:
>> * Jon Hunter [121205 10:22]:
>>>
>>> On 12/05/2012 11:41 AM, Tony Lindgren wrote:
>>>> * Daniel Mack [121205 09:29]:
>>>>> On 05.12.2012 18:19, Tony
On 12/05/2012 11:41 AM, Tony Lindgren wrote:
> * Daniel Mack [121205 09:29]:
>> On 05.12.2012 18:19, Tony Lindgren wrote:
>>>
>>> The plat/cpu.h file will disappear after the merge window, which means
>>> omap2+ related drivers cannot use cpu_is_omap macros.
>>>
>>> For legacy booting systems, th
been 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
---
arch/arm/mach-omap2/cclock44xx_data.c |2 ++
arch/arm/mach-omap2/clock.h | 10 ++
arch/arm/mach-omap2/dpll3
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
---
arch/arm/mach-omap2/cclock44xx_data.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/mach
to set
the parent 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
[p...@pwsan.com: updated to apply after the CCF conversion]
Signed-off-by: Paul Walmsley
---
arch/arm/
longer work.
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap2/cclock44xx_data.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/cclock44xx_data.c
b/arch/arm/mach-omap2/cclock44xx_data.c
index a1f0b55..7c1ffe6 100644
--- a/arch/arm
that includes common
clock updates for OMAP4.
- Added new function table for non-M4X DPLLs which is now required after
enhancing support for OMAP4 DPLLs for 4X multiplier.
Jon Hunter (4):
ARM: OMAP4: Update timer clock aliases
ARM: OMAP4: Add function table for non-M4X dplls
ARM: OMAP4
On 11/29/2012 05:47 PM, Vinod Koul wrote:
> On Thu, 2012-11-29 at 16:24 -0600, Jon Hunter wrote:
>> When compiling the kernel with DMA engine support enabled and device-tree
>> support disabled, the following warnings are observed.
> Thanks, already committed same change
to
avoid the unused warnings.
Reported-by: Fengguang Wu
Signed-off-by: Jon Hunter
---
include/linux/of_dma.h | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/include/linux/of_dma.h b/include/linux/of_dma.h
index 84b64f8..b14a34f 100644
--- a/include/linux/of_dma
On 11/29/2012 02:42 PM, Daniel Mack wrote:
> On 29.11.2012 21:32, Jon Hunter wrote:
>>
>> On 11/29/2012 01:59 PM, Jon Hunter wrote:
>>>
>>> On 11/29/2012 10:01 AM, Daniel Mack wrote:
>>>> The am33xx is capable of handling bch error correction mod
On 11/29/2012 01:59 PM, Jon Hunter wrote:
>
> On 11/29/2012 10:01 AM, Daniel Mack wrote:
>> The am33xx is capable of handling bch error correction modes, so
>> enable that feature in the driver.
>>
>> Signed-off-by: Daniel Mack
>> ---
>> arch/arm/mach-
On 11/29/2012 10:01 AM, Daniel Mack wrote:
> This patch adds basic DT bindings for OMAP GPMC.
>
> The actual peripherals are instantiated from child nodes within the GPMC
> node, and the only type of device that is currently supported is NAND.
>
> Code was added to parse the generic GPMC timing
On 11/29/2012 10:01 AM, Daniel Mack wrote:
> The am33xx is capable of handling bch error correction modes, so
> enable that feature in the driver.
>
> Signed-off-by: Daniel Mack
> ---
> arch/arm/mach-omap2/gpmc-nand.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --
+
> oh = omap_hwmod_lookup(oh_name);
> if (!oh) {
> pr_err("Could not look up %s\n", oh_name);
Acked-by: Jon Hunter
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/majordomo-info.html
On 11/29/2012 05:21 AM, Paul Walmsley wrote:
> Hi Jon,
>
> On Wed, 7 Nov 2012, Jon Hunter wrote:
>
>> Fixes included, fixing up timer clock aliases for v3.8 and working
>> around ABE DPLL issue seen with latest u-boot bootloader (v2012.10).
>>
>> Testing inc
On 11/29/2012 04:53 AM, Paul Walmsley wrote:
> Hi Jon,
>
> On Wed, 7 Nov 2012, Jon Hunter wrote:
>
>> Commit "ARM: dts: OMAP4: Update timer addresses" updated the device-tree
>> names of the OMAP4 timers 5-7 because the default address for the timers
>>
initialisation function for the AM335x
device as it has no 32k-sync timer.
Fix this by adding the "__maybe_unused" compiler directive to the
omap2_sync32k_clocksource_init() function to indicate that this function
may be used for certain configurations.
Cc: Igor Grinberg
Signed-off-by:
init". Therefore, correct this
typo to resolve the above error and warning.
Cc: Igor Grinberg
Reported-by: Tony Lindgren
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
Acked-by: Igor Grinberg
---
arch/arm/mach-omap2/timer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(
Shilimkar
Reported-by: Tony Lindgren
Signed-off-by: Jon Hunter
Acked-by Santosh Shilimkar
---
arch/arm/mach-omap2/Kconfig |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 813c267..500f2f6 100644
--- a/arch/arm
r.c:213:12: warning: symbol
'omap_dm_timer_get_errata' was not declared. Should it be static?
Add static to function declaration to fix warnings.
Signed-off-by: Vaibhav Hiremath
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap2/timer.c |4 ++--
1 file changed, 2 insertions(+), 2 deleti
ybe_unused (thanks Igor!)
- Add Vaibhav's fixes for sparse warnings
Jon Hunter (3):
ARM: OMAP2+: Fix realtime_counter_init warning in timer.c
ARM: OMAP4: Fix build error and warning in timer.c
ARM: AM335x: Fix warning in timer.c
Vaibhav Hiremath (1):
ARM: OMAP2+: Fix sparse warn
On 11/28/2012 09:18 AM, Russell King - ARM Linux wrote:
> On Tue, Nov 20, 2012 at 05:00:19PM -0600, Jon Hunter wrote:
>>
>> On 11/20/2012 11:57 AM, Tony Lindgren wrote:
>>> * Russell King - ARM Linux [121117 01:35]:
>>>> On Wed, Nov 14, 2012 at 09:26:43AM +
On 11/28/2012 01:20 AM, Santosh Shilimkar wrote:
> On Wednesday 28 November 2012 12:16 PM, Igor Grinberg wrote:
>> On 11/28/12 08:28, Santosh Shilimkar wrote:
>>> On Wednesday 28 November 2012 07:45 AM, Jon Hunter wrote:
>>>> When compiling the ker
On 11/28/2012 09:55 AM, Santosh Shilimkar wrote:
> On Wednesday 28 November 2012 09:17 PM, Jon Hunter wrote:
>>
>> On 11/28/2012 12:09 AM, Santosh Shilimkar wrote:
>>> On Wednesday 28 November 2012 07:45 AM, Jon Hunter wrote:
>>>> In commit fa6d79d (ARM: OMAP:
On 11/28/2012 12:09 AM, Santosh Shilimkar wrote:
> On Wednesday 28 November 2012 07:45 AM, Jon Hunter wrote:
>> In commit fa6d79d (ARM: OMAP: Add initialisation for the real-time
>> counter), the function realtime_counter_init() was added. However, if
>> the kernel
initialisation function for the AM335x
device as it has no 32k-sync timer.
Fix this by only including the omap2_sync32k_clocksource_init() function
if either OMAP2, OMAP3, OMAP4 or OMAP5 devices are enabled.
Cc: Igor Grinberg
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap2/timer.c |3 +++
1
init". Therefore, correct this
typo to resolve the above error and warning.
Cc: Igor Grinberg
Reported-by: Tony Lindgren
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap2/timer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/timer.c b/arc
Reported-by: Tony Lindgren
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap2/Kconfig |4
arch/arm/mach-omap2/timer.c |7 ++-
2 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 813c267..ea88b7d 100644
--- a
Fixes for build warnings and errors seen with various kernel
configuration combinations.
Jon Hunter (3):
ARM: OMAP2+: Fix realtime_counter_init warning in timer.c
ARM: OMAP4: Fix build error and warning in timer.c
ARM: AM335x: Fix warning in timer.c
arch/arm/mach-omap2/Kconfig |4
continue;
> }
>
> - prom_add_property(np, &device_disabled);
> + of_add_property(np, &device_disabled);
> return np;
> }
I tested this on the AM335x device and it is working fine. So ...
Acked-by:
On 11/20/2012 11:57 AM, Tony Lindgren wrote:
> * Russell King - ARM Linux [121117 01:35]:
>> On Wed, Nov 14, 2012 at 09:26:43AM +, Russell King - ARM Linux wrote:
>>> OMAP* allnoconfig fails:
>>>
>>> arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
>>> twl-common.c:(.t
would be
> easy to add.
>
> Version 2 addresses details pointed out by Jon Hunter, Afzal Mohammed
> and Rob Herring:
>
> - add "reg" and "ti,hwmod" properties to Documentation
> - use generic of_mtd functions and the property names defined by them,
r is not wired on the board.
>Cirrently, the the timer is chosen in the machine_desc structure on
Nit ...
s/Cirrently/Currently
Otherwise ...
Reviewed-by: Jon Hunter
Thanks for updating this!
Cheers
Jon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body o
On 11/16/2012 08:44 PM, Joel A Fernandes wrote:
> Hi Jon,
>
> On Fri, Nov 16, 2012 at 6:12 PM, Jon Hunter wrote:
>>> diff --git a/arch/arm/mach-omap2/clock33xx_data.c
>>> b/arch/arm/mach-omap2/clock33xx_data.c
>>> index b7b7995..d0b4313 100644
>>&g
On 11/16/2012 05:44 PM, Joel A Fernandes wrote:
> Set ENABLE_ON_INIT for debugss clock so that it is on during init and the
> usecount is incremented.
> Not doing so causes kernel to disable debugss clock to save power when
> CONFIG_OMAP_RESET_CLOCKS
> is set, causing a JTAG disconnect.
>
> Sig
cussed.
I have also included the compilation warning fix for sync-32k
reported by Kevin Hilman.
--------
Jon Hunter (8):
ARM: OMAP: Clean-up dmtimer reset code
ARM: OMAP: Define omap_dm_timer_prepare function as static
ARM: O
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 throu
On 11/16/2012 01:52 AM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 15, 2012 at 03:35:47PM -0600, Jon Hunter wrote:
>>
>> On 11/15/2012 02:45 PM, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Thu, Nov 15, 2012 at 01:44:04PM -0600, Jon Hunter wrote:
>
On 11/15/2012 02:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 15, 2012 at 01:44:04PM -0600, Jon Hunter wrote:
>> +static struct of_device_id omap_counter_match[] __initdata = {
>
> not directly related to $SUBJECT, but shouldn't this be static const
> __initcons
imer.c:163:28: warning: 'omap_counter_match'
defined but not used [-Wunused-variable]
Move the definition of omap_counter_match to avoid this warning when
CONFIG_OMAP_32K_TIMER is not set.
Thanks to Kevin Hilman for tracking down and reporting this problem.
Reported-by: Kevin Hilam
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
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 erra
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
> ---
> arch/arm/
On 11/13/2012 04:26 PM, Tony Lindgren wrote:
> * Jon Hunter [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 eithe
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
---
arch/arm/mach-omap2/board-h4.c | 80 ++--
1 file
.
Signed-off-by: Jon Hunter
---
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/debug-devices.h
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
Move plat/dmtimer.h to plat-omap/dmtimer.h in order to support a single
zImage for ARM devices.
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap1/pm.c |2 +-
arch/arm/mach-omap1/timer.c|2 +-
arch/arm/mach-omap2
Move definition of dmtimer platform data structure in to its own header
under .
Signed-off-by: Jon Hunter
---
arch/arm/mach-omap1/timer.c|1 +
arch/arm/mach-omap2/timer.c|2 ++
arch/arm/plat-omap/dmtimer.c |2 ++
arch/arm/plat-omap
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
---
arch/arm/mach-omap1/timer32k.c |1 -
arch/arm/mach-omap2/omap_hwmod_2420_data.c
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
---
arch/arm/plat-omap/include/plat/dmtimer.h | 52
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
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
---
arch/arm/plat-omap/dmtimer.c |2 +-
arch/arm/plat-omap/include/plat
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
---
arch/arm/mach-omap2/timer.c | 11
lease note 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
---
arch/arm/plat-omap/dmtimer.c
://marc.info/?l=linux-omap&m=135275633628412&w=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:
for OMAP1
--------
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
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,
On 11/12/2012 02:34 PM, Tony Lindgren wrote:
> * Jon Hunter [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 b
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 G
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
> On 11/08/12 18:20, Tony Lindgren wrote:
>> * Igor Grinberg [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.
>>>
>>> W
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
Acked-by: Santosh Shilimkar
---
arch/arm/plat-omap/dmtimer.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/arch/arm/plat
n
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 H
that the interrupt disable function has been written so that it
can be used by all OMAP devices.
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
---
arch/arm/plat-omap/dmtimer.c | 31 +
arch/arm/plat-omap/include/plat/dmtimer.h |3 ++-
2 files
. 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
Acked-by: Santosh Shilimkar
---
arch/ar
it's
context will not be lost. Users should take care to service all interrupts
before disabling the timer.
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
---
arch/arm/plat-omap/dmtimer.c |5 +
arch/arm/plat-omap/include/plat/dmtimer.h |1 -
2 files chang
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
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 13 +
arch/arm/mach-omap2
.
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
---
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 d4f9541..320d103
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
Acked-by: Santosh Shilimkar
---
arch
0 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
Acked-by: Santosh Shilimkar
---
arch/arm/mach-
. 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
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 27 ++-
1 file changed
function was introduced. 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
Acked-by: Santosh Shilimkar
---
arch/arm/plat-omap/dmtimer.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff
make it
clear that posted mode is being used add some definitions so that it is more
readable.
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/timer.c | 17 ++---
arch/arm/plat-omap/include/plat/dmtimer.h |4
2 files changed, 14
impacts AM33xx
devices.
Signed-off-by: Jon Hunter
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/timer.c | 49 ++-
arch/arm/plat-omap/dmtimer.c |3 +-
arch/arm/plat-omap/include/plat/dmtimer.h | 52 +++--
3
timer 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 DM
On 11/09/2012 06:21 PM, Tony Lindgren wrote:
> * Jon Hunter [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
On 11/09/2012 05:50 PM, Tony Lindgren wrote:
> * Jon Hunter [121109 15:44]:
>>
>> On 11/09/2012 03:10 PM, Tony Lindgren wrote:
>>> * Jon Hunter [121109 08:31]:
>>>>
>>>> On 11/09/2012 10:22 AM, Tony Lindgren wrote:
>>>>> * Jon Hunt
On 11/09/2012 03:10 PM, Tony Lindgren wrote:
> * Jon Hunter [121109 08:31]:
>>
>> On 11/09/2012 10:22 AM, Tony Lindgren wrote:
>>> * Jon Hunter [121109 08:21]:
>>>> If the header soc.h is included more than once in a source (for example
>>>> once
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 it
401 - 500 of 1176 matches
Mail list logo
