mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tip-bot for Eric Anholt <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, swarren@wwwdotorg.org, hpa@zytor.com,
	eric@anholt.net, jason@lakedaemon.net,
	linux-kernel@vger.kernel.org, lee@kernel.org, tglx@linutronix.de
Subject: [tip:irq/core] irqchip: Add documentation for the bcm2836 interrupt controller
Date: Thu, 20 Aug 2015 13:43:14 -0700	[thread overview]
Message-ID: <tip-815e7a31c3f7929f371da9c7e9ee91cfd52ef453@git.kernel.org> (raw)
In-Reply-To: <1438902033-31477-4-git-send-email-eric@anholt.net>

Commit-ID:  815e7a31c3f7929f371da9c7e9ee91cfd52ef453
Gitweb:     http://git.kernel.org/tip/815e7a31c3f7929f371da9c7e9ee91cfd52ef453
Author:     Eric Anholt <eric@anholt.net>
AuthorDate: Thu, 6 Aug 2015 16:00:32 -0700
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 20 Aug 2015 22:38:42 +0200

irqchip: Add documentation for the bcm2836 interrupt controller

This is a new per-cpu root interrupt controller on the Raspberry Pi 2,
which will chain to the bcm2835 interrupt controller for peripheral
interrupts.

Signed-off-by: Eric Anholt <eric@anholt.net>
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-rpi-kernel@lists.infradead.org
Cc: Lee Jones <lee@kernel.org>
Cc: Jason Cooper <jason@lakedaemon.net>
Cc: linux-arm-kernel@lists.infradead.org
Link: http://lkml.kernel.org/r/1438902033-31477-4-git-send-email-eric@anholt.net
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 .../interrupt-controller/brcm,bcm2836-l1-intc.txt  | 37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt
new file mode 100644
index 0000000..f320dcd
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt
@@ -0,0 +1,37 @@
+BCM2836 per-CPU interrupt controller
+
+The BCM2836 has a per-cpu interrupt controller for the timer, PMU
+events, and SMP IPIs.  One of the CPUs may receive interrupts for the
+peripheral (GPU) events, which chain to the BCM2835-style interrupt
+controller.
+
+Required properties:
+
+- compatible:	 	Should be "brcm,bcm2836-l1-intc"
+- reg:			Specifies base physical address and size of the
+			  registers
+- interrupt-controller:	Identifies the node as an interrupt controller
+- #interrupt-cells:	Specifies the number of cells needed to encode an
+			  interrupt source. The value shall be 1
+
+Please refer to interrupts.txt in this directory for details of the common
+Interrupt Controllers bindings used by client devices.
+
+The interrupt sources are as follows:
+
+0: CNTPSIRQ
+1: CNTPNSIRQ
+2: CNTHPIRQ
+3: CNTVIRQ
+8: GPU_FAST
+9: PMU_FAST
+
+Example:
+
+local_intc: local_intc {
+	compatible = "brcm,bcm2836-l1-intc";
+	reg = <0x40000000 0x100>;
+	interrupt-controller;
+	#interrupt-cells = <1>;
+	interrupt-parent = <&local_intc>;
+};

  reply	other threads:[~2015-08-20 20:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 23:00 Raspberry Pi 2 interrupt controller support (v4) Eric Anholt
2015-08-06 23:00 ` [PATCH v4 1/4] irqchip: bcm2835: Refactor handle_IRQ() calls out of MAKE_HWIRQ Eric Anholt
2015-08-20 20:42   ` [tip:irq/core] irqchip/bcm2835: " tip-bot for Eric Anholt
2015-08-06 23:00 ` [PATCH v4 2/4] irqchip: bcm2835: Add support for being used as a second level controller Eric Anholt
2015-08-20 20:42   ` [tip:irq/core] irqchip/bcm2835: " tip-bot for Eric Anholt
2015-08-06 23:00 ` [PATCH v4 3/4] irqchip: Add documentation for the bcm2836 interrupt controller Eric Anholt
2015-08-20 20:43   ` tip-bot for Eric Anholt [this message]
2015-08-06 23:00 ` [PATCH v4 4/4] irqchip: Add bcm2836 interrupt controller for Raspberry Pi 2 Eric Anholt
2015-08-20 20:43   ` [tip:irq/core] " tip-bot for Eric Anholt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tip-815e7a31c3f7929f371da9c7e9ee91cfd52ef453@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=eric@anholt.net \
    --cc=hpa@zytor.com \
    --cc=jason@lakedaemon.net \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome