Based on kernel version 6.11
. Page generated on 2024-09-24 08:21 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 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) # Copyright (C) 2020 Texas Instruments Incorporated # Author: Peter Ujfalusi <peter.ujfalusi@ti.com> %YAML 1.2 --- $id: http://devicetree.org/schemas/dma/ti/k3-bcdma.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Texas Instruments K3 DMSS BCDMA maintainers: - Peter Ujfalusi <peter.ujfalusi@gmail.com> description: | The Block Copy DMA (BCDMA) is intended to perform similar functions as the TR mode channels of K3 UDMA-P. BCDMA includes block copy channels and Split channels. Block copy channels mainly used for memory to memory transfers, but with optional triggers a block copy channel can service peripherals by accessing directly to memory mapped registers or area. Split channels can be used to service PSI-L based peripherals. The peripherals can be PSI-L native or legacy, non PSI-L native peripherals with PDMAs. PDMA is tasked to act as a bridge between the PSI-L fabric and the legacy peripheral. PDMAs can be configured via BCDMA split channel's peer registers to match with the configuration of the legacy peripheral. properties: compatible: enum: - ti,am62a-dmss-bcdma-csirx - ti,am64-dmss-bcdma - ti,j721s2-dmss-bcdma-csi reg: minItems: 3 maxItems: 9 reg-names: minItems: 3 maxItems: 9 "#dma-cells": const: 3 description: | cell 1: type of the BCDMA channel to be used to service the peripheral: 0 - split channel 1 - block copy channel using global trigger 1 2 - block copy channel using global trigger 2 3 - block copy channel using local trigger cell 2: parameter for the channel: if cell 1 is 0 (split channel): PSI-L thread ID of the remote (to BCDMA) end. Valid ranges for thread ID depends on the data movement direction: for source thread IDs (rx): 0 - 0x7fff for destination thread IDs (tx): 0x8000 - 0xffff Please refer to the device documentation for the PSI-L thread map and also the PSI-L peripheral chapter for the correct thread ID. if cell 1 is 1 or 2 (block copy channel using global trigger): Unused, ignored The trigger must be configured for the channel externally to BCDMA, channels using global triggers should not be requested directly, but via DMA event router. if cell 1 is 3 (block copy channel using local trigger): bchan number of the locally triggered channel cell 3: ASEL value for the channel msi-parent: true power-domains: description: Power domain if available maxItems: 1 ti,asel: $ref: /schemas/types.yaml#/definitions/uint32 description: ASEL value for non slave channels ti,sci-rm-range-bchan: $ref: /schemas/types.yaml#/definitions/uint32-array description: | Array of BCDMA block-copy channel resource subtypes for resource allocation for this host minItems: 1 # Should be enough maxItems: 255 items: maximum: 0x3f ti,sci-rm-range-tchan: $ref: /schemas/types.yaml#/definitions/uint32-array description: | Array of BCDMA split tx channel resource subtypes for resource allocation for this host minItems: 1 # Should be enough maxItems: 255 items: maximum: 0x3f ti,sci-rm-range-rchan: $ref: /schemas/types.yaml#/definitions/uint32-array description: | Array of BCDMA split rx channel resource subtypes for resource allocation for this host minItems: 1 # Should be enough maxItems: 255 items: maximum: 0x3f required: - compatible - "#dma-cells" - reg - reg-names - msi-parent - ti,sci - ti,sci-dev-id - ti,sci-rm-range-rchan allOf: - $ref: /schemas/dma/dma-controller.yaml# - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# - if: properties: compatible: contains: const: ti,am62a-dmss-bcdma-csirx then: properties: ti,sci-rm-range-bchan: false ti,sci-rm-range-tchan: false reg: items: - description: BCDMA Control /Status Registers region - description: RX Channel Realtime Registers region - description: Ring Realtime Registers region reg-names: items: - const: gcfg - const: rchanrt - const: ringrt required: - power-domains - if: properties: compatible: contains: const: ti,am64-dmss-bcdma then: properties: reg: minItems: 5 items: - description: BCDMA Control /Status Registers region - description: Block Copy Channel Realtime Registers region - description: RX Channel Realtime Registers region - description: TX Channel Realtime Registers region - description: Ring Realtime Registers region - description: Ring Configuration Registers region - description: TX Channel Configuration Registers region - description: RX Channel Configuration Registers region - description: Block Copy Channel Configuration Registers region reg-names: minItems: 5 items: - const: gcfg - const: bchanrt - const: rchanrt - const: tchanrt - const: ringrt - const: ring - const: tchan - const: rchan - const: bchan required: - ti,sci-rm-range-bchan - ti,sci-rm-range-tchan - if: properties: compatible: contains: const: ti,j721s2-dmss-bcdma-csi then: properties: ti,sci-rm-range-bchan: false reg: items: - description: BCDMA Control /Status Registers region - description: RX Channel Realtime Registers region - description: TX Channel Realtime Registers region - description: Ring Realtime Registers region reg-names: items: - const: gcfg - const: rchanrt - const: tchanrt - const: ringrt required: - ti,sci-rm-range-tchan unevaluatedProperties: false examples: - |+ cbass_main { #address-cells = <2>; #size-cells = <2>; main_dmss { compatible = "simple-mfd"; #address-cells = <2>; #size-cells = <2>; dma-ranges; ranges; ti,sci-dev-id = <25>; main_bcdma: dma-controller@485c0100 { compatible = "ti,am64-dmss-bcdma"; reg = <0x0 0x485c0100 0x0 0x100>, <0x0 0x4c000000 0x0 0x20000>, <0x0 0x4a820000 0x0 0x20000>, <0x0 0x4aa40000 0x0 0x20000>, <0x0 0x4bc00000 0x0 0x100000>, <0x0 0x48600000 0x0 0x8000>, <0x0 0x484a4000 0x0 0x2000>, <0x0 0x484c2000 0x0 0x2000>, <0x0 0x48420000 0x0 0x2000>; reg-names = "gcfg", "bchanrt", "rchanrt", "tchanrt", "ringrt", "ring", "tchan", "rchan", "bchan"; msi-parent = <&inta_main_dmss>; #dma-cells = <3>; ti,sci = <&dmsc>; ti,sci-dev-id = <26>; ti,sci-rm-range-bchan = <0x20>; /* BLOCK_COPY_CHAN */ ti,sci-rm-range-rchan = <0x21>; /* SPLIT_TR_RX_CHAN */ ti,sci-rm-range-tchan = <0x22>; /* SPLIT_TR_TX_CHAN */ }; }; }; |