summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: d18eaeb)
raw | patch | inline | side by side (parent: d18eaeb)
author | Suman Anna <s-anna@ti.com> | |
Tue, 31 Jan 2017 00:50:18 +0000 (18:50 -0600) | ||
committer | Suman Anna <s-anna@ti.com> | |
Sun, 24 Feb 2019 01:20:51 +0000 (19:20 -0600) |
Two PRU system events "vring" and "kick" have been added to each
PRU node in each of the PRU-ICSS0 and PRU-ICSS1 remote processor
subsystems to enable the virtio/rpmsg communication between MPU
and that PRU core. The additions are done in the common base
keystone-k2g.dtsi file, and so are inherited by all 66AK2G boards.
The PRU system events is the preferred approach over using the
alternate IPCGR registers, as it eliminates an external MMR 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. Note that the 66AK2G SoCs do not have the OMAP
Mailbox IP, so there is no option of using mailboxes.
Signed-off-by: Suman Anna <s-anna@ti.com>
PRU node in each of the PRU-ICSS0 and PRU-ICSS1 remote processor
subsystems to enable the virtio/rpmsg communication between MPU
and that PRU core. The additions are done in the common base
keystone-k2g.dtsi file, and so are inherited by all 66AK2G boards.
The PRU system events is the preferred approach over using the
alternate IPCGR registers, as it eliminates an external MMR 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. Note that the 66AK2G SoCs do not have the OMAP
Mailbox IP, so there is no option of using mailboxes.
Signed-off-by: Suman Anna <s-anna@ti.com>
arch/arm/boot/dts/keystone-k2g.dtsi | patch | blob | history |
index 19b4e87e6dfe245945f7619b792e5f0d76348af6..a84b2092124657649f3df7279124b4f0a6ff5d5b 100644 (file)
<0x20aa2400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "k2g-pru0_0-fw";
+ interrupt-parent = <&pruss0_intc>;
+ interrupts = <16>, <17>;
+ interrupt-names = "vring", "kick";
};
pru0_1: pru@20ab8000 {
<0x20aa4400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "k2g-pru0_1-fw";
+ interrupt-parent = <&pruss0_intc>;
+ interrupts = <18>, <19>;
+ interrupt-names = "vring", "kick";
};
pruss0_mdio: mdio@20ab2400 {
<0x20ae2400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "k2g-pru1_0-fw";
+ interrupt-parent = <&pruss1_intc>;
+ interrupts = <16>, <17>;
+ interrupt-names = "vring", "kick";
};
pru1_1: pru@20af8000 {
<0x20ae4400 0x100>;
reg-names = "iram", "control", "debug";
firmware-name = "k2g-pru1_1-fw";
+ interrupt-parent = <&pruss1_intc>;
+ interrupts = <18>, <19>;
+ interrupt-names = "vring", "kick";
};
pruss1_mdio: mdio@20af2400 {