Re: [RFC 2/5] ARM: dts: Add Cross Trigger Interface binding
From: Will Deacon <hidden>
Date: 2012-12-13 17:41:40
Also in:
linux-arm-kernel, linux-omap
On Wed, Dec 12, 2012 at 09:43:05PM +0000, Jon Hunter wrote:
quoted hunk ↗ jump to hunk
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 <redacted> --- Documentation/devicetree/bindings/arm/cti.txt | 32 +++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/cti.txtdiff --git a/Documentation/devicetree/bindings/arm/cti.txt b/Documentation/devicetree/bindings/arm/cti.txt new file mode 100644 index 0000000..4a0e2d3 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/cti.txt@@ -0,0 +1,32 @@ +* ARM Cross Trigger Interface (CTI) + +The ARM Cross Trigger Interface provides a way to route events between +processor modules. For example, debug events from one processor can be +broadcasted to other processors. The events that can be routed between +processors are specific to the device. + +Required properties: + +- compatible: Should be "arm,primecell". +- interrupts: Interrupt associated with CTI module. +- reg: Contains timer register address range (base + address and length). +- arm,cti-name: A unique name for the CTI module, that will be + used when requesting the CTI module instance. + + +Optional properties: + +- arm-primecell-periphid: Primecell peripheral ID associated with CTI + module.
For multi-cluster systems, I wouldn't be surprised to see multiple CTI instances, each with different CPU affinities. Can we include an affinity property following Mark's proposed binding? http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137290.html Will