On 03/05/13 03:02, Mark Rutland wrote:
+
+static void dummy_set_mode(enum clock_event_mode mode,
+ struct clock_event_device *evt)
+{
+ /*
+* Core clockevents code will call this when exchanging timer devices.
+* We don't need to do anything here.
+*/
generic dummy timer driver
* Split out omap changes into new patch
Mark Rutland (1):
clocksource: add generic dummy timer driver
Stephen Boyd (9):
ARM: smp: Remove duplicate dummy timer implementation
ARM: smp_twd: Divorce smp_twd from local timer API
ARM: OMAP2+: Divorce from local timer API
Separate the marco local timers from the local timer API. This
will allow us to remove ARM local timer support in the near future
and gets us closer to moving this driver to drivers/clocksource.
Cc: Barry Song baohua.s...@csr.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
There are no more users of this API, remove it.
Cc: Russell King li...@arm.linux.org.uk
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig | 10 --
arch/arm/include/asm/localtimer.h | 34 ---
arch/arm/kernel/smp.c | 69
Separate the smp_twd timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Russell King li...@arm.linux.org.uk
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm
Separate the armada 370xp local timers from the local timer API.
This will allow us to remove ARM local timer support in the near
future and makes this driver multi-architecture friendly.
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach-msm/timer.c | 125 +-
1 file changed, 67 insertions(+), 58 deletions(-)
diff --git a/arch/arm/mach-msm/timer.c b/arch/arm/mach-msm/timer.c
index 2969027..4675c5e 100644
Separate the mct local timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
On 03/07/13 16:40, Tony Lindgren wrote:
Hi,
* Stephen Boyd sb...@codeaurora.org [130306 17:53]:
Separate the smp_twd timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource
On 03/08/13 11:48, Tony Lindgren wrote:
* Stephen Boyd sb...@codeaurora.org [130308 10:21]:
diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
index 081de6f..4ea3e9d 100644
--- a/arch/arm/kernel/smp_twd.c
+++ b/arch/arm/kernel/smp_twd.c
@@ -227,7 +227,7 @@ static void
On 03/08/13 12:29, Tony Lindgren wrote:
Applying that does not seem to help, but you might want to get vexpress
running anyways for some multiplatform sanity checks.
I just built and installed qemu-linaro from their git, then ran the
command above. Looks like stock qemu does not work for
On 03/11/13 10:28, Tony Lindgren wrote:
* Stephen Boyd sb...@codeaurora.org [130308 17:10]:
On 03/08/13 12:29, Tony Lindgren wrote:
Applying that does not seem to help, but you might want to get vexpress
running anyways for some multiplatform sanity checks.
I just built and installed qemu
On 03/11/13 15:50, Tony Lindgren wrote:
* Stephen Boyd sb...@codeaurora.org [130311 15:22]:
Ok. qemu works for me before applying my patches. I've added this into
the series before this patch to fix the boot issue.
OK thanks:
Actually, it's worse. From reading the code it looks like quite
On 03/12/13 11:41, David Brown wrote:
With device tree, and deferred probe, it is no longer necessary to
make sure that the ssbi bus driver is initialized very early. Restore
to a regular module_init().
Signed-off-by: David Brown dav...@codeaurora.org
---
drivers/ssbi/ssbi.c | 2 +-
1
On 03/07/13 22:41, Will Deacon wrote:
On Wed, Mar 06, 2013 at 05:20:32AM +, Stephen Boyd wrote:
On 03/05/13 14:03, Stephen Boyd wrote:
On 03/05/13 00:34, Will Deacon wrote:
I was looking at this the other day and wondered whether we could set
HWCAP_IDIV in __v7_setup, depending
While attempting to upstream a patch to add the IDIV hwcap for
Krait processors, Will suggested we move the code to read the
ISAR0 register. This patchset does that and also works around
the early Krait CPU designs that don't follow the latest ARM ARM
for the ISAR0 register.
Stephen Boyd (3
-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
index 3f6cbb2..e2c8bbf 100644
--- a/arch/arm/kernel/setup.c
+++ b/arch/arm/kernel/setup.c
@@ -484,7 +484,7 @@ static
step...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/setup.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
index bd27a70..34ec24e 100644
--- a/arch/arm/kernel/setup.c
+++ b/arch/arm/kernel/setup.c
cpu variant that
supports these instructions.
Cc: Will Deacon will.dea...@arm.com
Cc: Stepan Moskovchenko step...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/setup.c | 20
arch/arm/mm/proc-v7.S | 4 ++--
2 files changed, 22 insertions
Now that the TWD doesn't rely on the local timer API, OMAP can
stop selecting it in Kconfig and relying on the config option to
decide if it should call smp_twd functions.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Stephen Boyd sb
Separate the armada 370xp local timers from the local timer API.
This will allow us to remove ARM local timer support in the near
future and makes this driver multi-architecture friendly.
Cc: Gregory CLEMENT gregory.clem...@free-electrons.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
There are no more users of this API, remove it.
Cc: Russell King li...@arm.linux.org.uk
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig | 10 --
arch/arm/include/asm/localtimer.h | 34 ---
arch
...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach-msm/timer.c | 125 +-
1 file changed, 67 insertions(+), 58 deletions(-)
diff --git a/arch/arm/mach-msm/timer.c b/arch/arm/mach-msm/timer.c
index 2969027..4675c5e 100644
Separate the marco local timers from the local timer API. This
will allow us to remove ARM local timer support in the near future
and gets us closer to moving this driver to drivers/clocksource.
Cc: Barry Song baohua.s...@csr.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
Separate the mct local timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
Drop ARM's version of the dummy timer now that we have a generic
implementation in drivers/clocksource.
Cc: Russell King li...@arm.linux.org.uk
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/smp.c | 22 ++
1 file changed, 2 insertions(+), 20 deletions
timer using this facility.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Cc: John Stultz john.stu...@linaro.org
Cc: Thomas Gleixner t...@linutronix.de
[sboyd: Make percpu data static and use __this_cpu_ptr()]
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/Makefile
We don't want executable permissions set on files such as
devicetree syntax files, text files, defconfig files, or binary
hex files.
Cc: Andy Whitcroft a...@canonical.com
Cc: Joe Perches j...@perches.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
scripts/checkpatch.pl | 2 +-
1 file
from that function it doesn't blow up.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/sched_clock.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/kernel/sched_clock.c b/arch/arm/kernel/sched_clock.c
index bd6f56b..59d2adb 100644
--- a/arch/arm
On 03/05/13 00:31, Arnd Bergmann wrote:
On Monday 04 March 2013, Stephen Boyd wrote:
Scorpion processors have always been v7 CPUs. Fix the Kconfig
text to reflect this.
Reported-by: Stepan Moskovchenko step...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm
it's duplicate work
that is eventually done in the set_next_event() callback.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach-msm/timer.c | 41 +++--
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git a/arch/arm/mach-msm/timer.c b/arch
the
status registers, etc.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
.../devicetree/bindings/arm/msm/timer.txt | 41 ++-
arch/arm/boot/dts/msm8660-surf.dts | 20 ++
arch/arm/boot/dts/msm8960-cdp.dts | 22 +++---
arch/arm/mach-msm
On 3/5/2013 2:34 PM, Arnd Bergmann wrote:
On Tuesday 05 March 2013, Stephen Boyd wrote:
On 02/27/13 15:43, Stephen Warren wrote:
Seems simple enough it doesn't really need many, but for Tegra,
Acked-by: Stephen Warren swar...@nvidia.com
Which kernel is this going into? It's possible Tegra
On 03/17/13 07:28, Will Deacon wrote:
On Wed, Mar 13, 2013 at 01:32:01AM +, Stephen Boyd wrote:
Some early versions of the Krait CPU design incorrectly indicate
that they only support the UDIV and SDIV instructions in Thumb
mode when they actually support them in ARM and Thumb mode
On 03/17/13 07:36, Will Deacon wrote:
On Wed, Mar 13, 2013 at 01:32:00AM +, Stephen Boyd wrote:
The ISAR0 register indicates support for the SDIV and UDIV
instructions in both the Thumb and ARM instruction set. Read the
register to detect the supported instructions and update
(1):
ARM: Work around faulty ISAR0 register in some Krait CPUs
Stephen Boyd (2):
ARM: Clear IDIVT hwcap if CONFIG_ARM_THUMB=n
ARM: Detect support for SDIV/UDIV from ISAR0 register
arch/arm/kernel/setup.c | 22 +-
arch/arm/mm/proc-v7.S | 19 +--
2 files
cpu variant that
supports these instructions.
Acked-by: Will Deacon will.dea...@arm.com
Cc: Stepan Moskovchenko step...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/setup.c | 20
arch/arm/mm/proc-v7.S | 4 ++--
2 files changed, 22
will.dea...@arm.com
Signed-off-by: Stepan Moskovchenko step...@codeaurora.org
[sboyd: Rewrote commit text to reflect real reasoning now that
we autodetect udiv/sdiv]
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mm/proc-v7.S | 15 +++
1 file changed, 15 insertions
On 03/18/13 11:34, Will Deacon wrote:
On Mon, Mar 18, 2013 at 06:28:57PM +, Stephen Boyd wrote:
From: Stepan Moskovchenko step...@codeaurora.org
Some early versions of the Krait CPU design incorrectly indicate
that they only support the UDIV and SDIV instructions in Thumb
mode when
From: Abhijeet Dharmapurikar adhar...@codeaurora.org
The genirq layer expects a 0 in case of failure but the code is
returning -ENXIO. Fix it.
Signed-off-by: Abhijeet Dharmapurikar adhar...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/irqchip/irq-gic.c | 3 ++-
1
On 03/20/13 10:44, Gregory CLEMENT wrote:
On 03/20/2013 06:26 PM, Gregory CLEMENT wrote:
On 03/20/2013 06:20 PM, Stephen Boyd wrote:
On 03/20/13 10:09, Gregory CLEMENT wrote:
On 03/13/2013 07:17 PM, Stephen Boyd wrote:
Separate the armada 370xp local timers from the local timer API
On 03/14/13 17:08, Stephen Boyd wrote:
cyc_to_sched_clock() is called by sched_clock() and cyc_to_ns()
is called by cyc_to_sched_clock(). I suspect that some compilers
inline both of these functions into sched_clock() and so we've
been getting away without having a notrace marking. It seems
On 03/21/13 11:09, Mark Rutland wrote:
Hi Stephen,
I've just been trying to test the dummy timer, and realised it's broken, as it
registers a cpu notifier from a device_initcall (after SMP's been brought up),
and doesn't ensure all active CPUs have been set up. Evidently no-one else has
On 03/22/13 11:03, Mark Rutland wrote:
On Thu, Mar 21, 2013 at 06:13:17PM +, Stephen Boyd wrote:
On 03/21/13 11:09, Mark Rutland wrote:
Hi Stephen,
I've just been trying to test the dummy timer, and realised it's broken, as
it
registers a cpu notifier from a device_initcall (after
On 03/25/13 11:00, Mark Rutland wrote:
I've spent the last few hours trying to get the dummy_timer driver working
on
tc2 with the sp804 as the broadcast source (with architected timer support
disabled). It turns out that having dummy timer's rating so low means that
it
won't be selected
On 03/19/13 16:05, Stephen Boyd wrote:
From: Abhijeet Dharmapurikar adhar...@codeaurora.org
The genirq layer expects a 0 in case of failure but the code is
returning -ENXIO. Fix it.
Signed-off-by: Abhijeet Dharmapurikar adhar...@codeaurora.org
Signed-off-by: Stephen Boyd sb
On 03/16/13 12:32, Stephen Boyd wrote:
On 3/5/2013 2:34 PM, Arnd Bergmann wrote:
On Tuesday 05 March 2013, Stephen Boyd wrote:
On 02/27/13 15:43, Stephen Warren wrote:
Seems simple enough it doesn't really need many, but for Tegra,
Acked-by: Stephen Warren swar...@nvidia.com
Which kernel
On 03/21/13 10:49, Stephen Boyd wrote:
On 03/14/13 17:08, Stephen Boyd wrote:
cyc_to_sched_clock() is called by sched_clock() and cyc_to_ns()
is called by cyc_to_sched_clock(). I suspect that some compilers
inline both of these functions into sched_clock() and so we've
been getting away
the twd driver on a UP
system? Or would the overhead of handling frequency change make this
pointless?
I don't see why not but I don't have any interest in pursuing it.
On Wed, Mar 13, 2013 at 06:17:49PM +, Stephen Boyd wrote:
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5b71469
the warning.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/arm_arch_timer.c
b/drivers
On 03/26/13 04:28, Mark Rutland wrote:
On Tue, Mar 26, 2013 at 02:14:53AM +, Stephen Boyd wrote:
Ok. Thanks for clearing up my confusion.
Like you say, increasing the dummy timer rating seems like a hack. But
it also sounds like you want to keep the dummy timer driver fully self
On 4/2/2013 1:31 PM, Stephen Boyd wrote:
Hot-plugging with CONFIG_DEBUG_PREEMPT=y on a device with arm
architected timers causes a slew of using smp_processor_id() in
preemptible warnings:
BUG: using smp_processor_id() in preemptible [] code: sh/111
caller
On 04/05/13 03:04, Marc Zyngier wrote:
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/arm_arch_timer.c
b/drivers/clocksource/arm_arch_timer.c
index d7ad425..5928c29 100644
---
down into the cases to force the
checks to occur only in non-preemptible contexts.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
Changes since v1:
* Pushed down this_cpu_ptr and added a comment
drivers/clocksource
as there isn't a higher rated tick
device and any global clockevent will be bumped out into
broadcast mode, fixing the problem described above.
Reported-by: Mark Rutland mark.rutl...@arm.com
Cc: John Stultz john.stu...@linaro.org
Cc: Thomas Gleixner t...@linutronix.de
Signed-off-by: Stephen Boyd sb
:
* Picked up Mark's generic dummy timer driver
* Split out omap changes into new patch
Mark Rutland (1):
clocksource: add generic dummy timer driver
Stephen Boyd (10):
clockevents: Prefer CPU local devices over global devices
ARM: smp: Remove duplicate dummy timer implementation
ARM
Separate the mct local timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/time-armada-370-xp.c | 3 ++-
include/linux/time-armada-370-xp.h | 4 +---
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/clocksource/time-armada-370-xp.c
b/drivers/clocksource/time-armada-370-xp.c
-electrons.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/time-armada-370-xp.c | 89 +++-
1 file changed, 41 insertions(+), 48 deletions(-)
diff --git a/drivers/clocksource/time-armada-370-xp.c
b/drivers/clocksource/time-armada-370-xp.c
...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach-msm/timer.c | 127 +-
1 file changed, 69 insertions(+), 58 deletions(-)
diff --git a/arch/arm/mach-msm/timer.c b/arch/arm/mach-msm/timer.c
index 2969027..f4bc4a6 100644
Now that the TWD doesn't rely on the local timer API, OMAP can
stop selecting it in Kconfig and relying on the config option to
decide if it should call smp_twd functions.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Stephen Boyd sb
There are no more users of this API, remove it.
Cc: Russell King li...@arm.linux.org.uk
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig | 10 --
arch/arm/include/asm/localtimer.h | 34 ---
arch
Separate the marco local timers from the local timer API. This
will allow us to remove ARM local timer support in the near future
and gets us closer to moving this driver to drivers/clocksource.
Cc: Barry Song baohua.s...@csr.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach
Drop ARM's version of the dummy timer now that we have a generic
implementation in drivers/clocksource.
Cc: Russell King li...@arm.linux.org.uk
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/smp.c | 22 ++
1 file changed, 2 insertions(+), 20 deletions
if more than one CPU possible]
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/Makefile | 1 +
drivers/clocksource/dummy_timer.c | 69 +++
2 files changed, 70 insertions(+)
create mode 100644 drivers/clocksource/dummy_timer.c
diff
mark.rutl...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig | 2 +-
arch/arm/kernel/smp_twd.c | 64 +++
2 files changed, 44 insertions(+), 22 deletions(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 13b7394
patch adds support for mmio timers.
Patches are based on a recent patch from Mark that removes the
physical count reading (clocksource: arch_timer: use virtual counter,
message id 1364404312-4427-4-git-send-email-mark.rutl...@arm.com).
Stephen Boyd (4):
Documentation: Add memory mapped ARM
...@lists.ozlabs.org
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
.../devicetree/bindings/arm/arch_timer.txt | 62 --
1 file changed, 59 insertions(+), 3 deletions(-)
diff --git a/Documentation
support, although it should be
possible to support it by searching for the hyp frame instead of
the kernel frame and updating KVM timers to support it.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource
...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/include/asm/arch_timer.h| 5 ++--
arch/arm64/include/asm/arch_timer.h | 4 ++--
drivers/clocksource/arm_arch_timer.c | 44
3 files changed, 34 insertions(+), 19 deletions(-)
diff --git
On 04/09/13 02:38, Mark Rutland wrote:
On Tue, Apr 09, 2013 at 03:30:22AM +0100, Stephen Boyd wrote:
-static inline u32 arch_timer_reg_read(const int access, const int reg)
+static inline u32 __arch_timer_reg_read(const int access, const int reg)
Rather than prefixing all of these with __, why
On 03/26/13 10:34, Stephen Boyd wrote:
On 03/16/13 12:32, Stephen Boyd wrote:
On 3/5/2013 2:34 PM, Arnd Bergmann wrote:
On Tuesday 05 March 2013, Stephen Boyd wrote:
On 02/27/13 15:43, Stephen Warren wrote:
Seems simple enough it doesn't really need many, but for Tegra,
Acked-by: Stephen
On 04/09/13 03:33, Mark Rutland wrote:
On Mon, Apr 08, 2013 at 10:27:23PM +0100, Stephen Boyd wrote:
On an SMP system with only one global clockevent and a dummy
clockevent per CPU we run into problems. We want the dummy
clockevents to be registered as the per CPU tick devices, but
we can
-by: Stephen Boyd sb...@codeaurora.org
---
Nobody has noticed this so far so I'm ok waiting for 3.10 on this one. Also
it doesn't improve stability (debug feature) so I don't see a reason to send
it to stable.
arch/arm/mach-msm/include/mach/uncompress.h | 2 +-
1 file changed, 1 insertion(+), 1
On 04/11/13 04:24, Mark Rutland wrote:
Could we say the reg for the second view is optional?
Yes, that's already covered in the binding.
Might we have a hardware / firmware configuration where the kernel can only
access
the secondary view?
I don't see how this is possible. The CNTACRn
and commented why for arm64
* Updated DT binding to replace frame-id with frame-number and use status
property
Stephen Boyd (4):
Documentation: Add memory mapped ARM architected timer binding
ARM: arch_timers: Pass clock event to set_mode callback
clocksource: arch_timer: Push the read/write
...@lists.ozlabs.org
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
.../devicetree/bindings/arm/arch_timer.txt | 59 --
1 file changed, 56 insertions(+), 3 deletions(-)
diff --git a/Documentation
for hypervisor support, although it
should be possible to support it by searching for at least two
frames where one frame has the virtual capability and then
updating KVM timers to support it.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb
...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/include/asm/arch_timer.h| 5 ++--
arch/arm64/include/asm/arch_timer.h | 4 ++--
drivers/clocksource/arm_arch_timer.c | 44
3 files changed, 34 insertions(+), 19 deletions(-)
diff --git
There isn't any reason why we don't pass the event here and we'll
need it in the near future for memory mapped arch timers anyway.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/arm_arch_timer.c
On 04/06/13 03:41, Marc Zyngier wrote:
On Fri, 5 Apr 2013 13:57:29 -0700, Stephen Boyd sb...@codeaurora.org
wrote:
Hot-plugging with CONFIG_DEBUG_PREEMPT=y on a device with arm
architected timers causes a slew of using smp_processor_id() in
preemptible warnings:
BUG: using
On 04/15/13 14:20, Rob Herring wrote:
On Fri, Apr 12, 2013 at 7:27 PM, Stephen Boyd sb...@codeaurora.org wrote:
@@ -26,3 +30,52 @@ Example:
1 10 0xf08;
clock-frequency = 1;
};
+
+** Memory mapped timer node properties
a branch on 3.9-rc5 and a merge resolution with for-next in
arm-soc that you can pull to look at.
If not I will have to resend the series.
Thanks,
Stephen
On 04/08/13 14:27, Stephen Boyd wrote:
In light of Mark Rutland's recent work on divorcing the ARM architected
timers from the ARM local timer API
down into the cases to force the
checks to occur only in non-preemptible contexts.
Cc: John Stultz john.stu...@linaro.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Mark Rutland mark.rutl...@arm.com
Acked-by: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
On 03/26/13 10:35, Stephen Boyd wrote:
On 03/21/13 10:49, Stephen Boyd wrote:
On 03/14/13 17:08, Stephen Boyd wrote:
cyc_to_sched_clock() is called by sched_clock() and cyc_to_ns()
is called by cyc_to_sched_clock(). I suspect that some compilers
inline both of these functions into sched_clock
in smp_twd from Tony Lindgren's testing
* Move smp_twd to use late_time_init hook
* Collected Acks
Changes since v1:
* Picked up Mark's generic dummy timer driver
* Split out omap changes into new patch
Mark Rutland (1):
clocksource: add generic dummy timer driver
Stephen Boyd (10
...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/mach-msm/timer.c | 122 ++
1 file changed, 68 insertions(+), 54 deletions(-)
diff --git a/arch/arm/mach-msm/timer.c b/arch/arm/mach-msm/timer.c
index 284313f..02466d4 100644
-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/time-armada-370-xp.c | 3 ++-
include/linux/time-armada-370-xp.h | 4 +---
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/clocksource/time-armada-370-xp.c
b/drivers/clocksource/time-armada-370-xp.c
index
There are no more users of this API, remove it.
Cc: Russell King li...@arm.linux.org.uk
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig | 10 --
arch/arm/include/asm/localtimer.h | 34 ---
arch
-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/Makefile | 1 +
drivers/clocksource/dummy_timer.c | 69 +++
2 files changed, 70 insertions(+)
create mode 100644 drivers/clocksource/dummy_timer.c
diff --git a/drivers/clocksource/Makefile b
-electrons.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/clocksource/time-armada-370-xp.c | 89 +++-
1 file changed, 41 insertions(+), 48 deletions(-)
diff --git a/drivers/clocksource/time-armada-370-xp.c
b/drivers/clocksource/time-armada-370-xp.c
Separate the mct local timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Kukjin Kim kgene@samsung.com
Cc: Thomas Abraham thomas.abra...@linaro.org
Signed-off-by: Stephen
Separate the marco local timers from the local timer API. This
will allow us to remove ARM local timer support in the near future
and gets us closer to moving this driver to drivers/clocksource.
Cc: Barry Song baohua.s...@csr.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers
as there isn't a higher rated tick
device and any global clockevent will be bumped out into
broadcast mode, fixing the problem described above.
Reported-by: Mark Rutland mark.rutl...@arm.com
Tested-by: Mark Rutland mark.rutl...@arm.com
Cc: John Stultz john.stu...@linaro.org
Signed-off-by: Stephen
This is what I was thinking. I don't see why we can't move this to generic code
and have arm64 use it too. Those patches will follow once I find an arm64
compiler.
First two patches should probably go in even if the 64 bit stuff doesn't go in
at the same time.
Stephen Boyd (4):
ARM
The needs_suspend member is unused now that we always do the
suspend/resume handling (see 6a4dae5 (ARM: 7565/1: sched: stop
sched_clock() during suspend, 2012-10-23)).
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/sched_clock.c | 1 -
1 file changed, 1 deletion(-)
diff
with sched_clock returning
gigantic numbers. Second, there is no support for suspend/resume
handling so problems such as discussed in 6a4dae5 (ARM: 7565/1:
sched: stop sched_clock() during suspend, 2012-10-23) can happen.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/include/asm
handling that the ARM
sched_clock code already has.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
Maybe we need a union for the epoch_ns usage?
arch/arm/include/asm/sched_clock.h | 2 +
arch/arm/kernel/sched_clock.c | 101 +++--
2 files changed, 77
as possible.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/sched_clock.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/kernel/sched_clock.c b/arch/arm/kernel/sched_clock.c
index 48ab64a..29ac613 100644
--- a/arch/arm/kernel/sched_clock.c
On 04/22/13 03:48, Will Deacon wrote:
Hi Stephen,
On Sat, Apr 20, 2013 at 01:29:05AM +0100, Stephen Boyd wrote:
The arm architected system counter has at least 56 bits of
useable bits. Add support to ARM's sched_clock implementation for
counters with more than 32 bits so we can avoid
201 - 300 of 1756 matches
Mail list logo
