drivers/remoteproc/ti_k3_r5_remoteproc.c

76  *   LockStep mode    : AM65x, J721E and J7200 SoCs
104  * @mode: Mode to configure the Cluster - Split or LockStep
443  * cluster in this mode. The function uses the same reset logic as LockStep
463 	/* Re-use LockStep-mode reset logic for Single-CPU mode */  in k3_r5_rproc_prepare()
501  * resets on all applicable cores for the rproc device (depending on LockStep
510  * reset assert logic as LockStep mode for this mode (though the behavior is
522 	/* Re-use LockStep-mode reset logic for Single-CPU mode */  in k3_r5_rproc_unprepare()
537  * The sequence is different between LockStep and Split modes. The LockStep
562 	/* boot vector need not be programmed for Core1 in LockStep mode */  in k3_r5_rproc_start()
607  * The sequence is different between LockStep and Split modes, and the order
609  * of the start function. The LockStep mode requires each operation to be
805  * subsystem either in a safety/fault-tolerant LockStep mode or a performance
807  * as an alternate for LockStep mode that exercises only a single R5F core
820  * once (in LockStep mode or Single-CPU modes) or twice (in Split mode). Support
821  * for LockStep-mode is dictated by an eFUSE register bit, and the config
830  * They are identically configured in LockStep mode using the primary Core0
831  * settings. However, some individual settings cannot be set in LockStep mode.
834  * LockStep mode.
874 	/* Override to split mode if lockstep enable bit is not set in status flag */  in k3_r5_rproc_configure()
876 		dev_err(cluster->dev, "lockstep mode not permitted, force configuring for split-mode\n");  in k3_r5_rproc_configure()
895 			 * LockStep configuration bit is Read-only on Split-mode  in k3_r5_rproc_configure()
923 		 * cores are programmed symmetrically in LockStep. LockStep  in k3_r5_rproc_configure()
1065  * LockStep-mode. The newer revisions of the R5FSS IP maximizes these TCMs by
1067  * otherwise been unusable (Eg: LockStep-mode on J7200 SoCs, Single-CPU mode on
1290 		/* create only one rproc in lockstep, single-cpu or  in k3_r5_cluster_rproc_init()
1358 	 * lockstep mode and single-cpu modes have only one rproc associated  in k3_r5_cluster_rproc_exit()
1761 		 * and LockStep-mode on all others  in k3_r5_probe()
1765 		 * LockStep-mode on all others  in k3_r5_probe()