Home
last modified time | relevance | path

Searched full:btcm (Results 1 – 14 of 14) sorted by relevance

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml80 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-6.6/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml101 ATCM and BTCM) provide read/write performance on par with the core's L1
126 - description: Address and Size of the BTCM internal memory region
131 - const: btcm
184 ti,btcm-enable:
188 R5F core configuration mode dictating if BTCM should be enabled. The
189 R5F address of BTCM is dictated by ti,loczrama property. Should be
199 at 0x0) or 0 (BTCM at 0x0), default value is 1 if omitted.
314 reg-names = "atcm", "btcm";
321 ti,btcm-enable = <1>;
333 reg-names = "atcm", "btcm";
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/ti/
Dk3-am62a.dtsi85 <0x00 0x79020000 0x00 0x79020000 0x00 0x00008000>, /* MCU R5 BTCM */
94 <0x00 0x78100000 0x00 0x78100000 0x00 0x00008000>; /* DM R5 BTCM */
102 <0x00 0x79020000 0x00 0x79020000 0x00 0x00008000>, /* MCU R5 BTCM */
115 <0x00 0x78100000 0x00 0x78100000 0x00 0x00008000>; /* DM R5 BTCM*/
Dk3-am65-mcu.dtsi405 reg-names = "atcm", "btcm";
412 ti,btcm-enable = <1>;
420 reg-names = "atcm", "btcm";
427 ti,btcm-enable = <1>;
Dk3-am62p.dtsi100 <0x00 0x79020000 0x00 0x79020000 0x00 0x00008000>, /* MCU R5 BTCM */
114 <0x00 0x78100000 0x00 0x78100000 0x00 0x00008000>; /* DM R5 BTCM*/
Dk3-j784s4-main.dtsi1413 reg-names = "atcm", "btcm";
1420 ti,btcm-enable = <1>;
1428 reg-names = "atcm", "btcm";
1435 ti,btcm-enable = <1>;
1453 reg-names = "atcm", "btcm";
1460 ti,btcm-enable = <1>;
1468 reg-names = "atcm", "btcm";
1475 ti,btcm-enable = <1>;
1493 reg-names = "atcm", "btcm";
1500 ti,btcm-enable = <1>;
[all …]
Dk3-j7200-mcu-wakeup.dtsi587 reg-names = "atcm", "btcm";
594 ti,btcm-enable = <1>;
602 reg-names = "atcm", "btcm";
609 ti,btcm-enable = <1>;
Dk3-j721e-mcu-wakeup.dtsi576 reg-names = "atcm", "btcm";
583 ti,btcm-enable = <1>;
591 reg-names = "atcm", "btcm";
598 ti,btcm-enable = <1>;
Dk3-j784s4-mcu-wakeup.dtsi588 reg-names = "atcm", "btcm";
595 ti,btcm-enable = <1>;
603 reg-names = "atcm", "btcm";
610 ti,btcm-enable = <1>;
Dk3-am64-main.dtsi896 reg-names = "atcm", "btcm";
903 ti,btcm-enable = <1>;
911 reg-names = "atcm", "btcm";
918 ti,btcm-enable = <1>;
938 reg-names = "atcm", "btcm";
945 ti,btcm-enable = <1>;
953 reg-names = "atcm", "btcm";
960 ti,btcm-enable = <1>;
Dk3-j721e-main.dtsi2046 reg-names = "atcm", "btcm";
2053 ti,btcm-enable = <1>;
2061 reg-names = "atcm", "btcm";
2068 ti,btcm-enable = <1>;
2086 reg-names = "atcm", "btcm";
2093 ti,btcm-enable = <1>;
2101 reg-names = "atcm", "btcm";
2108 ti,btcm-enable = <1>;
Dk3-j7200-main.dtsi1270 reg-names = "atcm", "btcm";
1277 ti,btcm-enable = <1>;
1285 reg-names = "atcm", "btcm";
1292 ti,btcm-enable = <1>;
/kernel/linux/linux-5.10/drivers/remoteproc/
Dti_k3_r5_remoteproc.c29 /* 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()
/kernel/linux/linux-6.6/drivers/remoteproc/
Dti_k3_r5_remoteproc.c30 /* This address can either be for ATCM or BTCM with the other at address 0x0 */
131 * @btcm_enable: flag to control BTCM enablement
478 * affected by ATCM & BTCM enable configuration values) so that ECC in k3_r5_rproc_prepare()
484 dev_dbg(dev, "zeroing out BTCM memory\n"); in k3_r5_rproc_prepare()
736 /* handle both R5 and SoC views of ATCM and BTCM */ in k3_r5_rproc_da_to_va()
1055 * split equally into two 32 KB banks between ATCM and BTCM. The TCMs from both
1087 dev_dbg(cdev, "adjusted TCM sizes, ATCM = 0x%zx BTCM = 0x%zx\n", in k3_r5_adjust_tcm_sizes()
1100 * In IPC-only mode, the driver state flags for ATCM, BTCM and LOCZRAMA settings
1385 static const char * const mem_names[] = {"atcm", "btcm"}; in k3_r5_core_of_get_internal_memories()
1429 * The R5F cores can place ATCM & BTCM anywhere in its address in k3_r5_core_of_get_internal_memories()
[all …]