Merge branch 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the updated remoteproc feature branch that adds a new sysfs file 'name' to allow userspace to easily identify a remoteproc. An equivalent file was already present in debugfs as well, but sysfs provides a more standardized userspace interface since debugfs is optional. * 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc: remoteproc: Add a sysfs interface for name Signed-off-by: Suman Anna <s-anna@ti.com>
remoteproc: Add a sysfs interface for name [ Upstream commit 6ed756aa0148a5ad0dbdced6f14f22e2f5748d35 ] This patch adds a sysfs interface that provides the name of the remote processor to userspace. This allows the userspace to identify a remote processor as the remoteproc devices themselves are created based on probe order and can change from one boot to another or at runtime. The name is made available in debugfs originally, and is being retained for now. This can be cleaned up after couple of releases once users get familiar with the new interface. [s-anna@ti.com: cherry-pick commit '6ed756aa0148' from v5.4] Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Merge branch 'topic/4.19/am65x' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the dedicated AM65x remoteproc topic branch that adds the preliminary support for representing PRUSS clocks as clocks nodes in DT. The support is added _only_ for the ICSSG instances on K3 AM65x SoCs at the moment, and will be enhanced in the future to scale for all applicable SoCs that have a PRUSS. * 'topic/4.19/am65x' of git://git.ti.com/rpmsg/remoteproc: arm64: dts: ti: k3-am65-main: Add input clock to IEP nodes dt-bindings: soc: ti: pruss: Update IEP node bindings TEMP: soc: ti: pruss: support CORECLK_MUX and IEPCLK_MUX TEMP: arm64: dts: ti: k3-am65-main: Add IEP and CORE clock muxes TEMP: dt-bindings: soc: ti: pruss: Add IEP and CORE clock mux Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: soc: ti: pruss: Update IEP node bindings IEP driver needs to know the clock rate of the IEP core clock. Provide a clocks property for that. TODO: Update the existing examples once these clocks are added on those SoCs Signed-off-by: Roger Quadros <rogerq@ti.com> [s-anna@ti.com: add under the proper sub-section] Signed-off-by: Suman Anna <s-anna@ti.com>
TEMP: dt-bindings: soc: ti: pruss: Add IEP and CORE clock mux ICSS/ICSSG modules have an IEP clock mux that allow selection of internal IEP clock from 2 clock sources. ICSSG module has a CORE clock mux that allows selection of internal CORE clock from 2 clock sources. Add binding information for these 2 clock muxes. Signed-off-by: Roger Quadros <rogerq@ti.com> [s-anna@ti.com: few minor fixups] Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the updated remoteproc feature branch that adds the support for system suspend/resume and runtime auto-suspend/resume support on the IPU and DSP remote processors on OMAP4, OMAP5 and DRA7 SoCs. The feature branch merge also pulls in automatically the dependent OMAP iommu feature branch with suspend/resume support. OMAP mailbox driver already has the suspend/resume support in upstream 4.19 kernel. * 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc: remoteproc: Fix sysfs interface to stop a suspended processor remoteproc/omap: add support for runtime auto-suspend/resume remoteproc/omap: add support for system suspend/resume ARM: dts: dra7: Add standby info for IPU & DSPs ARM: dts: omap5: Add standby info for IPU and DSP ARM: dts: omap4: Add standby info for IPU and DSP dt-bindings: remoteproc: Update omap remoteproc binding for suspend iommu/omap: introduce new API for runtime suspend/resume control iommu/omap: Add system suspend/resume support iommu/omap: add logic to save/restore locked TLBs iommu/omap: streamline enable/disable through runtime pm callbacks ARM: OMAP2+: add pdata-quirks for OMAP3 ISP IOMMU ARM: OMAP2+: Add iommu pdata-quirks for DRA7 DSP EDMA MMUs ARM: OMAP2+: plug in device_enable/idle ops for IOMMUs iommu/omap: add pdata ops for omap_device_enable/idle Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: remoteproc: Update omap remoteproc binding for suspend The OMAP remoteproc binding has been updated to add an additional property, "ti,rproc-standby-info". The property is used to define the standby register address required by the OMAP remoteproc driver to check that a remote proessor has entered standby and ready to be suspended during a system suspend or a runtime auto-suspend of the corresponding remoteproc device. Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the remoteproc feature branch supporting the boot of all DSP and IPU remote processors on OMAP4, OMAP5 and various DRA7xx/AM57xx SoCs. The feature branch also pulls in automatically the dependent iommu feature tree with DRA7 support into the rpmsg-ti-linux-4.19.y RPMsg integration branch. OMAP mailbox is fully upstream in vanilla 4.19 kernel for all OMAP SoCs. The merge also includes couple of fixes to the OMAP4, OMAP5 and DRA7 clock data files and the DMTimer nodes to be able to assign the correct functional clocks for certain DMTimers and be able to set their parent clocks. The supported functional features in OMAP remoteproc include: - Device Tree based support for device-specific carveouts and CMA pools - Boot of device-tree based IPU and DSP remoteproc devices - Internal memory loading support on DSPs - BIOS Tick timer support using OMAP DMTimer clocksource code - Cleanup of legacy platform device based code Supported platforms include OMAP4 Pandaboard, OMAP5 uEVM, DRA7 EVMs, DRA76 EVM, both DRA72 rev.B and rev.C EVMs, DRA71 EVM, all AM57xx BeagleBoard-X15 boards and their derivative boards, AM572x IDK, AM571x IDK and AM574x IDK boards. The IVA and DSP remote processors will be running at OPP_NOM clock frequencies by default, and at OPP_HIGH with the appropriate U-Boot on boards/SoCs that can support them (DRA71 only supports OPP_NOM). * 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc: (72 commits) ARM: dts: am571x-idk: Add CMA pools and enable IPUs & DSP1 rprocs ARM: dts: am572x-idk-common: Add CMA pools and enable IPU & DSP rprocs ARM: dts: beagle-x15-common: Add CMA pools and enable IPU & DSP rprocs ARM: dts: dra76-evm: Add CMA pools and enable IPU & DSP rprocs ARM: dts: dra71-evm: Add CMA pools and enable IPUs & DSP1 rprocs ARM: dts: dra72-evm-revc: Add CMA pools and enable IPUs & DSP1 rprocs ARM: dts: dra72-evm: Add CMA pools and enable IPUs & DSP1 rprocs ARM: dts: dra7-evm: Add CMA pools and enable IPU & DSP rprocs ARM: dts: dra7-ipu-dsp-common: Add timers to IPU and DSP nodes ARM: dts: dra7-ipu-dsp-common: Add mailboxes to IPU and DSP nodes ARM: dts: dra7-ipu-dsp-common: Move mailboxes into common files ARM: OMAP2+: Extend rproc pdata-quirks for DSP2 rproc on DRA74x ARM: OMAP2+: Extend rproc pdata-quirks for IPUs & DSP1 on DRA7 ARM: DRA7: hwmod_data: add data for DSP2 processor ARM: DRA7: hwmod_data: add data for IPU and DSP1 rprocs ARM: dts: dra72x: Add aliases for rproc nodes ARM: dts: dra74x: Add aliases for rproc nodes ARM: dts: dra74x: Add DSP2 processor device node ARM: dts: dra7: Add common IPU and DSP nodes ARM: dts: omap5-uevm: Add system timers to DSP and IPU ... Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'topic/4.19/am65x' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the dedicated AM65x remoteproc topic branch that adds the support for the dual-core Arm Cortex R5F cores present within a R5F subsystem in MCU domain on AM65x SoCs through a new TI K3 R5F remoteproc driver. The remoteproc driver is somewhat different from other existing remoteproc drivers - it requires two or more carveout reserved memory nodes to be defined. The firmwares are expected to use the TCMs for boot-strapping themselves to be able to execute from DDR memory. Supported features include functionality for both LockStep mode and Split modes, loading into on-chip internal memories etc. There is no support for advanced features such as Power Management or Error Recovery. The RPMsg stack is supported through OMAP Mailboxes much like the OMAP remoteproc driver. The support required couple of enhancements to the remoteproc core - new .prepare() and .unprepare() ops were added that are needed by the R5F remoteproc driver for managing its reset for loading into TCMs. The merge also includes a platform tree merge to bring in the TI-SCI processor control support and the support for the MCU SRAM through the mmio-sram driver. * topic/4.19/am65x: (37 commits) arm64: dts: ti: k3-am65-mcu: Reserve some MCU SRAM for MCU R5F0 remoteproc/k3-r5: add loading support for on-chip SRAM regions dt-bindings: remoteproc: k3-r5f: Update bindings for on-chip SRAM support arm64: dts: ti: k3-am65: Add aliases for R5F rproc nodes arm64: dts: ti: k3-am654-base-board: Add DDR carveout memory nodes for R5Fs arm64: dts: ti: k3-am65-mcu: Add MCU domain R5F cluster node arm64: dts: ti: k3-am65: add R5F ranges in interconnect nodes HACK: remoteproc: silence devmem error for rprocs with no MMU remoteproc/k3-r5: add a remoteproc driver for R5F subsystem remoteproc/k3-r5: add TI-SCI processor control helper functions dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs remoteproc/omap: Check for undefined mailbox messages remoteproc: use a local copy for the name field remoteproc: add prepare and unprepare ops clk: keystone: sci-clk: add support from parsing clock info from DT dt-bindings: clock: ti,sci-clk: Add support for parsing clock info from DT soc: ti: Add TI_MESSAGE_MANAGER to default K3 AM65x SoC options firmware: ti_sci: Add support for processor control arm64: dts: ti: k3-am65-mcu: Add the MCU RAM node arm64: dts: ti: k3-am65: add MCU SRAM ranges in interconnect nodes ... Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: remoteproc: k3-r5f: Update bindings for on-chip SRAM support The K3 SoCs have various internal on-chip SRAM memories like the SRAM within the MCU domain or the shared MSMC RAM within NavSS that can be used for multiple purposes. One such purpose is to have the MCU domain R5F cores to use a portion of such on-chip SRAM for executing code. Update the K3 R5F remoteproc bindings to add the properties required to support the optional on-chip SRAM loading support. Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs The Texas Instruments K3 family of SoCs have one of more dual-core Arm Cortex R5F processor subsystems/clusters (R5FSS). Add the device tree bindings document for these R5F subsystem devices. These R5F processors do not have an MMU, and so require fixed memory carveout regions matching the firmware image addresses. The nodes require more than one memory region, with the first memory region used for DMA allocations at runtime. The remaining memory regions are reserved and are used for the loading and running of the R5F remote processors. The added example illustrates the DT nodes for the single R5FSS device present on K3 AM65x family of SoCs. Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'platform-ti-linux-4.19.y' of git://git.ti.com/~rrnayak/ti-linux-kernel/platform-linux-feature-tree into topic/4.19/am65x Resync/pull in the latest platform base tree (golden/vanilla equivalent patches) into the AM65x remoteproc topic branch. The merge pulls in the necessary TI-SCI processor control API and the MCU SRAM support on AM65x SoCs. Also included are few important TI-SCI clock fixes and crypto patches. This merges establishes the baseline to allow the R5F remoteproc driver support to be added on K3 AM65x platforms. The OMAP Mailbox support for K3 platforms and the board support for various AM65x boards is already available in the topic branch with the previous mailbox feature branch merge. * platform-ti-linux-4.19.y: (23 commits) clk: keystone: sci-clk: add support from parsing clock info from DT dt-bindings: clock: ti,sci-clk: Add support for parsing clock info from DT soc: ti: Add TI_MESSAGE_MANAGER to default K3 AM65x SoC options firmware: ti_sci: Add support for processor control arm64: dts: ti: k3-am65-mcu: Add the MCU RAM node arm64: dts: ti: k3-am65: add MCU SRAM ranges in interconnect nodes kbuild: dtbinst: Install overlays dmaengine: ti: k3-udma: Fix compiler warning in udma_get_chan_pair clk: keystone: sci-clk: add slack to clk-set-rate passed to firmware clk: keystone: sci-clk: increase the max gap size to 50 for clk ids HACK: firmware: ti_sci: increase timeout to 10000ms arm64: dts: ti: am6: Add the trng node char: hwrng: Kconfig: Or ARCH_K3 dependency for HW_RANDOM_OMAP arm64: dts: k3-am6: Add crypto accelarator node sa2ul: Add 3DES ECB & CBC Mode support crypto: sa2ul: Add hmac(sha256) HMAC algorithm support crypto: sa2ul: Add hmac(sha1) HMAC algorithm support crypto: sa2ul: Add hmac(sha256)cbc(aes) AEAD Algo support crypto: sha256_generic: Export the Transform function crypto: sa2ul: Add aead support for hmac(sha1)cbc(aes) algorithm ... Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'topic/4.19/am65x' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the dedicated AM65x remoteproc topic branch that adds the support to various PRUSS platform drivers for the next-generation PRUSS IP - ICSSG present on K3 AM65x family of SoCs. The ICSSG IP has various new additions compared to the current generation PRUSS IP. The RPMsg stack is supported through the PRU System Events, including the support for the two auxiliary RTU cores in each ICSSG. Supported instances include all the three ICSSG - ICSSG0, ICSSG1 and ICSSG2 instances on the AM65x EVM and IDK boards. The support required some enhancements to both the PRU remoteproc driver and the PRUSS INTC irqchip drivers to account for the newer RTU cores and the increased number of PRUSS INTC System Events, Interrupt Channels and Host Interrupts. The PRU/RTU remoteproc cores required a custom ELF loader function. A second version of the PRUSS INTC custom vendor resource is also added to allow the firmwares to configure the newer INTC appropriately. The ICSSG Core clocks and IEP clocks are also sourced differently to run at 250 MHz instead of the default 200 MHz for maximum performance. The merge also brings in the support for Mailbox IP present within the MAIN NavSS module on the K3 AM65x family of SoCs. * 'topic/4.19/am65x' of git://git.ti.com/rpmsg/remoteproc: arm64: dts: ti: k3-am65-main: Add ICSSG MDIO nodes arm64: dts: ti: k3-am65-main: Add mii-g-rt nodes in ICSSG arm64: dts: ti: k3-am65-main: Add PRU system events for virtio arm64: dts: ti: k3-am65-main: Add ICSSG nodes soc: ti: pruss: Configure different internal ICSSG source clocks remoteproc/pru: Add support for various PRU cores on K3 AM65x SoCs remoteproc/pru: Introduce new vendor interrupt resource for K3 AM65x SoCs dt-bindings: remoteproc: pru: Update bindings for K3 AM65x SoCs irqchip/pruss-intc: Add support for ICSSG INTC on K3 AM65x SoCs dt-bindings: irqchip: pruss-intc: Update bindings for K3 AM65x SoCs soc: ti: pruss: enable support for ICSSG subsystems on K3 AM65x SoCs dt-bindings: soc: ti: pruss: Update bindings for K3 AM65x SoCs remoteproc/pru: use macros and types from omap mailbox dt-bindings: mailbox: omap: Update example for TI K3 AM65x SoCs arm64: dts: ti: k3-am65-main: Rename IPC sub-mailboxes arm64: dts: ti: k3-am65-main: Add IPC sub-mailbox nodes for R5Fs arm64: dts: ti: k3-am65-main: Add mailbox cluster nodes ti_config_fragments: v8_rpmsg: Enable OMAP Mailbox support mailbox/omap: add support for TI K3 SoCs dt-bindings: mailbox: omap: Update bindings for TI K3 AM65x SoCs Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: remoteproc: pru: Update bindings for K3 AM65x SoCs The K3 AM65x SoCs have the next generation of the PRU-ICSS IP, commonly called ICSSG. The ICSSG IP on K3 SoCs has two PRU cores and two additional custom PRU cores called Real Time Units (RTUs). Update the PRU binings for these newer generarion ICSSG instances. Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: irqchip: pruss-intc: Update bindings for K3 AM65x SoCs The K3 AM65x SoCs have the next generation of the PRU-ICSS IP, commonly called ICSSG. The ICSSG interrupt controller on K3 SoCs provide a higher number of host interrupts (20 vs 10) and can handle an increased number of input events (160 vs 64) from various SoC interrupt sources. Update the PRUSS interrupt controller binings for these newer generarion ICSSG instances. Signed-off-by: Suman Anna <s-anna@ti.com>
dt-bindings: soc: ti: pruss: Update bindings for K3 AM65x SoCs The K3 AM65x SoCs have the next generation of the PRU-ICSS IP, commonly called ICSSG. The ICSSG IP on K3 SoCs has couple of additional sub-modules (two IEP and MII_RT sub-modules each vs one, a new MII_G_RT sub-module) w.r.t previous generation PRU-ICSS IPs. Update the PRUSS bindings for these newer ICSSG instances including the info for MII_G_RT. NOTE: - The usage of the second IEP and MII_RT sub-module instances are yet to be determined, and so are yet to be added. Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'mailbox-linux-4.19.y' of git://git.ti.com/rpmsg/mailbox into topic/4.19/am65x Pull in the mailbox feature branch into a new topic remoteproc branch dedicated for adding remoteproc support patches for the remote processors present on K3 AM65x SoCs. The merge brings in the base platform and board support for K3 AM65x SoCs, including the support for the Mailbox IP present within the Main NavSS sub-module on K3 AM65x SoCs. * 'mailbox-linux-4.19.y' of git://git.ti.com/rpmsg/mailbox: (134 commits) dt-bindings: mailbox: omap: Update example for TI K3 AM65x SoCs arm64: dts: ti: k3-am65-main: Rename IPC sub-mailboxes arm64: dts: ti: k3-am65-main: Add IPC sub-mailbox nodes for R5Fs arm64: dts: ti: k3-am65-main: Add mailbox cluster nodes ti_config_fragments: v8_rpmsg: Enable OMAP Mailbox support mailbox/omap: add support for TI K3 SoCs dt-bindings: mailbox: omap: Update bindings for TI K3 AM65x SoCs ti_config_fragments: v8_defconfig_map: Add v8 rpmsg config file ti_config_fragments: v8_rpmsg: Add RPMsg domain config fragment file ti_config_fragments: defconfig_map: Include RPMsg config fragment ti_config_fragments: rpmsg: Add RPMsg domain config fragment file dmaengine: ti: k3-udma: Try to use the highest TPL channels for MEM_TO_MEM dmaengine: ti: k3-udma: Only allow MEM_TO_MEM transfer on the main UDMA ti_config_fragments/defconfig_map.txt: add missing baseport.cfg entries ti_config_fragments: v8_baseport: Forward port v8_baseport cfg from 4.14 arm64: dts: ti: k3-am6: Add NAVSS and PDMA nodes dmaengine: ti: k3-udma: Add glue layer for non DMAengine users dmaengine: ti: New driver for K3 UDMA dmaengine: ti: Add cppi5 header for UDMA dt-bindings: dma: ti: Add document for K3 UDMA ... Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the updated remoteproc feature branch that adds the base infrastructure to enable the PRUSS Ethernet driver to be able to load and boot Ethernet-specific firmwares onto the PRUs on various TI industrial boards (AM335x ICEv2, AM437x IDK, AM572x IDK, AM571x IDK, and K2G-ICE boards). The support is made possible by adding various new API to the PRUSS platform drivers - these include API to get a PRU rproc instance, and from it a PRUSS instance, request various memory regions, API to program the various PRUSS syscon sub-modules and helper functions to program certain common registers within the PRUSS CFG space. The PRU remoteproc infrastructure is also enhanced to parse the client DT nodes and program in client specific features such as the PRU core firmware names, the internal PinMux configuration, and PRUSS INTC mapping configuration. The DT INTC configuration feature will override any configuration provided through the firmware's resource table, paving way to use a resource-table less PRU firmwares in the future. * 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc: soc: ti: pruss: enable OCP master ports in SYSCFG always remoteproc/pru: add support for configuring GPMUX based on client setup soc: ti: pruss: add helper functions to get/set PRUSS_CFG_GPMUX soc: ti: pruss: add helper functions to set GPI mode, MII_RT_event and XFR soc: ti: pruss: add pruss_regmap_read()/update() API soc: ti: pruss: add pruss_{request,release}_mem_region() API soc: ti: pruss: add pruss_get()/put() API remoteproc/pru: add pru_rproc_get_id() API to retrieve the PRU id remoteproc/pru: add support for parsing pru interrupt mapping from DT remoteproc/pru: configure firmware based on client setup remoteproc/pru: Add pru_rproc_set_ctable() function remoteproc/pru: deny rproc sysfs ops for PRU client driven boots remoteproc/pru: add APIs to get and put the PRU cores dt-bindings: remoteproc: pru: Document application node bindings Signed-off-by: Suman Anna <s-anna@ti.com>
Merge branch 'rproc-linux-4.19.y' of git://git.ti.com/rpmsg/remoteproc into rpmsg-ti-linux-4.19.y Pull in the updated remoteproc feature branch that adds new platform drivers for the PRUSS subsystem on OMAP-architecture based AM33xx, AM437x, and AM57xx SoCs and Keystone-architecture based 66AK2G SoCs. 66AK2G is the first SoC in the Keystone 2 family to have PRUSS IPs. The drivers include a PRUSS SoC bus driver, a PRUSS platform driver, a PRUSS INTC irqchip driver, and a PRU remoteproc driver to load and boot the PRU cores within the PRU-ICSS subsystem. The new modules that will be built are pruss_soc_bus.ko, pruss.ko, irq-pruss-intc.ko and pru_rproc.ko respectively. The PRU remoteproc driver follows a no auto-boot architecture, and requires a client driver/application to trigger a PRU boot. The PRUSS SoC bus driver and PRUSS platform drivers are moved to drivers/soc/ti folder, and the PRUSS INTC irqchip driver is moved to drivers/irqchip folder for 4.19 kernel following initial feedback from upstream maintainers. Supported instances include the single PRU-ICSS on AM335x, both the regular PRU-ICSS1 and the smaller PRU-ICSS0 instances on AM437x SoCs, both the PRU-ICSS1 and PRU-ICSS2 instances on AM57xx SoCs, and both the PRU-ICSS0 and PRU-ICSS1 instances on 66AK2G SoCs. Supported platforms include all the TI supported AM33xx and AM437x boards, the AM57xx BeagleBoard-X15 boards, AM57xx GP EVMs, all three of the AM571x, AM572x and AM574x IDKS, and both the K2G-EVM and K2G-ICE boards. The support required some enhancements to the remoteproc core. These include an enhancement to handle new vendor resource types supporting custom resource processing both before and after loading, a public rproc_set_firmware() API to be able to configure the firmware name at runtime (reused by sysfs code as well), and a state-machine fix for the sysfs path for the no auto-boot remoteprocs. The RPMsg stack is supported for the PRU remoteproc devices through the usage of PRU system events (instead of OMAP mailboxes). This is done to align on a common interrupt mechanism for PRUSS support on all ICSS instances (AM437x does not have enough mailboxes) on both OMAP architecture (AM33xx/AM43xx/AM57xx) and Keystone architecture (66AK2G) SoCs. The PRU remoteproc will be leveraging the Linux default CMA pools for virtio ring buffers and control data. * rproc-linux-4.19.y: (53 commits) ARM: dts: keystone-k2g: Add PRU system events for virtio ARM: dts: DRA7: Add PRU system events for virtio ARM: dts: AM4372: Add PRU system events for virtio ARM: dts: AM33xx: Add PRU system events for virtio remoteproc/pru: Add support for virtio rpmsg stack dt-bindings: remoteproc: pru: Update bindings for supporting rpmsg ARM: dts: keystone-k2g: Add PRUSS GPIO controller nodes ARM: dts: keystone-k2g: Add PRUSS MDIO controller nodes ARM: dts: keystone-k2g: Add the PRU-ICSS nodes ARM: dts: am57xx-idk-common: Enable PRU-ICSS nodes ARM: dts: beagle-x15-common: Enable PRU-ICSS nodes ARM: DRA7: hwmod_data: Add PRU-ICSS data for AM57xx variants ARM: dts: DRA7: Add PRUSS MDIO controller nodes ARM: dts: DRA7: Add the PRU-ICSS nodes ARM: dts: am437x-idk: Enable PRU-ICSS nodes ARM: dts: am437x-sk: Enable PRU-ICSS nodes ARM: dts: am437x-gp-evm: Enable PRU-ICSS nodes ARM: OMAP2+: extend pruss pdata-quirks to AM437x SoCs ARM: dts: AM4372: Add PRUSS MDIO controller node ARM: dts: AM4372: Add the PRU-ICSS0 DT node ... Signed-off-by: Suman Anna <s-anna@ti.com>