aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSuman Anna2018-01-29 15:41:00 -0600
committerSuman Anna2019-02-23 19:20:51 -0600
commitd18eaeb0fb36f87d31297fd56c22211b23e7cec8 (patch)
treef1996264dc9082ac252a78f1778a8212dac3ecfd
parentb7e221bb51c3ebd23cf7cb0336929cbc861d5ad2 (diff)
downloadremoteproc-d18eaeb0fb36f87d31297fd56c22211b23e7cec8.tar.gz
remoteproc-d18eaeb0fb36f87d31297fd56c22211b23e7cec8.tar.xz
remoteproc-d18eaeb0fb36f87d31297fd56c22211b23e7cec8.zip
ARM: dts: DRA7: Add PRU system events for virtio
Two PRU system events "vring" and "kick" have been added to each PRU node in each of the PRU-ICSS1 and PRU-ICSS2 remote processor subsystems to enable the virtio/rpmsg communication between MPU and that PRU core. The additions are done in the common base dra7.dtsi file, and so are inherited by all the AM57xx boards. Do note that PRUSS is not available/supported on the DRA7xx SoCs SoCs and is only limited to the AM57xx SoCs. The PRU system events is the preferred approach over using OMAP mailboxes, as it eliminates an external peripheral access from the PRU-side, and keeps the interrupt generation internal to the PRUSS. The difference from MPU would be minimal in using one versus the other. Mailboxes can still be used if desired. Either approach would require that an appropriate firmware image is loaded/booted on the PRU. Signed-off-by: Suman Anna <s-anna@ti.com>
-rw-r--r--arch/arm/boot/dts/dra7.dtsi12
1 files changed, 12 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 3a7c0436309b..812355048db8 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -1239,6 +1239,9 @@
1239 <0x4b222400 0x100>; 1239 <0x4b222400 0x100>;
1240 reg-names = "iram", "control", "debug"; 1240 reg-names = "iram", "control", "debug";
1241 firmware-name = "am57xx-pru1_0-fw"; 1241 firmware-name = "am57xx-pru1_0-fw";
1242 interrupt-parent = <&pruss1_intc>;
1243 interrupts = <16>, <17>;
1244 interrupt-names = "vring", "kick";
1242 }; 1245 };
1243 1246
1244 pru1_1: pru@4b238000 { 1247 pru1_1: pru@4b238000 {
@@ -1248,6 +1251,9 @@
1248 <0x4b224400 0x100>; 1251 <0x4b224400 0x100>;
1249 reg-names = "iram", "control", "debug"; 1252 reg-names = "iram", "control", "debug";
1250 firmware-name = "am57xx-pru1_1-fw"; 1253 firmware-name = "am57xx-pru1_1-fw";
1254 interrupt-parent = <&pruss1_intc>;
1255 interrupts = <18>, <19>;
1256 interrupt-names = "vring", "kick";
1251 }; 1257 };
1252 1258
1253 pruss1_mdio: mdio@4b232400 { 1259 pruss1_mdio: mdio@4b232400 {
@@ -1328,6 +1334,9 @@
1328 <0x4b2a2400 0x100>; 1334 <0x4b2a2400 0x100>;
1329 reg-names = "iram", "control", "debug"; 1335 reg-names = "iram", "control", "debug";
1330 firmware-name = "am57xx-pru2_0-fw"; 1336 firmware-name = "am57xx-pru2_0-fw";
1337 interrupt-parent = <&pruss2_intc>;
1338 interrupts = <16>, <17>;
1339 interrupt-names = "vring", "kick";
1331 }; 1340 };
1332 1341
1333 pru2_1: pru@4b2b8000 { 1342 pru2_1: pru@4b2b8000 {
@@ -1337,6 +1346,9 @@
1337 <0x4b2a4400 0x100>; 1346 <0x4b2a4400 0x100>;
1338 reg-names = "iram", "control", "debug"; 1347 reg-names = "iram", "control", "debug";
1339 firmware-name = "am57xx-pru2_1-fw"; 1348 firmware-name = "am57xx-pru2_1-fw";
1349 interrupt-parent = <&pruss2_intc>;
1350 interrupts = <18>, <19>;
1351 interrupt-names = "vring", "kick";
1340 }; 1352 };
1341 1353
1342 pruss2_mdio: mdio@4b2b2400 { 1354 pruss2_mdio: mdio@4b2b2400 {