From: Cyril Bur <cyrilbur@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: [PATCH v3 1/5] Documentation: dt: mailbox: Add Aspeed ast2400/2500 bindings
Date: Tue, 10 Jan 2017 20:06:36 +1100 [thread overview]
Message-ID: <20170110090640.12608-2-cyrilbur@gmail.com> (raw)
In-Reply-To: <20170110090640.12608-1-cyrilbur@gmail.com>
Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
---
.../devicetree/bindings/mailbox/aspeed-mbox.txt | 44 ++++++++++++++++++++++
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mailbox/aspeed-mbox.txt
diff --git a/Documentation/devicetree/bindings/mailbox/aspeed-mbox.txt b/Documentation/devicetree/bindings/mailbox/aspeed-mbox.txt
new file mode 100644
index 000000000000..633cd534d91c
--- /dev/null
+++ b/Documentation/devicetree/bindings/mailbox/aspeed-mbox.txt
@@ -0,0 +1,44 @@
+ASpeed Mailbox Driver
+=====================
+
+The ASpeed mailbox allows for communication between different
+processors. The mailbox on the ASpeed ast2400 and ast2500 is a set of
+16 single byte data registers along with interrupt and configuration
+registers directly on the SoC. These are memory mapped on the aspeed
+and can be accessed via the SuperIO registers on the other processor.
+
+Device Node:
+============
+This represents the mailbox on the Soc.
+
+As the mailbox registers sit on the LPC bus, it makes most sense for
+the device to be within the LPC host node. See
+Documentation/devicetree/bindings/mfd/aspeed-lpc.txt for more
+information. This does not have to be the case, provided the reg
+property can give the full address of the mbox registers.
+
+Required Properties:
+--------------------
+- compatible: Should be one of the following,
+ "aspeed,ast2400-mbox" for ast2400 SoCs
+ "aspeed,ast2500-mbox" for ast2500 SoCs
+
+- reg: Contains the mailbox address register range (base
+ address and length). Keeping in mind that if the node
+ exists within the LPC host node and that base is
+ relative to that.
+
+- interrupts: Contains interrupt information for the mailbox device.
+
+- #mbox-cells: Common property, should be 1.
+
+Example:
+--------
+
+mbox: mbox@180 {
+ compatible = "aspeed,ast2400-mbox";
+ reg = <0x180 0x5c>;
+ interrupts = <46>;
+ #mbox-cells = <1>;
+};
+
--
2.11.0
next prev parent reply other threads:[~2017-01-10 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 9:06 [PATCH v3 0/5] LPC/MBOX work Cyril Bur
2017-01-10 9:06 ` Cyril Bur [this message]
2017-01-10 9:06 ` [PATCH v3 2/5] Documentation: dt: misc: Add Aspeed ast2400/2500 LPC Control bindings Cyril Bur
2017-01-11 1:29 ` Andrew Jeffery
2017-01-10 9:06 ` [PATCH v3 3/5] ARM: dts: aspeed: Add mailbox and LPC Control nodes Cyril Bur
2017-01-11 0:57 ` Joel Stanley
2017-01-10 9:06 ` [PATCH v3 4/5] drivers/misc: Add aspeed ast2400/ast2500 lpc controlling driver Cyril Bur
2017-01-10 9:06 ` [PATCH v3 5/5] drivers/mailbox: Add aspeed ast2400/ast2500 mbox driver Cyril Bur
2017-01-11 0:33 ` Joel Stanley
2017-01-11 3:54 ` Joel Stanley
2017-01-11 4:06 ` Cyril Bur
2017-01-11 1:27 ` Andrew Jeffery
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=20170110090640.12608-2-cyrilbur@gmail.com \
--to=cyrilbur@gmail.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.