Based on kernel version 6.12.4
. Page generated on 2024-12-12 21:01 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/remoteproc/ti,k3-m4f-rproc.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: TI K3 M4F processor subsystems maintainers: - Hari Nagalla <hnagalla@ti.com> - Mathieu Poirier <mathieu.poirier@linaro.org> description: | Some K3 family SoCs have Arm Cortex M4F cores. AM64x is a SoC in K3 family with a M4F core. Typically safety oriented applications may use the M4F core in isolation without an IPC. Where as some industrial and home automation applications, may use the M4F core as a remote processor with IPC communications. $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# properties: compatible: enum: - ti,am64-m4fss power-domains: maxItems: 1 "#address-cells": const: 2 "#size-cells": const: 2 reg: items: - description: IRAM internal memory region - description: DRAM internal memory region reg-names: items: - const: iram - const: dram resets: maxItems: 1 firmware-name: maxItems: 1 description: Name of firmware to load for the M4F core mboxes: description: OMAP Mailbox specifier denoting the sub-mailbox, to be used for communication with the remote processor. This property should match with the sub-mailbox node used in the firmware image. maxItems: 1 memory-region: description: phandle to the reserved memory nodes to be associated with the remoteproc device. Optional memory regions available for firmware specific purposes. (see reserved-memory/reserved-memory.yaml in dtschema project) maxItems: 8 items: - description: regions used for DMA allocations like vrings, vring buffers and memory dedicated to firmware's specific purposes. additionalItems: true required: - compatible - reg - reg-names - ti,sci - ti,sci-dev-id - ti,sci-proc-ids - resets - firmware-name unevaluatedProperties: false examples: - | reserved-memory { #address-cells = <2>; #size-cells = <2>; mcu_m4fss_dma_memory_region: m4f-dma-memory@9cb00000 { compatible = "shared-dma-pool"; reg = <0x00 0x9cb00000 0x00 0x100000>; no-map; }; mcu_m4fss_memory_region: m4f-memory@9cc00000 { compatible = "shared-dma-pool"; reg = <0x00 0x9cc00000 0x00 0xe00000>; no-map; }; }; soc { #address-cells = <2>; #size-cells = <2>; mailbox0_cluster0: mailbox-0 { #mbox-cells = <1>; }; remoteproc@5000000 { compatible = "ti,am64-m4fss"; reg = <0x00 0x5000000 0x00 0x30000>, <0x00 0x5040000 0x00 0x10000>; reg-names = "iram", "dram"; resets = <&k3_reset 9 1>; firmware-name = "am62-mcu-m4f0_0-fw"; mboxes = <&mailbox0_cluster0>, <&mbox_m4_0>; memory-region = <&mcu_m4fss_dma_memory_region>, <&mcu_m4fss_memory_region>; ti,sci = <&dmsc>; ti,sci-dev-id = <9>; ti,sci-proc-ids = <0x18 0xff>; }; }; |