Home
last modified time | relevance | path

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

/Linux-v6.1/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml14 processor subsystems/clusters (R5FSS). The dual core cluster can be used
33 pattern: "^r5fss(@.*)?"
37 - ti,am654-r5fss
38 - ti,j721e-r5fss
39 - ti,j7200-r5fss
40 - ti,am64-r5fss
41 - ti,j721s2-r5fss
46 specifier containing the R5FSS device id value.
215 - ti,am64-r5fss
266 /* AM65x MCU R5FSS node */
[all …]
/Linux-v6.1/drivers/remoteproc/
Dti_k3_r5_remoteproc.c101 * @soc_data: SoC-specific feature data for a R5FSS
795 * Each R5FSS has a cluster-level setting for configuring the processor
1056 * Each R5F core within a typical R5FSS instance has a total of 64 KB of TCMs,
1059 * LockStep-mode. The newer revisions of the R5FSS IP maximizes these TCMs by
1778 { .compatible = "ti,am654-r5fss", .data = &am65_j721e_soc_data, },
1779 { .compatible = "ti,j721e-r5fss", .data = &am65_j721e_soc_data, },
1780 { .compatible = "ti,j7200-r5fss", .data = &j7200_j721s2_soc_data, },
1781 { .compatible = "ti,am64-r5fss", .data = &am64_soc_data, },
1782 { .compatible = "ti,j721s2-r5fss", .data = &j7200_j721s2_soc_data, },
/Linux-v6.1/arch/arm64/boot/dts/ti/
Dk3-am65-mcu.dtsi300 mcu_r5fss0: r5fss@41000000 {
301 compatible = "ti,am654-r5fss";
Dk3-j7200-mcu-wakeup.dtsi339 mcu_r5fss0: r5fss@41000000 {
340 compatible = "ti,j7200-r5fss";
Dk3-am64.dtsi93 <0x00 0x78000000 0x00 0x78000000 0x00 0x00800000>, /* Main R5FSS */
Dk3-j721e-mcu-wakeup.dtsi354 mcu_r5fss0: r5fss@41000000 {
355 compatible = "ti,j721e-r5fss";
Dk3-am64-main.dtsi712 main_r5fss0: r5fss@78000000 {
713 compatible = "ti,am64-r5fss";
754 main_r5fss1: r5fss@78400000 {
755 compatible = "ti,am64-r5fss";
Dk3-j7200-main.dtsi769 main_r5fss0: r5fss@5c00000 {
770 compatible = "ti,j7200-r5fss";
Dk3-j721e-main.dtsi1618 main_r5fss0: r5fss@5c00000 {
1619 compatible = "ti,j721e-r5fss";
1658 main_r5fss1: r5fss@5e00000 {
1659 compatible = "ti,j721e-r5fss";