summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a7c3fb3)
raw | patch | inline | side by side (parent: a7c3fb3)
author | Suman Anna <s-anna@ti.com> | |
Fri, 15 Feb 2019 17:24:25 +0000 (11:24 -0600) | ||
committer | Suman Anna <s-anna@ti.com> | |
Sun, 24 Feb 2019 01:20:51 +0000 (19:20 -0600) |
Update the PRU remoteproc DT bindings to add the properties required
to support the optional virtio rpmsg stack using the virtio-ring based
communication transport between MPU and a PRU core.
Signed-off-by: Suman Anna <s-anna@ti.com>
to support the optional virtio rpmsg stack using the virtio-ring based
communication transport between MPU and a PRU core.
Signed-off-by: Suman Anna <s-anna@ti.com>
Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt | patch | blob | history |
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt b/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt
index 646f26fef3d2ff06d0fff1faae0b265392e8f4ad..021516864e500b684f82b954f4e2395a501976f9 100644 (file)
- firmware-name : should contain the name of the default firmware image file
located on the firmware search path
+Optional Properties:
+--------------------
+The virtio based communication between the MPU and a PRU core _requires_
+either the 'mboxes' property, or the set of 'interrupt-parent', 'interrupts'
+and 'interrupt-names' properties to be defined. The latter option is the
+preferred choice. The 'mboxes' property is not applicable for 66AK2G and
+DA850/OMAP-L138 SoCs.
+
+- mboxes : OMAP Mailbox specifier denoting the sub-mailbox, if using
+ a mailbox for IPC signalling between host and a PRU core.
+ The specifier format is as per the bindings,
+ Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
+ This property should match with the sub-mailbox node used
+ in the corresponding firmware image.
+- interrupt-parent : phandle to the PRUSS INTC node. Should be defined if
+ interrupts property is to be used.
+- interrupts : array of interrupt specifiers if using PRU system events
+ for IPC signalling between host and a PRU core. This
+ property should match with the PRU system event used in
+ the corresponding firmware image.
+- interrupt-names : should use one of the following names for each interrupt,
+ the name should match the corresponding PRU system event
+ number,
+ "vring" - for PRU to HOST virtqueue signalling
+ "kick" - for HOST to PRU virtqueue signalling
+
Example:
--------
<0x4a322400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "am335x-pru0-fw";
+ interrupt-parent = <&pruss_intc>;
+ interrupts = <16>, <17>;
+ interrupt-names = "vring", "kick";
};
pru1: pru@4a338000 {
<0x4a324400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "am335x-pru1-fw";
+ interrupt-parent = <&pruss_intc>;
+ interrupts = <18>, <19>;
+ interrupt-names = "vring", "kick";
+ /* mboxes = <&mailbox &mbox_pru1>; */
};
};
};