From: majun258@huawei.com (MaJun)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v6 1/4] dt-binding:Documents of the mbigen bindings
Date: Tue, 20 Oct 2015 20:10:29 +0800 [thread overview]
Message-ID: <1445343032-8032-2-git-send-email-majun258@huawei.com> (raw)
In-Reply-To: <1445343032-8032-1-git-send-email-majun258@huawei.com>
From: Ma Jun <majun258@huawei.com>
Add the mbigen msi interrupt controller bindings document.
This patch based on Mark Rutland's patch
https://lkml.org/lkml/2015/7/23/558
Signed-off-by: Ma Jun <majun258@huawei.com>
---
Documentation/devicetree/bindings/arm/mbigen.txt | 63 ++++++++++++++++++++++
1 files changed, 63 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/mbigen.txt
diff --git a/Documentation/devicetree/bindings/arm/mbigen.txt b/Documentation/devicetree/bindings/arm/mbigen.txt
new file mode 100644
index 0000000..eb9a7fd
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/mbigen.txt
@@ -0,0 +1,63 @@
+Hisilicon mbigen device tree bindings.
+=======================================
+
+Mbigen means: message based interrupt generator.
+
+MBI is kind of msi interrupt only used on Non-PCI devices.
+
+To reduce the wired interrupt number connected to GIC,
+Hisilicon designed mbigen to collect and generate interrupt.
+
+
+Non-pci devices can connect to mbigen and generate the
+interrupt by writing ITS register.
+
+The mbigen chip and devices connect to mbigen have the following properties:
+
+Mbigen main node required properties:
+-------------------------------------------
+- compatible: Should be "hisilicon,mbigen-v2"
+- reg: Specifies the base physical address and size of the Mbigen
+ registers.
+- interrupt controller: Identifies the node as an interrupt controller
+- msi-parent: This property has two cells.
+ The 1st cell specifies the ITS this device connected.
+ The 2nd cell specifies the device id.
+- nr-msis:Specifies the total number of interrupt this device has.
+- #interrupt-cells : Specifies the number of cells needed to encode an
+ interrupt source. The value is 2 now.
+
+ The 1st cell is global hardware pin number of the interrupt.
+ This value depends on the Soc design.
+ The 2nd cell is the interrupt trigger type.
+
+Examples:
+
+ mbigen_device_gmac:intc {
+ compatible = "hisilicon,mbigen-v2";
+ reg = <0x0 0xc0080000 0x0 0x10000>;
+ interrupt-controller;
+ msi-parent = <&its_dsa 0x40b1c>;
+ num-msis = <9>;
+ #interrupt-cells = <2>;
+ };
+
+Devices connect to mbigen required properties:
+----------------------------------------------------
+-interrupt-parent: Specifies the mbigen device node which device connected.
+-interrupts:specifies the interrupt source.
+ The 1st cell is global hardware pin number of the interrupt.
+ This value depends on the Soc design.
+ The 2nd cell is the interrupt trigger type
+
+Examples:
+ gmac0: ethernet at c2080000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ reg = <0 0xc2080000 0 0x20000>,
+ <0 0xc0000000 0 0x1000>;
+ interrupt-parent = <&mbigen_device_gmac>;
+ interrupts = <656 1>,
+ <657 1>;
+ };
+
--
1.7.1
next prev parent reply other threads:[~2015-10-20 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 12:10 [PATCH RESEND v6 0/4] irqchip:support mbigen interrupt controller MaJun
2015-10-20 12:10 ` MaJun [this message]
2015-10-20 12:10 ` [PATCH RESEND v6 2/4] irqchip: add platform device driver for mbigen device MaJun
2015-10-20 12:10 ` [PATCH RESEND v6 3/4] irqchip:create irq domain for each " MaJun
2015-10-20 18:43 ` kbuild test robot
2015-10-21 5:57 ` majun (F)
2015-10-20 12:10 ` [PATCH RESEND v6 4/4] irqchip:implement the mbigen irq chip operation functions MaJun
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=1445343032-8032-2-git-send-email-majun258@huawei.com \
--to=majun258@huawei.com \
--cc=linux-arm-kernel@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).