Add names to the memory-region-names for easier identification of memory regions.
Signed-off-by: Markus Schneider-Pargmann (TI) <[email protected]> --- .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml index 15e0286e4926865d88b693998e5aa64543ae125d..3f2425e0880f9a516ac10700a218ed035ff07d5a 100644 --- a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml +++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml @@ -175,6 +175,24 @@ patternProperties: - description: LPM FS context data and reserved sections - description: DM RM/PM trace and firmware code/data + memory-region-names: + description: | + Names for the memory regions specified in the memory-region property. + The names must correspond with the entries in memory-region. + oneOf: + - description: Basic layout + items: + - const: dma + - const: firmware + - description: Detailed layout + items: + - const: dma + - const: ipc + - const: lpm-stub + - const: lpm-metadata + - const: lpm-context + - const: dm-firmware + # Optional properties: # -------------------- # The following properties are optional properties for each of the R5F cores: @@ -330,6 +348,7 @@ examples: mboxes = <&mailbox0 &mbox_mcu_r5fss0_core0>; memory-region = <&mcu_r5fss0_core0_dma_memory_region>, <&mcu_r5fss0_core0_memory_region>; + memory-region-names = "dma", "firmware"; sram = <&mcu_r5fss0_core0_sram>; }; -- 2.53.0
