From: David Lechner <david@lechnology.com>
To: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: "David Lechner" <david@lechnology.com>,
"Ohad Ben-Cohen" <ohad@wizery.com>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Sekhar Nori" <nsekhar@ti.com>,
"Kevin Hilman" <khilman@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 4/8] dt-bindings: add bindings for TI PRU as remoteproc
Date: Sat, 23 Jun 2018 16:08:06 -0500 [thread overview]
Message-ID: <20180623210810.21232-5-david@lechnology.com> (raw)
In-Reply-To: <20180623210810.21232-1-david@lechnology.com>
This adds a new binding for the TI Programmable Runtime Unit (PRU)
as a remoteproc device.
Signed-off-by: David Lechner <david@lechnology.com>
---
.../bindings/remoteproc/ti_pru_rproc.txt | 51 +++++++++++++++++++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti_pru_rproc.txt
diff --git a/Documentation/devicetree/bindings/remoteproc/ti_pru_rproc.txt b/Documentation/devicetree/bindings/remoteproc/ti_pru_rproc.txt
new file mode 100644
index 000000000000..0e80a8db46d0
--- /dev/null
+++ b/Documentation/devicetree/bindings/remoteproc/ti_pru_rproc.txt
@@ -0,0 +1,51 @@
+TI Programmable Realtime Unit (PRU)
+===================================
+
+Some TI Sitara SoCs contain a Programmable Realtime Unit subsystem with two
+processor cores that can be used for hard-realtime tasks.
+
+
+Required properties:
+--------------------
+The following are the mandatory properties:
+
+- compatible: Should be one of the following,
+ "ti,da850-pru-rproc" for AM18xx/OMAPL138 SoCs
+ "ti,am3352-pru-rproc" for AM355x SoCs
+
+- reg: Should contain the memory region for the PRUSS
+
+- interrupts: Should contain the interrupt number used to receive the
+ virtualqueue kick interrupts from the PRU (i.e.
+ PRU_EVTOUT0 and PRU_EVTOUT1)
+
+- interrupt-names Should contain "pru0-vq", "pru1-vq"
+
+Optional properties:
+--------------------
+
+- power-domains: A phandle to the power domain that powers the PRUSS
+
+- ti,hwmods: Name of the hwmod associated to the PRUSS, which is
+ typically "pruss"
+
+Example:
+--------
+
+ // AM18xx
+ pru_rproc: cpu@30000 {
+ compatible = "ti,da850-pru-rproc";
+ reg = <0x30000 0x10000>;
+ interrupts = <3>, <4>;
+ interrupt-names = "pru0-vq", "pru1-vq";
+ power-domains = <&psc0 13>;
+ };
+
+ // AM335x
+ pru_rproc: cpu@4a300000 {
+ compatible = "ti,am3352-pru-rproc";
+ reg = <0x4a300000 0x80000>;
+ interrupts = <20>, <21>;
+ interrupt-names = "pru0-vq", "pru1-vq";
+ ti,hwmods = "pruss";
+ };
--
2.17.1
next prev parent reply other threads:[~2018-06-23 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180623210810.21232-1-david@lechnology.com>
2018-06-23 21:08 ` [PATCH 1/8] remoteproc: add map parameter to da_to_va David Lechner
2018-06-23 21:08 ` [PATCH 2/8] remoteproc: add page lookup for TI PRU to ELF loader David Lechner
2018-06-23 21:08 ` [PATCH 3/8] ARM: OMAP2+: add pdata quirks for PRUSS reset David Lechner
2018-06-23 21:08 ` David Lechner [this message]
2018-07-03 20:59 ` [PATCH 4/8] dt-bindings: add bindings for TI PRU as remoteproc Rob Herring
2018-06-23 21:08 ` [PATCH 5/8] remoteproc: new driver for TI PRU David Lechner
2018-06-29 10:14 ` Roger Quadros
[not found] ` <CA+CtpRhQ07=3UytY7QrfnpWkY06UqHbNVq099Coez3C4H3U5yg@mail.gmail.com>
2018-07-02 8:05 ` Roger Quadros
2018-06-23 21:08 ` [PATCH 6/8] ARM: davinci_all_defconfig: enable PRU remoteproc module David Lechner
2018-06-23 21:08 ` [PATCH 7/8] ARM: dts: da850: add node for PRUSS David Lechner
2018-06-23 21:08 ` [PATCH 8/8] ARM: dts: am33xx: add node for PRU remoteproc David Lechner
2018-06-29 9:58 ` New remoteproc driver for TI PRU Roger Quadros
2018-06-29 17:44 ` David Lechner
2018-06-30 0:17 ` Suman Anna
2018-08-06 16:32 ` David Lechner
2018-08-07 1:39 ` Suman Anna
2018-07-02 8:17 ` Roger Quadros
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=20180623210810.21232-5-david@lechnology.com \
--to=david@lechnology.com \
--cc=bcousson@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--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).