From: Joachim Eastwood <manabian@gmail.com>
To: marc.zyngier@arm.com, jason@lakedaemon.net, tglx@linutronix.de,
robh+dt@kernel.org
Cc: Joachim Eastwood <manabian@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] devicetree: document NXP LPC1850 PINT irq controller binding
Date: Sat, 2 Apr 2016 18:35:24 +0200 [thread overview]
Message-ID: <1459614924-32670-3-git-send-email-manabian@gmail.com> (raw)
In-Reply-To: <1459614924-32670-1-git-send-email-manabian@gmail.com>
Add binding documentation for NXP LPC1850 GPIO Pin Interrupt (PINT)
controller.
Signed-off-by: Joachim Eastwood <manabian@gmail.com>
---
.../interrupt-controller/nxp,lpc1850-gpio-pint.txt | 26 ++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
diff --git a/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt b/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
new file mode 100644
index 0000000..0d59d31
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/nxp,lpc1850-gpio-pint.txt
@@ -0,0 +1,26 @@
+NXP LPC18xx/43xx GPIO Pin Interrupt (PINT) controller
+
+Required properties:
+
+- compatible : should be "nxp,lpc1850-gpio-pint".
+- 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 2.
+- interrupts : Must contain the interrupt numbers from the parent controller.
+ This defines the mapping between the controllers where the first
+ interrupt is mapped to pint hwirq 0 and so on. Which interrupts
+ that are connected to where and the number of is device specific.
+ For lpc1850 the mapping is 32 33 34 35 36 37 38 39 (8 in total).
+- clocks: Must contain a reference to the functional clock.
+
+Example:
+
+pint: interrupt-controller@40087000 {
+ compatible = "nxp,lpc1850-gpio-pint";
+ reg = <0x40087000 0x1000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ interrupts = <32 33 34 35 36 37 38 39>;
+ clocks = <&ccu1 CLK_CPU_GPIO>;
+};
--
2.8.0
next prev parent reply other threads:[~2016-04-02 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 16:35 [PATCH v2 0/2] PINT irqchip driver for NXP LPC18xx family Joachim Eastwood
2016-04-02 16:35 ` [PATCH v2 1/2] irqchip: add lpc18xx gpio pin interrupt driver Joachim Eastwood
[not found] ` <1459614924-32670-2-git-send-email-manabian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-11 15:15 ` Marc Zyngier
[not found] ` <570BBF7F.2040001-5wv7dgnIgG8@public.gmane.org>
2016-04-11 15:40 ` Joachim Eastwood
2016-04-02 16:35 ` Joachim Eastwood [this message]
2016-04-07 17:57 ` [PATCH v2 2/2] devicetree: document NXP LPC1850 PINT irq controller binding Rob Herring
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=1459614924-32670-3-git-send-email-manabian@gmail.com \
--to=manabian@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).