Searched full:btcm (Results 1 – 2 of 2) sorted by relevance
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 80 ATCM and BTCM) provide read/write performance on par with the core's L1
102 - description: Address and Size of the BTCM internal memory region
107 - const: btcm
160 ti,btcm-enable:
164 R5F core configuration mode dictating if BTCM should be enabled. The
165 R5F address of BTCM is dictated by ti,loczrama property. Should be
175 at 0x0) or 0 (BTCM at 0x0), default value is 1 if omitted.
248 reg-names = "atcm", "btcm";
255 ti,btcm-enable = <1>;
267 reg-names = "atcm", "btcm";
[all …]
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 29 /* This address can either be for ATCM or BTCM with the other at address 0x0 */
96 * @btcm_enable: flag to control BTCM enablement
377 * affected by ATCM & BTCM enable configuration values) so that ECC in k3_r5_rproc_prepare()
383 dev_dbg(dev, "zeroing out BTCM memory\n"); in k3_r5_rproc_prepare()
573 /* handle both R5 and SoC views of ATCM and BTCM */ in k3_r5_rproc_da_to_va()
977 static const char * const mem_names[] = {"atcm", "btcm"}; in k3_r5_core_of_get_internal_memories()
1021 * The R5F cores can place ATCM & BTCM anywhere in its address in k3_r5_core_of_get_internal_memories()
1023 * Control coprocessor. For now, place ATCM and BTCM at in k3_r5_core_of_get_internal_memories()
1161 ret = of_property_read_u32(np, "ti,btcm-enable", &core->btcm_enable); in k3_r5_core_of_init()
1163 dev_err(dev, "invalid format for ti,btcm-enable, ret = %d\n", in k3_r5_core_of_init()
|