From: Dave Gerlach <d-gerlach@ti.com>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Ohad Ben-Cohen <ohad@wizery.com>, Suman Anna <s-anna@ti.com>,
Kevin Hilman <khilman@linaro.org>,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>,
Dave Gerlach <d-gerlach@ti.com>
Subject: [PATCH v2 2/3] Documentation: dt: add ti,am3353-wkup-m3 bindings
Date: Wed, 4 Mar 2015 21:53:59 -0600 [thread overview]
Message-ID: <1425527640-2690-3-git-send-email-d-gerlach@ti.com> (raw)
In-Reply-To: <1425527640-2690-1-git-send-email-d-gerlach@ti.com>
Add the device tree bindings document for ti,am3353-wkup-m3 which is
used by the wkup_m3_rproc driver.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
---
.../bindings/remoteproc/wkup_m3_rproc.txt | 46 ++++++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt
diff --git a/Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt b/Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt
new file mode 100644
index 0000000..995af3d
--- /dev/null
+++ b/Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt
@@ -0,0 +1,46 @@
+Wakeup M3 Remoteproc Driver
+===========================
+
+TI AMx3 family of devices use a Cortex M3 co-processor to help with various
+low power tasks that cannot be controlled from the MPU. The CM3 requires
+a firmware binary to accomplish this. The wkup_m3 remoteproc driver handles
+the loading of the firmware and booting of the CM3.
+
+Wkup M3 Device Node:
+====================
+A wkup_m3 device node is used to represent a wakeup M3 IP instance within
+a SoC.
+
+Required properties:
+--------------------
+- compatible: Should be:
+ "ti,am3353-wkup-m3" for AM33xx SoCs
+ "ti,am4372-wkup-m3" for AM43xx SoCs
+- reg: Contains the wkup_m3 register address ranges for
+ umem and dmem, from the devices address space.
+ NOTE: Parent node must contains ranges specifying
+ mapping from bus address space to device
+ address space.
+- ti,hwmods: Name of the hwmod associated with the mailbox
+- ti,pm-firmware: Name of firmware file to load for remoteproc.
+
+Example:
+--------
+/* AM33xx */
+soc {
+ compatible = "ti,omap-infra";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0x44d00000 0x4000>,
+ <0x80000 0x44d80000 0x2000>;
+
+ ...
+
+ wkup_m3: wkup_m3@44d00000 {
+ compatible = "ti,am3353-wkup-m3";
+ reg = <0x0 0x4000 /* M3 UMEM */
+ 0x80000 0x2000>; /* M3 DMEM */
+ ti,hwmods = "wkup_m3";
+ ti,pm-firmware = "am335x-pm-firmware.elf";
+ };
+};
--
2.3.0
next prev parent reply other threads:[~2015-03-05 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 3:53 [PATCH v2 0/3] remoteproc: Introduce wkup_m3_rproc driver Dave Gerlach
2015-03-05 3:53 ` [PATCH v2 1/3] remoteproc: add a rproc ops for performing address translation Dave Gerlach
2015-03-05 3:53 ` Dave Gerlach [this message]
2015-03-05 3:54 ` [PATCH v2 3/3] remoteproc: wkup_m3: Add wkup_m3 remoteproc driver Dave Gerlach
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=1425527640-2690-3-git-send-email-d-gerlach@ti.com \
--to=d-gerlach@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).