From: hkallweit1@gmail.com (Heiner Kallweit)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH RfC v4 3/6] dt-bindings: add Amlogic Meson GPIO interrupt-controller DT binding documentation
Date: Sun, 28 May 2017 21:11:20 +0200 [thread overview]
Message-ID: <4f082b42-40dd-6e7d-61f5-d3aad1fc19de@gmail.com> (raw)
In-Reply-To: <49ab677f-3165-d6f5-75f5-a963879e8ecf@gmail.com>
Add dt binding documentation for Amlogic meson GPIO interrupt controller.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
.../amlogic,meson-gpio-intc.txt | 26 ++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
diff --git a/Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt b/Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
new file mode 100644
index 00000000..2f20d212
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
@@ -0,0 +1,26 @@
+Amlogic meson GPIO interrupt controller
+
+Meson SoCs contains an interrupt controller which is able watch the SoC pads
+and generate an interrupt on edges or level. The controller is essentially a
+256 pads to 8 GIC interrupt multiplexer, with a filter block to select edge
+or level and polarity. The actual number of interrupt exposed depends on the
+SoC.
+
+Required properties:
+
+- compatible : should be "amlogic,meson-gpio-intc".
+- reg : Specifies base physical address and size of the registers.
+- interrupt-controller : Identifies the node as an interrupt controller.
+- #interrupt-cells : should be 2.
+- parent-interrupts : list of GIC interrupts which can be used with the
+ GPIO IRQ multiplexer
+
+Example:
+
+gpio_intc: interrupt-controller at 9880 {
+ compatible = "amlogic,meson-gpio-intc";
+ reg = <0x0 0x09880 0x0 0x10>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ parent-interrupts = <64 65 66 67 68 69 70 71>;
+};
--
2.13.0
next prev parent reply other threads:[~2017-05-28 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 18:40 [PATCH RfC v4 0/6] pintrl: meson: add support for GPIO IRQs Heiner Kallweit
2017-05-28 19:10 ` [PATCH RfC v4 1/6] pinctrl: meson: add interrupts to pinctrl data Heiner Kallweit
2017-05-29 8:43 ` Neil Armstrong
2017-05-28 19:11 ` [PATCH RfC v4 2/6] irqchip: add Amlogic Meson GPIO irqchip driver Heiner Kallweit
2017-05-29 7:57 ` Linus Walleij
2017-05-29 8:38 ` Neil Armstrong
2017-05-28 19:11 ` Heiner Kallweit [this message]
2017-05-29 8:44 ` [PATCH RfC v4 3/6] dt-bindings: add Amlogic Meson GPIO interrupt-controller DT binding documentation Neil Armstrong
2017-05-28 19:11 ` [PATCH RfC v4 4/6] ARM(64): dts: meson: add GPIO interrupt-controller support Heiner Kallweit
2017-05-29 8:49 ` Neil Armstrong
2017-05-29 20:01 ` Heiner Kallweit
2017-05-30 8:41 ` Neil Armstrong
2017-05-28 19:12 ` [PATCH RfC v4 5/6] pinctrl: meson: add support for GPIO interrupts Heiner Kallweit
2017-05-29 8:43 ` Neil Armstrong
2017-05-29 20:12 ` Heiner Kallweit
2017-05-30 7:46 ` Jerome Brunet
2017-05-30 18:51 ` Heiner Kallweit
2017-05-28 19:13 ` [PATCH RfC v4 6/6] ARM(64): dts: meson: mark gpio controllers as interrupt controllers and update binding documentation Heiner Kallweit
2017-05-29 8:50 ` Neil Armstrong
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=4f082b42-40dd-6e7d-61f5-d3aad1fc19de@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linus-amlogic@lists.infradead.org \
/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).