Home
last modified time | relevance | path

Searched full:r5fss (Results 1 – 15 of 15) sorted by relevance

/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,k3-r5f-rproc.yaml14 processor subsystems/clusters (R5FSS). The dual core cluster can be used
36 pattern: "^r5fss(@.*)?"
40 - ti,am62-r5fss
41 - ti,am64-r5fss
42 - ti,am654-r5fss
43 - ti,j7200-r5fss
44 - ti,j721e-r5fss
45 - ti,j721s2-r5fss
50 specifier containing the R5FSS device id value.
230 - ti,am64-r5fss
[all …]
H A Dxlnx,zynqmp-r5fss.yaml4 $id: http://devicetree.org/schemas/remoteproc/xlnx,zynqmp-r5fss.yaml#
21 const: xlnx,zynqmp-r5fss
116 compatible = "xlnx,zynqmp-r5fss";
/openbmc/linux/drivers/remoteproc/
H A Dti_k3_r5_remoteproc.c107 * @soc_data: SoC-specific feature data for a R5FSS
804 * Each R5FSS has a cluster-level setting for configuring the processor
1062 * Each R5F core within a typical R5FSS instance has a total of 64 KB of TCMs,
1065 * LockStep-mode. The newer revisions of the R5FSS IP maximizes these TCMs by
1855 { .compatible = "ti,am654-r5fss", .data = &am65_j721e_soc_data, },
1856 { .compatible = "ti,j721e-r5fss", .data = &am65_j721e_soc_data, },
1857 { .compatible = "ti,j7200-r5fss", .data = &j7200_j721s2_soc_data, },
1858 { .compatible = "ti,am64-r5fss", .data = &am64_soc_data, },
1859 { .compatible = "ti,am62-r5fss", .data = &am62_soc_data, },
1860 { .compatible = "ti,j721s2-r5fss", .data = &j7200_j721s2_soc_data, },
H A Dxlnx_r5_remoteproc.c1217 { .compatible = "xlnx,zynqmp-r5fss", },
/openbmc/linux/arch/arm64/boot/dts/ti/
H A Dk3-am64.dtsi79 <0x00 0x78000000 0x00 0x78000000 0x00 0x00800000>, /* Main R5FSS */
H A Dk3-am65-mcu.dtsi392 mcu_r5fss0: r5fss@41000000 {
393 compatible = "ti,am654-r5fss";
H A Dk3-j784s4-main.dtsi1400 main_r5fss0: r5fss@5c00000 {
1401 compatible = "ti,j721s2-r5fss";
1440 main_r5fss1: r5fss@5e00000 {
1441 compatible = "ti,j721s2-r5fss";
1480 main_r5fss2: r5fss@5900000 {
1481 compatible = "ti,j721s2-r5fss";
H A Dk3-j7200-mcu-wakeup.dtsi574 mcu_r5fss0: r5fss@41000000 {
575 compatible = "ti,j7200-r5fss";
H A Dk3-j784s4-mcu-wakeup.dtsi575 mcu_r5fss0: r5fss@41000000 {
576 compatible = "ti,j721s2-r5fss";
H A Dk3-j721e-mcu-wakeup.dtsi563 mcu_r5fss0: r5fss@41000000 {
564 compatible = "ti,j721e-r5fss";
H A Dk3-am64-main.dtsi881 main_r5fss0: r5fss@78000000 {
882 compatible = "ti,am64-r5fss";
923 main_r5fss1: r5fss@78400000 {
924 compatible = "ti,am64-r5fss";
H A Dk3-j721e-main.dtsi2033 main_r5fss0: r5fss@5c00000 {
2034 compatible = "ti,j721e-r5fss";
2073 main_r5fss1: r5fss@5e00000 {
2074 compatible = "ti,j721e-r5fss";
H A Dk3-j7200-main.dtsi1257 main_r5fss0: r5fss@5c00000 {
1258 compatible = "ti,j7200-r5fss";
/openbmc/linux/arch/arm64/boot/dts/xilinx/
H A Dzynqmp.dtsi251 compatible = "xlnx,zynqmp-r5fss";
/openbmc/linux/
H A Dopengrok0.0.log[all...]