devicetree: remoteproc: r5: use sram_N for fw mems

Sync device tree example with the change in the driver.
Use sram memory for firmware memory.

Signed-off-by: Wendy Liang <jliang@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>

diff --git a/Documentation/devicetree/bindings/remoteproc/r5_remoteproc.txt b/Documentation/devicetree/bindings/remoteproc/r5_remoteproc.txt
index 6b3c847b76a19f23a7dc86c1ba455cee026d9391..be2a5871a6600556a1baba6ac981a9b8a8160805 100644 (file)
--- a/Documentation/devicetree/bindings/remoteproc/r5_remoteproc.txt
+++ b/Documentation/devicetree/bindings/remoteproc/r5_remoteproc.txt
@@ -20,6 +20,7 @@ Required properties:
               ipi, rpu_base and apb_base must be provided
  - interrupts : Interrupt mapping for remoteproc IPI
  - interrupt-parent : Phandle for the interrupt controller
+ - sram_N: firmware memory
 
 Optional properties:
 --------------------
@@ -28,6 +29,19 @@ Optional properties:
 
 Example:
 --------
+       r5_0_tcm_a: tcm@ffe00000 {
+               compatible = "mmio-sram";
+               reg = <0x0 0xFFE00000 0x0 0x20000>;
+       };
+       r5_0_tcm_b: tcm@ffe20000 {
+               compatible = "mmio-sram";
+               reg = <0x0 0xFFE20000 0x0 0x20000>;
+       };
+       elf_ddr_0: ddr@3ed00000 {
+               compatible = "mmio-sram";
+               reg = <0x0 0x3ed00000 0x0 0x40000>;
+       };
+
        zynqmp-r5-remoteproc@0 {
                compatible = "xlnx,zynqmp-r5-remoteproc";
                reg = <0x0 0xff340000 0x0 0x100>,
@@ -35,6 +49,9 @@ Example:
                        <0x0 0xff5e0000 0x0 0x400>;
                reg-names = "ipi", "rpu_base", "apb_base";
                core_conf = "split0";
+               sram_0 = <&r5_0_tcm_a>;
+               sram_1 = <&r5_0_tcm_b>;
+               sram_2 = <&elf_ddr_0>;
                interrupt-parent = <&gic>;
                interrupts = <0 29 4>;
        } ;