| 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) | ||
| commit | a34939a93d3bcdbb2827f1818264a1e65fdd06ca | |
| tree | 78ce949ea969c25e6e3b3decaeb83aeef9531f75 | tree | snapshot (tar.xz tar.gz zip) |
| parent | d18eaeb0fb36f87d31297fd56c22211b23e7cec8 | commit | diff |
ARM: dts: keystone-k2g: 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-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>
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>
| arch/arm/boot/dts/keystone-k2g.dtsi | diff | blob | history |