| /kernel/linux/linux-6.6/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 76 * LockStep mode : AM65x, J721E and J7200 SoCs
104 * @mode: Mode to configure the Cluster - Split or LockStep
435 * cluster in this mode. The function uses the same reset logic as LockStep
455 /* Re-use LockStep-mode reset logic for Single-CPU mode */ in k3_r5_rproc_prepare()
493 * resets on all applicable cores for the rproc device (depending on LockStep
502 * reset assert logic as LockStep mode for this mode (though the behavior is
514 /* Re-use LockStep-mode reset logic for Single-CPU mode */ in k3_r5_rproc_unprepare()
529 * The sequence is different between LockStep and Split modes. The LockStep
554 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
599 * The sequence is different between LockStep and Split modes, and the order
[all …]
|
| D | xlnx_r5_remoteproc.c | 34 LOCKSTEP_MODE = 1, /* cores execute same code in lockstep,clk-for-clk */
300 * @tcm_mode: value expected by fw to configure TCM mode (lockstep or split)
629 * allocate and add remoteproc carveout for TCM memory in lockstep mode
651 * In lockstep mode, TCM is contiguous memory block in add_tcm_carveout_lockstep_mode()
673 dev_dbg(dev, "TCM add carveout lockstep mode %s addr=0x%llx, size=0x%lx", in add_tcm_carveout_lockstep_mode()
727 * In lockstep mode TCM banks are one contiguous memory region of 256Kb in add_tcm_banks()
909 * r5 core 0 will use all of TCM banks in lockstep mode. in zynqmp_r5_get_tcm_node()
945 * @tcm_mode: value expected by fw to configure TCM mode (lockstep or split)
1011 * In that case, default is LOCKSTEP mode. Other than that in zynqmp_r5_cluster_init()
1020 * For now driver only supports split mode and lockstep mode. in zynqmp_r5_cluster_init()
[all …]
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 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.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 15 either in a LockStep mode providing safety/fault tolerance features or in a
20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
72 It should be either a value of 1 (LockStep mode) or 0 (Split mode) on
73 most SoCs (AM65x, J721E, J7200, J721s2), default is LockStep mode if
144 # The following properties are mandatory for R5F Core0 in both LockStep and Split
146 # R5F Core1 in LockStep mode:
|
| D | xlnx,zynqmp-r5fss.yaml | 32 If set to 1 then lockstep mode and if 0 then split mode.
33 If set to 2 then single CPU mode. When not defined, default will be lockstep mode.
36 1: lockstep mode (default)
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 15 either in a LockStep mode providing safety/fault tolerance features or in a
61 Should be either a value of 1 (LockStep mode) or 0 (Split mode),
62 default is LockStep mode if omitted.
120 # The following properties are mandatory for R5F Core0 in both LockStep and Split
122 # R5F Core1 in LockStep mode:
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | edac.rst | 45 same branch can be used in single mode or in lockstep mode. When
46 lockstep is enabled, the cacheline is doubled, but it generally brings
|
| /kernel/linux/linux-6.6/Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 35 * If a security fix needs lockstep firmware and kernel fixes in order to
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | edac.rst | 45 same branch can be used in single mode or in lockstep mode. When
46 lockstep is enabled, the cacheline is doubled, but it generally brings
|
| /kernel/linux/linux-6.6/drivers/firmware/xilinx/ |
| D | zynqmp.c | 1282 * either split or lockstep
1307 * @rpu_mode: Argument 1 to requested IOCTL call. either split or lockstep
1310 * lockstep
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | i7300_edac.c | 644 * In normal or mirrored mode, it uses Lockstep mode, in decode_mtr()
656 edac_dbg(2, "\t\tECC code is on Lockstep mode\n"); in decode_mtr()
|
| D | ghes_edac.c | 465 p += sprintf(p, "Loss of Lockstep "); in ghes_edac_report_mem_error()
|
| D | sb_edac.c | 1687 /* KNL doesn't support mirroring or lockstep, in get_dimm_config()
1732 edac_dbg(0, "Lockstep is enabled\n"); in get_dimm_config()
1736 edac_dbg(0, "Lockstep is disabled\n"); in get_dimm_config()
3085 * FIXME: On some memory configurations (mirror, lockstep), the in sbridge_mce_output_error()
|
| D | i5400_edac.c | 22 * 2 channels operating in lockstep no-mirror mode. Each channel can have up to
|
| /kernel/linux/linux-6.6/drivers/edac/ |
| D | i7300_edac.c | 644 * In normal or mirrored mode, it uses Lockstep mode, in decode_mtr()
656 edac_dbg(2, "\t\tECC code is on Lockstep mode\n"); in decode_mtr()
|
| D | sb_edac.c | 1700 /* KNL doesn't support mirroring or lockstep, in get_dimm_config()
1745 edac_dbg(0, "Lockstep is enabled\n"); in get_dimm_config()
1749 edac_dbg(0, "Lockstep is disabled\n"); in get_dimm_config()
1995 pr_warn_once("LockStep row/column decode is not supported yet!\n"); in sb_decode_ddr4()
3214 * FIXME: On some memory configurations (mirror, lockstep), the in sbridge_mce_output_error()
|
| D | i5400_edac.c | 22 * 2 channels operating in lockstep no-mirror mode. Each channel can have up to
|
| /kernel/linux/linux-6.6/arch/x86/kernel/cpu/mtrr/ |
| D | mtrr.c | 168 * the rendezvous handler is started on each CPU. And in lockstep they
|
| /kernel/linux/linux-5.10/arch/x86/events/ |
| D | rapl.c | 636 * Divide interval by 2 to avoid lockstep (2 * 100) in rapl_check_hw_unit()
|
| /kernel/linux/linux-6.6/arch/x86/events/ |
| D | rapl.c | 635 * Divide interval by 2 to avoid lockstep (2 * 100) in rapl_check_hw_unit()
|
| /kernel/linux/linux-6.6/drivers/firmware/efi/ |
| D | cper.c | 229 case 20: return "Loss of Lockstep"; in cper_mem_err_status_str()
|
| /kernel/linux/linux-5.10/arch/x86/kernel/cpu/mtrr/ |
| D | mtrr.c | 221 * the rendezvous handler is started on each CPU. And in lockstep they
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 104 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vc4/ |
| D | vc4_crtc.c | 141 * in active scanout the HVS and PV work in lockstep wrt. HVS in vc4_crtc_get_scanout_position()
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/vc4/ |
| D | vc4_crtc.c | 157 * in active scanout the HVS and PV work in lockstep wrt. HVS in vc4_crtc_get_scanout_position()
|