optional for a frame to support a virtual timer.
Cc: devicetree-disc...@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
on.
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Marc Zyngier marc.zyng...@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
.
It might be worth pointing out that if dummy timers are only registered
when there's more than one CPU, UP behaviour won't degrade from the
current state of affairs.
Reported-by: Mark Rutland mark.rutl...@arm.com
Cc: John Stultz john.stu...@linaro.org
Cc: Thomas Gleixner t...@linutronix.de
On Tue, Apr 09, 2013 at 05:42:38PM +0100, Stephen Boyd wrote:
On 04/09/13 02:08, Mark Rutland wrote:
On Tue, Apr 09, 2013 at 03:30:20AM +0100, Stephen Boyd wrote:
-** Timer node properties:
+** CP15 Timer node properties:
- compatible : Should at least contain one of
arm
On Thu, Apr 11, 2013 at 03:52:52AM +0100, Stephen Boyd wrote:
On 04/10/13 03:13, Mark Rutland wrote:
+
+- #size-cells : Must be 1.
+
+- ranges : Indicates parent and child bus address space are the same.
+
Similarly, what if someone wants to write a more complex mapping for some
On Thu, Mar 28, 2013 at 08:09:31PM +, Stephen Boyd wrote:
On 03/28/13 08:22, Mark Rutland wrote:
This works on my A9x4 coretile, bringing CPUs up and down via
/sys/devices/system/cpu/*/online, so:
Tested-by: Mark Rutland mark.rutl...@arm.com
Thanks. I still need to resolve patch #1
Hi,
I attempted to cross-build v3.9-rc3's perf tool for an arm system today, and
got the following out of the build system:
CHK libnewt
Makefile:655: newt not found, disables TUI support. Please install newt-devel
or libnewt-dev
[...]
builtin-report.c: In function ‘__cmd_report’:
On Wed, Mar 20, 2013 at 01:23:22PM +, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 20, 2013 at 12:11:11PM +, Mark Rutland escreveu:
I attempted to cross-build v3.9-rc3's perf tool for an arm system today, and
got the following out of the build system:
CHK libnewt
Makefile:655
Hi Rob,
(adding Marc to Cc as he may have comments).
On Wed, Mar 20, 2013 at 10:34:35PM +, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
This converts arm and arm64 to use CLKSRC_OF DT based initialization for
the arch timer. A new function arch_timer_arch_init is added
On Wed, Mar 20, 2013 at 10:54:01PM +, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
Add an empty version of of_device_is_available.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
---
include/linux/of.h |5 +
1 file changed, 5 insertions(+)
diff --git
.
On Wed, Mar 13, 2013 at 06:17:47PM +, Stephen Boyd wrote:
From: Mark Rutland mark.rutl...@arm.com
Several architectures have a dummy timer driver tightly coupled with
their broadcast code to support machines without cpu-local timers (or
where there is a lack of driver support).
Since
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 SMP's been brought
up
On Mon, Mar 25, 2013 at 04:49:18PM +, Stephen Boyd wrote:
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
On Tue, Mar 26, 2013 at 02:14:53AM +, Stephen Boyd wrote:
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
On Mon, Mar 25, 2013 at 08:47:42PM +, Thomas Gleixner wrote:
On Mon, 25 Mar 2013, Mark Rutland wrote:
Thomas, do you have an idea of if/when tip/timers/urgent will hit mainline?
Thanks for the reminder. I just sent a pull request Linuswards.
Cheers!
Mark.
--
To unsubscribe from
This works on my A9x4 coretile, bringing CPUs up and down via
/sys/devices/system/cpu/*/online, so:
Tested-by: Mark Rutland mark.rutl...@arm.com
Otherwise, is there any reason we couldn't now use the twd driver on a UP
system? Or would the overhead of handling frequency change make
On Mon, Mar 04, 2013 at 11:50:22PM +, Stephen Boyd wrote:
On 02/25/13 05:40, Mark Rutland wrote:
I've had a quick go at writing a generic timer driver. I've not had a
chance to
test it, and there are a couple of things that are up for discussion (e.g.
what
should the rating
On Tue, Nov 27, 2012 at 01:41:16PM +, Arnaldo Carvalho de Melo wrote:
Em Tue, Nov 27, 2012 at 12:16:31PM +, Mark Rutland escreveu:
The UAPI changes broke the perf tool, and as of 3.7-rc7, it
still won't build for arm:
util/../../../arch/arm/include/asm/unistd.h:16:29: fatal
Hi,
[...]
diff --git a/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
b/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
new file mode 100644
index 000..6717ab1
--- /dev/null
+++ b/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
@@ -0,0 +1,30 @@
+*
Hello,
On Thu, Feb 07, 2013 at 04:02:41PM +, Roger Quadros wrote:
The PHY clock, clock rate, VCC regulator and RESET regulator
can now be provided via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
On Thu, Feb 07, 2013 at 04:02:47PM +, Roger Quadros wrote:
Allows the OHCI controller found in OMAP3 and later chips to
be specified via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
On Thu, Feb 07, 2013 at 04:02:48PM +, Roger Quadros wrote:
Allows the OMAP EHCI controller to be specified via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
.../devicetree/bindings/usb/omap-ehci.txt | 34
On Thu, Feb 07, 2013 at 04:02:49PM +, Roger Quadros wrote:
Allows the OMAP HS USB host controller to be specified
via device tree.
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
.../devicetree/bindings/mfd/omap-usb-host.txt | 80 ++
Hi Roger,
On Mon, Feb 11, 2013 at 03:14:26PM +, Roger Quadros wrote:
On 02/11/2013 01:40 PM, Mark Rutland wrote:
Hello,
On Thu, Feb 07, 2013 at 04:02:41PM +, Roger Quadros wrote:
The PHY clock, clock rate, VCC regulator and RESET regulator
can now be provided via device tree
+Required properties:
+
+- compatible: should be ti,ohci-omap3
+- reg: should contain one register range i.e. start and length
+- interrupt-parent: phandle to the interrupt controller
I'm not sure that needs to be documented as a required property. It's a
standard property, and if
Hello,
I have a few comments on the devicetree binding and the way it's parsed.
+static const struct of_device_id dbx500_mailbox_match[] = {
+ { .compatible = stericsson,db8500-mailbox,
+ .data = (void *)db8500_mboxes,
+ },
+ { .compatible =
On Tue, Feb 12, 2013 at 08:01:05PM +, Loic PALLARDY wrote:
Hi Mark,
Thanks for your comments.
On 02/12/2013 11:39 AM, Mark Rutland wrote:
Hello,
I have a few comments on the devicetree binding and the way it's parsed.
+static const struct of_device_id dbx500_mailbox_match
Hi,
On Mon, Feb 04, 2013 at 01:28:14PM +, Manjunathappa, Prakash wrote:
Hi Mark,
On Thu, Jan 31, 2013 at 16:53:03, Mark Rutland wrote:
Hello,
I have a few comments on the devicetree binding and the way it's parsed.
Thanks for review.
On Thu, Jan 31, 2013 at 10:33:06AM +
Hi Stephen,
Sorry about this; I'm to blame for the bug.
On Wed, Feb 06, 2013 at 08:51:43PM +, Stephen Warren wrote:
On 01/14/2013 10:05 AM, Mark Rutland wrote:
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer
Hello,
I have a couple of comments on the dt bindings and the way it's parsed.
On Thu, Feb 07, 2013 at 07:57:04AM +, Manjunathappa, Prakash wrote:
Adds device tree support for davinci_mmc. Also add binding documentation.
Tested in non-dma PIO mode and without GPIO card_detect/write_protect
[...]
The intent of 12ad100046: clockevents: Add generic timer broadcast
function
was to setup the broadcast function both for non-functional/dummy timers and
those that stop in low-power states (CLOCK_EVT_FEAT_C3STOP). I missed the
CLOCK_EVT_FEAT_C3STOP case.
I am not sure this
[...]
The intent of 12ad100046: clockevents: Add generic timer broadcast
function
was to setup the broadcast function both for non-functional/dummy timers and
those that stop in low-power states (CLOCK_EVT_FEAT_C3STOP). I missed the
CLOCK_EVT_FEAT_C3STOP case.
I believe the patch
Hello,
I have a couple of minor comments.
On Thu, Feb 07, 2013 at 02:11:37PM +, Anil Kumar wrote:
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG
Hello,
I have a few comments on the devicetree binding and the way it's parsed.
On Thu, Jan 31, 2013 at 10:33:06AM +, Manjunathappa, Prakash wrote:
Adds device tree support for davinci_mmc. Also add
binding documentation.
Tested with non-dma PIO mode and without GPIO
On Fri, Mar 01, 2013 at 08:36:24AM +, Uwe Kleine-König wrote:
Hello,
On Fri, Mar 01, 2013 at 01:25:52AM -0300, Vinicius Tinti wrote:
Remove extra semicolon in perf_event.c if statement.
The commit log sounds like a style fix, but your patch introduces a
semantical change. I suspect
On Fri, Jan 25, 2013 at 10:23:57AM +, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control
[...]
+OMAP CONTROL USB
+
+Required properties:
+ - compatible: Should be ti,omap-control-usb
+ - reg : Address and length of the register set for the device. It
contains
+ the address of control_dev_conf and otghs_control or
phy_power_usb
Could you not use '-'
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon omap4 or omap5.
+ - reg-names: The names of the register addresses corresponding to
the registers
+ filled in reg
On Fri, Jan 25, 2013 at 04:23:46PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 04:14:02PM +, Mark Rutland wrote:
On Fri, Jan 25, 2013 at 02:59:28PM +, Felipe Balbi wrote:
Hi,
On Fri, Jan 25, 2013 at 12:29:43PM +, Mark Rutland wrote:
+ depending upon
+struct usb_phy *devm_usb_get_phy_by_phandle(struct device *dev,
+ const char *phandle, u8 index)
+{
+ struct usb_phy *phy = NULL, **ptr;
+ unsigned long flags;
+ struct device_node *node;
+
+ if (!dev-of_node) {
+ dev_dbg(dev, device does not have a
: Add generic timer broadcast function (2013-01-14 16:55:01 +)
Mark Rutland (2):
clockevents: Add generic timer broadcast receiver
clockevents: Add generic timer broadcast function
include/linux/clockchips.h | 9
generic timer broadcast function (2013-01-18 17:07:36 +)
Mark Rutland (2):
clockevents: Add generic timer broadcast receiver
clockevents: Add generic timer broadcast function
include/linux/clockchips.h | 9
*’ but
argument is of type ‘stack_t’
make[1]: *** [arch/arm64/kernel/signal.o] Error 1
make: *** [arch/arm64/kernel] Error 2
This patch fixes up the call to restore_altstack to pass the correct
type.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
arch/arm64/kernel/signal.c | 2 +-
1 file changed, 1
Hi,
As with Stephen Warren's fix [1], this looks right to me. Stephen's has the
added benefit of keeping the includes ordered.
For either version:
Acked-By: Mark Rutland mark.rutl...@arm.com
Thanks,
Mark.
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149579.html
Hi Stephen,
One thing that struck me when I was fiddling with the broadcast mechanism was
that it should be possible to have a generic dummy timer implementation. As
long as the architecture calls notifiers at the appropriate times, it should
look like any other timer driver (apart from not
On Fri, Feb 22, 2013 at 04:25:00PM +, Paul Mundt wrote:
On Fri, Feb 22, 2013 at 11:15:45AM +, Mark Rutland wrote:
One thing that struck me when I was fiddling with the broadcast mechanism
was
that it should be possible to have a generic dummy timer implementation. As
long
On Sun, Feb 24, 2013 at 02:37:15AM +, Stephen Boyd wrote:
On 2/22/2013 3:15 AM, Mark Rutland wrote:
Hi Stephen,
One thing that struck me when I was fiddling with the broadcast mechanism
was
that it should be possible to have a generic dummy timer implementation. As
long
/unistd.h.
This patch copies 77626081: perf tools: Fix build on sparc. in simply
changing the path to use arch/arm/include/uapi/asm/unistd.h directly for
all of these cases.
I've tested this on arm, but I don't have the necessary toolchains to
check the other cases.
Signed-off-by: Mark Rutland
drivers to be decoupled from a particular
architecture will retaining support for timer tick broadcasts. These
mechanisms are wired up for the arm port, and have been boot-tested on a
pandaboard.
Thanks,
Mark.
Mark Rutland (5):
ARM: remove useless guard in smp.c
clockevents: Add generic timer
guard.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
arch/arm/kernel/smp.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
index fbc8b26..21954bc 100644
--- a/arch/arm/kernel/smp.c
+++ b/arch/arm/kernel/smp.c
.
This patch adds a standard path for the receipt of timer broadcasts, so
drivers and/or architecture backends need not manage redundant lists of
timers for the purpose of routing broadcast timer ticks.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
include/linux/clockchips.h |4
, which already maintains its own list
of timers.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
arch/arm/kernel/smp.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
index 21954bc..59bf6d5 100644
--- a/arch/arm/kernel
) architecture-specific function for timer
tick broadcast, allowing drivers which may require broadcast
functionality to be shared across multiple architectures.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
include/linux/clockchips.h |5 +
kernel/time/Kconfig |4
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer tick broadcast
mechanism.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
arch/arm/Kconfig |1 +
arch/arm/kernel/smp.c |3 +--
2 files changed, 2
On Tue, Dec 18, 2012 at 02:30:23PM +, Roland Stigge wrote:
Hi Mark,
On 12/17/2012 04:51 PM, Mark Rutland wrote:
+static int __devinit gpioblock_of_probe(struct platform_device *pdev)
+{
+ struct device_node *block;
+ unsigned *gpios;
+ int ngpio;
+ int ret;
+ struct
On Tue, Dec 18, 2012 at 06:47:09PM +, Stephen Boyd wrote:
On 12/18/12 04:06, Mark Rutland wrote:
Currently we only provide an implementation of smp_timer_broadcast in
smp.c if GENERIC_CLOCKEVENTS_BROADCAST is selected. As
smp_timer_broadcast is only used in smp.c, smp.c depends on SMP
On Tue, Dec 18, 2012 at 10:17:11PM +, Stephen Boyd wrote:
On 12/18/12 04:06, Mark Rutland wrote:
diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index f113755..c2dd022 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -125,6
On Tue, Dec 18, 2012 at 10:17:13PM +, Stephen Boyd wrote:
Minor nit
On 12/18/12 04:06, Mark Rutland wrote:
diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index c2dd022..ec22a80 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
On Fri, Dec 21, 2012 at 10:02:18AM +, Santosh Shilimkar wrote:
On Tuesday 18 December 2012 05:36 PM, Mark Rutland wrote:
Currently the broadcast mechanism used for timers is abstracted by a
function pointer on struct clock_event_device. As the fundamental
mechanism for broadcast
On Fri, Dec 21, 2012 at 10:02:01AM +, Santosh Shilimkar wrote:
On Tuesday 18 December 2012 05:36 PM, Mark Rutland wrote:
Currently we only provide an implementation of smp_timer_broadcast in
smp.c if GENERIC_CLOCKEVENTS_BROADCAST is selected. As
smp_timer_broadcast is only used in smp.c
On Fri, Dec 21, 2012 at 10:08:02AM +, Santosh Shilimkar wrote:
Mark,
On Tuesday 18 December 2012 05:36 PM, Mark Rutland wrote:
In some SMP systems, cpu-local timers may stop delivering interrupts
when in low power states, or not all CPUs may have local timers. To
support
Hi,
I have a few comments on the parsing code.
On Fri, Dec 14, 2012 at 02:26:24PM +, Roland Stigge wrote:
This patch adds device tree support to the block GPIO API.
Signed-off-by: Roland Stigge sti...@antcom.de
---
Documentation/devicetree/bindings/gpio/gpio-block.txt | 36 +++
On Fri, Nov 16, 2012 at 06:38:21AM +, Alexandre Courbot wrote:
Some device drivers (e.g. panel or backlights) need to follow precise
sequences for powering on and off, involving GPIOs, regulators, PWMs
with a precise powering order and delays to respect between steps.
These sequences are
On Tue, Sep 25, 2012 at 08:08:47PM +0100, Rohit Vaswani wrote:
Any comments ?
I have a few questions about the irq side of things.
diff --git a/Documentation/devicetree/bindings/arm/arch_timer.txt
b/Documentation/devicetree/bindings/arm/arch_timer.txt
index 52478c8..8e01328 100644
---
On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
On Wed, 9 Jan 2013, Mark Rutland wrote:
+#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
+extern int tick_receive_broadcast(void);
+#else
+static inline int tick_receive_broadcast(void)
+{
+ return 0;
+}
What's
On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote:
On Wed, 9 Jan 2013, Mark Rutland wrote:
+#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
+extern int
On Mon, Jan 14, 2013 at 02:17:26PM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 11:50:55AM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 11:06:31AM +, Thomas Gleixner wrote
function which allows drivers to be decoupled from a particular
architecture will retaining support for timer tick broadcasts. These
mechanisms are wired up for the arm port, and have been boot-tested on a
pandaboard.
Thanks,
Mark.
Mark Rutland (4):
clockevents: Add generic timer broadcast receiver
) architecture-specific function for timer
tick broadcast, allowing drivers which may require broadcast
functionality to be shared across multiple architectures.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar
, which already maintains its own list
of timers.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/smp.c | 10 +++---
1
.
This patch adds a standard path for the receipt of timer broadcasts, so
drivers and/or architecture backends need not manage redundant lists of
timers for the purpose of routing broadcast timer ticks.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer tick broadcast
mechanism.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar
On Tue, Jan 15, 2013 at 11:24:53AM +, Thomas Gleixner wrote:
On Mon, 14 Jan 2013, Mark Rutland wrote:
On Mon, Jan 14, 2013 at 02:17:26PM +, Thomas Gleixner wrote:
I thought this previously also [1], but I couldn't find any path such
that a
tick_cpu_device would have
, and have been boot-tested on a
pandaboard.
Thanks,
Mark.
Mark Rutland (4):
clockevents: Add generic timer broadcast receiver
arm: Use generic timer broadcast receiver
clockevents: Add generic timer broadcast function
arm: Add generic timer broadcast support
arch/arm/Kconfig
.
This patch adds a standard path for the receipt of timer broadcasts, so
drivers and/or architecture backends need not manage redundant lists of
timers for the purpose of routing broadcast timer ticks.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim
, which already maintains its own list
of timers.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/kernel/smp.c |8 +---
1 files changed, 1 insertions(+), 7 deletions
) architecture-specific function for timer
tick broadcast, allowing drivers which may require broadcast
functionality to be shared across multiple architectures.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer tick broadcast
mechanism.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
Reviewed-by: Santosh Shilimkar santosh.shilim...@ti.com
Tested-by: Santosh Shilimkar
On Wed, Jan 09, 2013 at 08:46:18PM +, Stephen Boyd wrote:
On 01/09/13 06:46, Mark Rutland wrote:
This is an updated version of the series I posted back in December:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137929.html
Changes since v1:
* Drop removal
On Fri, Aug 02, 2013 at 12:48:07PM +0100, Gururaja Hebbar wrote:
On 8/2/2013 4:50 PM, Mark Rutland wrote:
On Fri, Aug 02, 2013 at 12:07:36PM +0100, Gururaja Hebbar wrote:
On 8/1/2013 10:35 PM, Mark Rutland wrote:
On Tue, Jul 30, 2013 at 05:21:14PM +0100, Sekhar Nori wrote:
On 7/30/2013 8
On Fri, Aug 02, 2013 at 02:28:45PM +0100, Jonas Jensen wrote:
Add dmaengine driver for MOXA ART SoCs.
Signed-off-by: Jonas Jensen jonas.jen...@gmail.com
---
Notes:
Preemptively submitting a new version that has the previously
mentioned two cell xlate.
Changes since v5:
On Sun, Aug 04, 2013 at 02:09:04AM +0100, Jason Cooper wrote:
DT Maintainers,
It's been a week with no comment. Shall I assume it's ok to apply
this?
Apologies for the delay, still catching up on binding review.
I'm not entirely sure on this. The property described is still true for
the
On Fri, Aug 02, 2013 at 05:39:49PM +0100, Guenter Roeck wrote:
On 08/02/2013 04:41 AM, Mark Rutland wrote:
On Mon, Jul 29, 2013 at 01:33:48PM +0100, Jonas Jensen wrote:
Add watchdog driver for MOXA ART SoCs.
[ ... ]
+
+ err = watchdog_register_device(moxart_wdt-dev);
+ if (unlikely
On Mon, Aug 05, 2013 at 03:37:37PM +0100, Jonas Jensen wrote:
The MOXA ART SoC has a DMA controller capable of offloading expensive
memory operations, such as large copies. This patch adds support for
the controller including four channels. Two of these are used to
handle MMC copy on the
On Mon, Aug 05, 2013 at 10:56:00PM +0100, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
pinctrl bindings can benefit from generic property names that define
which pins a pin configuration node affects, and which mux function
to select onto those pins. Document new properties
Hi Vince,
Thanks for the report.
On Mon, Aug 05, 2013 at 10:17:37PM +0100, Vince Weaver wrote:
On Mon, 5 Aug 2013, Vince Weaver wrote:
My perf_fuzzer quickly triggers this oops on my ARM Cortex A9 pandaboard
running Linux 3.11-rc4.
Below is the oops, I've attached a simple C test
On Tue, Aug 06, 2013 at 12:59:21PM +0100, Will Deacon wrote:
On Tue, Aug 06, 2013 at 12:19:32PM +0100, Mark Rutland wrote:
On Mon, Aug 05, 2013 at 10:17:37PM +0100, Vince Weaver wrote:
It looks like in validate_event() we do
struct arm_pmu *armpmu = to_arm_pmu(event-pmu
On Tue, Aug 06, 2013 at 12:53:10PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-ssusb.txt | 49 +++
drivers/usb/phy/Kconfig| 11 +
On Tue, Aug 06, 2013 at 12:53:11PM +0100, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
What does the glue layer do? Is it an actual piece of hardware, or
just some platform-specific code?
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
On Wed, Aug 07, 2013 at 02:00:27PM +0100, Will Deacon wrote:
On Tue, Aug 06, 2013 at 02:08:15PM +0100, Mark Rutland wrote:
On Tue, Aug 06, 2013 at 12:59:21PM +0100, Will Deacon wrote:
But we already check `event-pmu != leader_pmu' in validate_event, so we
shouldn't get anywhere nearer
that
the #interrupt-cells property should be 2.
I take it there are no device nodes for which any of these nodes are an
interrupt parent (which would need to be updated)?
If so:
Acked-by: Mark Rutland mark.rutl...@arm.com
Thanks,
Mark.
Signed-off-by: Lars Poeschel poesc...@lemonage.de
On Tue, Aug 06, 2013 at 01:38:31PM +0100, Jonas Jensen wrote:
The MOXA ART SoC has a DMA controller capable of offloading expensive
memory operations, such as large copies. This patch adds support for
the controller including four channels. Two of these are used to
handle MMC copy on the
On Tue, Aug 06, 2013 at 07:00:17PM +0100, Julius Werner wrote:
This patch simplifies the way the phy-samsung-usb code finds the correct
power management register to enable PHY clock gating. Previously, the
code would calculate the register address from a device tree supplied
base address and
On Wed, Aug 07, 2013 at 11:29:52AM +0100, Laxman Dewangan wrote:
Palmas series device like TPS65913, TPS80036 supports the backup battery
for powering the RTC when no other energy source is available.
The backup battery is optional, connected to the VBACKUP pin, and can be
nonrechargeable or
Hi Olof,
[Adding the other new dt bindings maintainers to Cc]
On Thu, Jul 25, 2013 at 05:09:19PM +0100, Olof Johansson wrote:
[I'm adding LKML and ksummit-discuss to this thread, since the ACPI/DT
discussions have been covered there and this overlaps some with that]
On Thu, Jul 25, 2013 at
On Thu, Jul 25, 2013 at 07:05:48PM +0100, Stephen Warren wrote:
On 07/25/2013 10:57 AM, Mark Rutland wrote:
On Thu, Jul 25, 2013 at 05:09:19PM +0100, Olof Johansson wrote:
...
So, there really seems to be a need for a layered approach, one in
which a binding graduates from being tentative
On Fri, Jul 26, 2013 at 04:40:15PM +0100, Stephen Warren wrote:
(CC'ing the new DT binding maintainers and mailing list on this reply,
hence quoting the whole of the DT binding)
Thanks Stephen.
On 07/25/2013 06:29 AM, Laxman Dewangan wrote:
Palmas series device like TPS65913, TPS80036
On Fri, Jul 26, 2013 at 04:11:57PM +0100, Mark Langsdorf wrote:
Some board designs do not drive the SATA transmit lines within the
specification. The ECME can provide override settings, on a per board
basis, to bring the transmit lines within spec. Read those settings
from the DTB and program
On Fri, Jul 26, 2013 at 04:11:58PM +0100, Mark Langsdorf wrote:
Some SGPIO PICs don't follow the standard very well and expect a
certain number of clock cycles or port frames in each SGPIO pattern.
Add two optional parameters in the DTB that can provide the number of
extra clock cycles to be
On Tue, Jul 23, 2013 at 11:25:06PM +0100, Maxime Ripard wrote:
The Allwinner A31 has a sligthly different watchdog that requires a
different restart code.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
arch/arm/mach-sunxi/sunxi.c | 37
1 - 100 of 8690 matches
Mail list logo
