Lines Matching defs:mode
73 * @mode: Mode to configure the Cluster - Split or LockStep
78 enum cluster_mode mode;
367 ret = (cluster->mode == CLUSTER_MODE_LOCKSTEP) ?
393 * or Split mode). This completes the second portion of powering down the R5F
406 ret = (cluster->mode == CLUSTER_MODE_LOCKSTEP) ?
420 * mode requires the boot vector to be configured only for Core0, and then
422 * first followed by Core0. The Split-mode requires that Core0 to be maintained
467 /* boot vector need not be programmed for Core1 in LockStep mode */
474 if (cluster->mode == CLUSTER_MODE_LOCKSTEP) {
504 * of the start function. The LockStep mode requires each operation to be
505 * performed first on Core0 followed by Core1. The Split-mode requires that
525 if (cluster->mode == CLUSTER_MODE_LOCKSTEP) {
634 * subsystem either in a safety/fault-tolerant LockStep mode or a performance
635 * oriented Split mode. Each R5F core has a number of settings to either
647 * once (in LockStep mode) or twice (in Split mode). Support for LockStep-mode
649 * DT are adjusted accordingly as per the permitted cluster mode. All cluster
650 * level settings like Cluster mode and TEINIT (exception handling state
651 * dictating ARM or Thumb mode) can only be set and retrieved using Core0.
653 * The function behavior is different based on the cluster mode. The R5F cores
654 * are configured independently as per their individual settings in Split 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.
657 * This is overcome by switching to Split-mode initially and then programming
659 * LockStep mode.
673 core = (cluster->mode == CLUSTER_MODE_LOCKSTEP) ? core0 : kproc->core;
684 if (!lockstep_en && cluster->mode == CLUSTER_MODE_LOCKSTEP) {
685 dev_err(cluster->dev, "lockstep mode not permitted, force configuring for split-mode\n");
686 cluster->mode = CLUSTER_MODE_SPLIT;
689 /* always enable ARM mode and set boot vector to 0 */
694 * LockStep configuration bit is Read-only on Split-mode _only_
717 if (cluster->mode == CLUSTER_MODE_LOCKSTEP) {
918 /* create only one rproc in lockstep mode */
919 if (cluster->mode == CLUSTER_MODE_LOCKSTEP)
933 /* undo core0 upon any failures on core1 in split-mode */
934 if (cluster->mode == CLUSTER_MODE_SPLIT && core == core1) {
951 * lockstep mode has only one rproc associated with first core, whereas
952 * split-mode has two rprocs associated with each core, and requires
955 core = (cluster->mode == CLUSTER_MODE_LOCKSTEP) ?
1324 cluster->mode = CLUSTER_MODE_LOCKSTEP;
1327 ret = of_property_read_u32(np, "ti,cluster-mode", &cluster->mode);
1329 dev_err(dev, "invalid format for ti,cluster-mode, ret = %d\n",