Lines Matching full:lockstep
73 * @mode: Mode to configure the Cluster - Split or LockStep
392 * resets on all applicable cores for the rproc device (depending on LockStep
419 * The sequence is different between LockStep and Split modes. The LockStep
467 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
502 * The sequence is different between LockStep and Split modes, and the order
504 * of the start function. The LockStep mode requires each operation to be
634 * subsystem either in a safety/fault-tolerant LockStep mode or a performance
647 * once (in LockStep mode) or twice (in Split mode). Support for LockStep-mode
655 * They are identically configured in LockStep mode using the primary Core0
656 * settings. However, some individual settings cannot be set in LockStep mode.
659 * LockStep mode.
685 dev_err(cluster->dev, "lockstep mode not permitted, force configuring for split-mode\n"); in k3_r5_rproc_configure()
694 * LockStep configuration bit is Read-only on Split-mode _only_ in k3_r5_rproc_configure()
720 * cores are programmed symmetrically in LockStep. LockStep in k3_r5_rproc_configure()
918 /* create only one rproc in lockstep mode */ in k3_r5_cluster_rproc_init()
951 * lockstep mode has only one rproc associated with first core, whereas in k3_r5_cluster_rproc_exit()