From: Jiaying Liang <jliang@xilinx.com>
To: Jiaying Liang <jliang@xilinx.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
Cyril Chemparathy <cyrilc@xilinx.com>,
"Michal Simek" <michals@xilinx.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
Soren Brinkmann <sorenb@xilinx.com>
Subject: RE: [RFC LINUX PATCH] Dcoumentation: dt: mailbox: Add Xilinx IPI Mailbox
Date: Fri, 22 Sep 2017 06:05:18 +0000 [thread overview]
Message-ID: <BY1PR0201MB0885E6563EBAFE83DF8822A4B0670@BY1PR0201MB0885.namprd02.prod.outlook.com> (raw)
In-Reply-To: <1506034724-14639-1-git-send-email-jliang@xilinx.com>
> -----Original Message-----
> From: Wendy Liang [mailto:wendy.liang@xilinx.com]
> Sent: Thursday, September 21, 2017 3:59 PM
> To: linux-kernel@vger.kernel.org
> Cc: jassisinghbrar@gmail.com; Cyril Chemparathy <cyrilc@xilinx.com>;
> Michal Simek <michals@xilinx.com>; Jiaying Liang <jliang@xilinx.com>
> Subject: [RFC LINUX PATCH] Dcoumentation: dt: mailbox: Add Xilinx IPI
> Mailbox
>
> Xilinx ZynqMP IPI(Inter Processor Interrupt) is a hardware block in ZynqMP
> SoC used for the communication between various processor systems.
>
> Signed-off-by: Wendy Liang <jliang@xilinx.com>
> ---
> .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt | 88
> ++++++++++++++++++++++
> 1 file changed, 88 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt
>
> diff --git a/Documentation/devicetree/bindings/mailbox/xlnx,zynqmp-ipi-
> mailbox.txt b/Documentation/devicetree/bindings/mailbox/xlnx,zynqmp-ipi-
> mailbox.txt
> new file mode 100644
> index 0000000..5d915d1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/xlnx,zynqmp-ipi-mailbox.
> +++ txt
> @@ -0,0 +1,88 @@
> +Xilinx IPI Mailbox Driver
> +========================================
> +
> +The Xilinx IPI(Inter Processor Interrupt) mailbox driver is a mailbox
> +controller that manages the messaging between two IPI agents. Each IPI
> +mailbox has request and response buffers between the two IPI agents.
> +
> ++-------------------------------------+
> +| | Xilinx ZynqMP IPI Mailbox
> +| Controller|
> +| |
> +| +-------------+
> +| | SMC |
> +| | |
> ++--------+--------------+------+------+
> + | |
> + | +-----------------+
> + | | ATF (ARM trusted firmware)
> + | |
> ++-------------------------------------+
> + | | Hardware
> + | |
> + +--------------------------------------+
> + | |
> + +----------------------+ +-----------+ |
> + | | Buffers between | | IPI Agent | |
> + | | two IPI agents | | Registers | |
> + | +--------------------+ +-----------+ |
> + | |
> + | Xilinx ZynqMP IPI |
> + +--------------------------------------+
> +
> +
> +Message Manager Device Node:
> +===========================
> +Required properties:
> +--------------------
> +- compatible: Shall be: "xlnx,zynqmp-ipi-mailbox"
> +- ipi-smc-fid-base Base offset of SMC function IDs for IPI mailbox SMC.
> + It contains the IPI IDs of the two IPI agents.
> +- reg: IPI request and response buffers address range. It
> + can be the IPI buffers from the hardware or it can
> + be carved out shared memory.
> +- reg-names: Reg resource name of the IPI request and response
> + buffers.
> +- #mbox-cells: Shall be 1. Contains the logical channel IDs of the
> + channels on the IPI mailbox.
> +- interrupt-parent: Phandle for the interrupt controller.
> +- interrupts: Interrupt mapping.
> +
> +Required properties:
> +--------------------
> +- method: The method of accessing the IPI agent registers.
> + Permitted values are: "smc" and "hvc". Default is
> + "smc".
> +Example:
> +------------
> + /* APU IPI mailbox driver */
> + ipis {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + ipi_mailbox_apu_rpu0: ipi_mailbox@0 {
> + compatible = "xlnx,zynqmp-ipi-mailbox";
> + reg = <0 0xff990400 40>;
> + reg-names = "apu-rpu0";
> + ipi-smc-fid-base = <0x1010>;
> + method = "smc";
> + #mbox-cells = <1>;
> + interrupt-parent = <&gic>;
> + interrupts = <0 35 4>;
> + };
> + ipi_mailbox_apu_rpu1: ipi_mailbox@1 {
> + compatible = "xlnx,zynqmp-ipi-mailbox";
> + reg = <0 0xff990440 40>;
> + reg-names = "apu-rpu1";
> + ipi-smc-fid-base = <0x1020>;
> + method = "smc";
> + #mbox-cells = <1>;
> + interrupt-parent = <&gic>;
> + interrupts = <0 35 4>;
> + };
> + };
> + device0: device0 {
> + ...
> + mbox-names = "rpu0", "rpu1",
> + mboxes = <&ipi_mailbox_apu_rpu0 0>,
> + < &ipi_mailbox_apu_rpu1 0>;
> + };
> --
> 2.7.4
cc: device tree and linux arm kernel mailing lists.
next prev parent reply other threads:[~2017-09-22 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 22:58 Wendy Liang
2017-09-22 6:05 ` Jiaying Liang [this message]
2017-09-22 11:10 ` Sudeep Holla
2017-09-22 17:37 ` Jiaying Liang
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=BY1PR0201MB0885E6563EBAFE83DF8822A4B0670@BY1PR0201MB0885.namprd02.prod.outlook.com \
--to=jliang@xilinx.com \
--cc=cyrilc@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michals@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sorenb@xilinx.com \
/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
all inboxes | Powered by JetHome®