Searched full:r5f (Results 1 – 25 of 25) sorted by relevance
/Linux-v6.1/Documentation/devicetree/bindings/remoteproc/ |
D | ti,k3-r5f-rproc.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-rproc.yaml# 7 title: TI K3 R5F processor subsystems 13 The TI K3 family of SoCs usually have one or more dual-core Arm Cortex R5F 24 Each Dual-Core R5F sub-system is represented as a single DTS node 26 the individual R5F cores. Each node has a number of required or optional 58 local R5F TCM address spaces to bus addresses. 66 Configuration Mode for the Dual R5F cores within the R5F cluster. 72 # R5F Processor Child Nodes: 76 "^r5f@[a-f0-9]+$": 79 The R5F Sub-System device node should define two R5F child nodes, each [all …]
|
/Linux-v6.1/arch/arm64/boot/dts/ti/ |
D | k3-j721e-som-p0.dtsi | 29 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 35 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 { 41 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 47 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 { 53 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 { 59 main_r5fss0_core0_memory_region: r5f-memory@a2100000 { 65 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 { 71 main_r5fss0_core1_memory_region: r5f-memory@a3100000 { 77 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 { 83 main_r5fss1_core0_memory_region: r5f-memory@a4100000 { [all …]
|
D | k3-j7200-som-p0.dtsi | 29 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 35 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 { 41 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 47 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 { 53 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 { 59 main_r5fss0_core0_memory_region: r5f-memory@a2100000 { 65 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 { 71 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
|
D | k3-j721e-sk.dts | 42 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 48 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 { 54 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 60 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 { 66 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 { 72 main_r5fss0_core0_memory_region: r5f-memory@a2100000 { 78 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 { 84 main_r5fss0_core1_memory_region: r5f-memory@a3100000 { 90 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 { 96 main_r5fss1_core0_memory_region: r5f-memory@a4100000 { [all …]
|
D | k3-am642-evm.dts | 42 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 48 main_r5fss0_core0_memory_region: r5f-memory@a0100000 { 54 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 60 main_r5fss0_core1_memory_region: r5f-memory@a1100000 { 66 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 { 72 main_r5fss1_core0_memory_region: r5f-memory@a2100000 { 78 main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 { 84 main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
|
D | k3-am642-sk.dts | 42 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 48 main_r5fss0_core0_memory_region: r5f-memory@a0100000 { 54 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 60 main_r5fss0_core1_memory_region: r5f-memory@a1100000 { 66 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 { 72 main_r5fss1_core0_memory_region: r5f-memory@a2100000 { 78 main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 { 84 main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
|
D | k3-am65-mcu.dtsi | 309 mcu_r5fss0_core0: r5f@41000000 { 310 compatible = "ti,am654-r5f"; 324 mcu_r5fss0_core1: r5f@41400000 { 325 compatible = "ti,am654-r5f";
|
D | k3-j7200-mcu-wakeup.dtsi | 348 mcu_r5fss0_core0: r5f@41000000 { 349 compatible = "ti,j7200-r5f"; 363 mcu_r5fss0_core1: r5f@41400000 { 364 compatible = "ti,j7200-r5f";
|
D | k3-am654-base-board.dts | 39 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 45 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 { 51 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 57 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
|
D | k3-j721e-mcu-wakeup.dtsi | 363 mcu_r5fss0_core0: r5f@41000000 { 364 compatible = "ti,j721e-r5f"; 378 mcu_r5fss0_core1: r5f@41400000 { 379 compatible = "ti,j721e-r5f";
|
D | k3-am65.dtsi | 101 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */ 102 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
|
D | k3-j7200.dtsi | 159 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */ 160 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
|
D | k3-j721s2.dtsi | 150 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */ 151 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
|
D | k3-am65-iot2050-common.dtsi | 38 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 { 44 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 { 50 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 { 56 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
|
D | k3-j721e.dtsi | 172 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */ 173 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
|
D | k3-am64-main.dtsi | 723 main_r5fss0_core0: r5f@78000000 { 724 compatible = "ti,am64-r5f"; 738 main_r5fss0_core1: r5f@78200000 { 739 compatible = "ti,am64-r5f"; 765 main_r5fss1_core0: r5f@78400000 { 766 compatible = "ti,am64-r5f"; 780 main_r5fss1_core1: r5f@78600000 { 781 compatible = "ti,am64-r5f";
|
D | k3-j7200-main.dtsi | 778 main_r5fss0_core0: r5f@5c00000 { 779 compatible = "ti,j7200-r5f"; 793 main_r5fss0_core1: r5f@5d00000 { 794 compatible = "ti,j7200-r5f";
|
D | k3-j721e-main.dtsi | 1627 main_r5fss0_core0: r5f@5c00000 { 1628 compatible = "ti,j721e-r5f"; 1642 main_r5fss0_core1: r5f@5d00000 { 1643 compatible = "ti,j721e-r5f"; 1667 main_r5fss1_core0: r5f@5e00000 { 1668 compatible = "ti,j721e-r5f"; 1682 main_r5fss1_core1: r5f@5f00000 { 1683 compatible = "ti,j721e-r5f";
|
D | k3-am62a7-sk.dts | 50 wkup_r5fss0_core0_memory_region: r5f-dma-memory@9c900000 {
|
D | k3-j7200-common-proc-board.dts | 163 /* MAIN UART 2 is used by R5F firmware */
|
D | k3-am625-sk.dts | 67 wkup_r5fss0_core0_dma_memory_region: r5f-dma-memory@9db00000 {
|
/Linux-v6.1/drivers/remoteproc/ |
D | ti_k3_r5_remoteproc.c | 3 * TI K3 R5F (MCU) Remote Processor driver 97 * struct k3_r5_cluster - K3 R5F Cluster structure 196 dev_err(dev, "K3 R5F rproc %s crashed\n", name); in k3_r5_rproc_mbox_callback() 418 * The R5F cores have controls for both a reset and a halt/run. The code 488 * or Split mode). This completes the second portion of powering down the R5F 519 * The R5F start sequence includes two different operations 520 * 1. Configure the boot vector for R5F core(s) 521 * 2. Unhalt/Run the R5F core(s) 550 dev_dbg(dev, "booting R5F core using boot addr = 0x%x\n", boot_addr); in k3_r5_rproc_start() 584 * The R5F stop function includes the following operations [all …]
|
D | Kconfig | 348 Say m here to support TI's R5F remote processor subsystems
|
/Linux-v6.1/sound/soc/bcm/ |
D | cygnus-pcm.c | 159 /* Mask for R5F register. Set all relevant interrupt for playback handler */ 164 /* Mask for R5F register. Set all relevant interrupt for capture handler */
|
/Linux-v6.1/sound/soc/codecs/ |
D | cs42l73.c | 136 { 95, 0x00 }, /* r5F - Interrupt Mask 2 */
|