Home
last modified time | relevance | path

Searched full:r5f (Results 1 – 25 of 48) sorted by relevance

12

/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,k3-r5f-rproc.yaml4 $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 AM62 SoC family support a single R5F core only which runs Device Manager
27 Each Dual-Core R5F sub-system is represented as a single DTS node
29 the individual R5F cores. Each node has a number of required or optional
62 local R5F TCM address spaces to bus addresses.
70 Configuration Mode for the Dual R5F cores within the R5F cluster.
83 # R5F Processor Child Nodes:
87 "^r5f@[a-f0-9]+$":
[all …]
H A Dxlnx,zynqmp-r5fss.yaml7 title: Xilinx R5F processor subsystem
14 The Xilinx platforms include a pair of Cortex-R5F processors (RPU) for
15 real-time processing based on the Cortex-R5F processor core from ARM.
16 The Cortex-R5F processor implements the Arm v7-R architecture and includes a
40 "^r5f-[a-f0-9]+$":
55 const: xlnx,zynqmp-r5f
119 r5f-0 {
120 compatible = "xlnx,zynqmp-r5f";
127 r5f-1 {
128 compatible = "xlnx,zynqmp-r5f";
/openbmc/linux/arch/arm64/boot/dts/ti/
H A Dk3-j721e-som-p0.dtsi31 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
37 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
43 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
49 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
55 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 {
61 main_r5fss0_core0_memory_region: r5f-memory@a2100000 {
67 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 {
73 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
79 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 {
85 main_r5fss1_core0_memory_region: r5f-memory@a4100000 {
[all …]
H A Dk3-am642-tqma64xxl.dtsi34 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
40 main_r5fss0_core0_memory_region: r5f-memory@a0100000 {
46 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
52 main_r5fss0_core1_memory_region: r5f-memory@a1100000 {
58 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 {
64 main_r5fss1_core0_memory_region: r5f-memory@a2100000 {
70 main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 {
76 main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
H A Dk3-j7200-som-p0.dtsi29 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 {
H A Dk3-j784s4-evm.dts49 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
55 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
61 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
67 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
73 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 {
79 main_r5fss0_core0_memory_region: r5f-memory@a2100000 {
85 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 {
91 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
97 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 {
103 main_r5fss1_core0_memory_region: r5f-memory@a4100000 {
[all …]
H A Dk3-j721e-beagleboneai64.dts54 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
60 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
66 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
72 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
78 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 {
84 main_r5fss0_core0_memory_region: r5f-memory@a2100000 {
90 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 {
96 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
102 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 {
108 main_r5fss1_core0_memory_region: r5f-memory@a4100000 {
[all …]
H A Dk3-am642-sk.dts54 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
60 main_r5fss0_core0_memory_region: r5f-memory@a0100000 {
66 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
72 main_r5fss0_core1_memory_region: r5f-memory@a1100000 {
78 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 {
84 main_r5fss1_core0_memory_region: r5f-memory@a2100000 {
90 main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 {
96 main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
H A Dk3-am642-evm.dts55 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
61 main_r5fss0_core0_memory_region: r5f-memory@a0100000 {
67 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
73 main_r5fss0_core1_memory_region: r5f-memory@a1100000 {
79 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 {
85 main_r5fss1_core0_memory_region: r5f-memory@a2100000 {
91 main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 {
97 main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
H A Dk3-j721e-sk.dts50 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
56 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
62 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
68 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
74 main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a2000000 {
80 main_r5fss0_core0_memory_region: r5f-memory@a2100000 {
86 main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a3000000 {
92 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
98 main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a4000000 {
104 main_r5fss1_core0_memory_region: r5f-memory@a4100000 {
[all …]
H A Dk3-j721e-thermal.dtsi62 r5f_thermal: r5f-thermal {
68 r5f_crit: r5f-crit {
H A Dk3-am65.dtsi85 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */
86 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
H A Dk3-am65-mcu.dtsi401 mcu_r5fss0_core0: r5f@41000000 {
402 compatible = "ti,am654-r5f";
416 mcu_r5fss0_core1: r5f@41400000 {
417 compatible = "ti,am654-r5f";
H A Dk3-j784s4-main.dtsi1409 main_r5fss0_core0: r5f@5c00000 {
1410 compatible = "ti,j721s2-r5f";
1424 main_r5fss0_core1: r5f@5d00000 {
1425 compatible = "ti,j721s2-r5f";
1449 main_r5fss1_core0: r5f@5e00000 {
1450 compatible = "ti,j721s2-r5f";
1464 main_r5fss1_core1: r5f@5f00000 {
1465 compatible = "ti,j721s2-r5f";
1489 main_r5fss2_core0: r5f@5900000 {
1490 compatible = "ti,j721s2-r5f";
[all …]
H A Dk3-j7200.dtsi146 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */
147 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
H A Dk3-j721s2.dtsi153 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */
154 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
H A Dk3-am654-base-board.dts52 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
58 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
64 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
70 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
H A Dk3-j721e.dtsi158 <0x00 0x41000000 0x00 0x41000000 0x00 0x00020000>, /* MCU R5F Core0 */
159 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
H A Dk3-am65-iot2050-common.dtsi47 mcu_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
53 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
59 mcu_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
65 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
H A Dk3-j7200-mcu-wakeup.dtsi583 mcu_r5fss0_core0: r5f@41000000 {
584 compatible = "ti,j7200-r5f";
598 mcu_r5fss0_core1: r5f@41400000 {
599 compatible = "ti,j7200-r5f";
H A Dk3-j784s4-mcu-wakeup.dtsi584 mcu_r5fss0_core0: r5f@41000000 {
585 compatible = "ti,j721s2-r5f";
599 mcu_r5fss0_core1: r5f@41400000 {
600 compatible = "ti,j721s2-r5f";
/openbmc/linux/drivers/remoteproc/
H A Dti_k3_r5_remoteproc.c3 * TI K3 R5F (MCU) Remote Processor driver
102 * struct k3_r5_cluster - K3 R5F Cluster structure
209 dev_err(dev, "K3 R5F rproc %s crashed\n", name); in k3_r5_rproc_mbox_callback()
432 * The R5F cores have controls for both a reset and a halt/run. The code
502 * or Split mode). This completes the second portion of powering down the R5F
533 * The R5F start sequence includes two different operations
534 * 1. Configure the boot vector for R5F core(s)
535 * 2. Unhalt/Run the R5F core(s)
560 dev_dbg(dev, "booting R5F core using boot addr = 0x%x\n", boot_addr); in k3_r5_rproc_start()
604 * The R5F stop function includes the following operations
[all …]
H A Dxlnx_r5_remoteproc.c109 * @dev: r5f subsystem cluster device node
350 * and jitter. Also, if the OCM is secured and the Cortex-R5F processor in zynqmp_r5_rproc_start()
351 * is non-secured, then the Cortex-R5F processor cannot access the in zynqmp_r5_rproc_start()
834 * Allocate and add struct rproc object for each r5f core
835 * This is called for each individual r5f core
1036 * r5f subsystem node in dts. If Split mode is used in dts in zynqmp_r5_cluster_init()
1204 dev_err_probe(dev, ret, "Invalid r5f subsystem device tree\n"); in zynqmp_r5_remoteproc_probe()
1231 MODULE_DESCRIPTION("Xilinx R5F remote processor driver");
H A DKconfig348 Say m here to support TI's R5F remote processor subsystems
366 It's safe to say N if not interested in using RPU r5f cores.
/openbmc/qemu/docs/system/arm/
H A Dxlnx-zcu102.rst5 This board has 4 Cortex-A53 CPUs and 2 Cortex-R5F CPUs.

12