From: hkallweit1@gmail.com (Heiner Kallweit)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH RfC v3 2/7] pinctrl: meson: document GPIO IRQ driver DT binding
Date: Wed, 17 May 2017 22:16:35 +0200 [thread overview]
Message-ID: <7c09969b-ac04-cfa4-7459-7ad25b7c5cbf@gmail.com> (raw)
In-Reply-To: <16950080-b19d-e25c-fb48-bc79cfe4acc0@gmail.com>
Document the DT binding for GPIO IRQ support on Amlogic Meson SoC's.
This documentation is intentionally not placed under
interrupt-controllers as GPIO IRQ support on these SoC's acts more
like an interrupt multiplexer.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
v2:
- remove syscon
v3:
- no changes
---
.../bindings/gpio/amlogic,meson-gpio-interrupt.txt | 30 ++++++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/amlogic,meson-gpio-interrupt.txt
diff --git a/Documentation/devicetree/bindings/gpio/amlogic,meson-gpio-interrupt.txt b/Documentation/devicetree/bindings/gpio/amlogic,meson-gpio-interrupt.txt
new file mode 100644
index 00000000..ba7d3015
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/amlogic,meson-gpio-interrupt.txt
@@ -0,0 +1,30 @@
+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. We don't expose all 256 mux inputs because the
+documentation shows that upper part is not mapped to any pad. The actual number
+of interrupt exposed depends on the SoC.
+
+Required properties:
+
+- compatible : should be "amlogic,meson-gpio-interrupt".
+- reg : Specifies base physical address and size of the registers.
+- interrupts : list of GIC interrupts which can be used with the
+ GPIO IRQ multiplexer
+
+Example:
+
+gpio_irq at 9880 {
+ compatible = "amlogic,meson-gpio-interrupt";
+ reg = <0x0 0x09880 0x0 0x10>;
+ interrupts = <GIC_SPI 64 IRQ_TYPE_NONE>,
+ <GIC_SPI 65 IRQ_TYPE_NONE>,
+ <GIC_SPI 66 IRQ_TYPE_NONE>,
+ <GIC_SPI 67 IRQ_TYPE_NONE>,
+ <GIC_SPI 68 IRQ_TYPE_NONE>,
+ <GIC_SPI 69 IRQ_TYPE_NONE>,
+ <GIC_SPI 70 IRQ_TYPE_NONE>,
+ <GIC_SPI 71 IRQ_TYPE_NONE>;
+ };
--
2.13.0
next prev parent reply other threads:[~2017-05-17 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 20:02 [PATCH RfC v3 0/7] pintrl: meson: add support for GPIO IRQs Heiner Kallweit
2017-05-17 20:16 ` [PATCH RfC v3 1/7] pinctrl: meson: add interrupts to pinctrl data Heiner Kallweit
2017-05-17 20:16 ` Heiner Kallweit [this message]
2017-05-23 0:56 ` [PATCH RfC v3 2/7] pinctrl: meson: document GPIO IRQ driver DT binding Rob Herring
2017-05-17 20:16 ` [PATCH RfC v3 3/7] pinctrl: meson: add DT node for GPIO IRQ on Meson GX Heiner Kallweit
2017-05-17 20:16 ` [PATCH RfC v3 4/7] pinctrl: meson: add DT node for GPIO IRQ on Meson 8 / 8b Heiner Kallweit
2017-05-17 20:16 ` [PATCH RfC v3 5/7] pinctrl: meson: improve meson_get_bank and export it Heiner Kallweit
2017-05-17 20:17 ` [PATCH RfC v3 6/7] pinctrl: meson: add support for GPIO interrupts Heiner Kallweit
2017-05-23 9:01 ` Jerome Brunet
2017-05-17 20:17 ` [PATCH RfC v3 7/7] pinctrl: meson: add interrupt controller to GPIO DT nodes Heiner Kallweit
2017-05-30 21:44 ` 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=7c09969b-ac04-cfa4-7459-7ad25b7c5cbf@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).