| /openbmc/linux/drivers/remoteproc/ |
| H A D | 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
[all …]
|
| H A 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 …]
|
| /openbmc/qemu/contrib/plugins/ |
| H A D | meson.build | 4 # lockstep uses socket.h
5 contrib_plugins += 'lockstep'
|
| H A D | lockstep.c | 2 * Lockstep Execution Plugin
4 * Allows you to execute two QEMU instances in lockstep and report
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A 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:
|
| H A 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)
|
| /openbmc/u-boot/arch/arm/mach-zynqmp/ |
| H A D | mp.c | 240 printf("<addr> <mode>-Start addr lockstep or split\n"); in cpu_release()
266 if (!strncmp(argv[1], "lockstep", 8)) { in cpu_release()
267 printf("R5 lockstep mode\n"); in cpu_release()
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-cryptography-common.inc | 5 # perform a lockstep upgrade for both.
|
| /openbmc/openbmc/poky/meta/recipes-graphics/spir/ |
| H A D | spirv-headers_1.3.296.0.bb | 10 # These recipes need to be updated in lockstep with each other:
|
| H A D | spirv-tools_1.3.296.0.bb | 14 # These recipes need to be updated in lockstep with each other:
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/ |
| H A D | vulkan-utility-libraries_1.3.296.0.bb | 27 # These recipes need to be updated in lockstep with each other:
|
| H A D | vulkan-volk_1.3.296.0.bb | 27 # These recipes need to be updated in lockstep with each other:
|
| H A D | vulkan-headers_1.3.296.0.bb | 23 # These recipes need to be updated in lockstep with each other:
|
| H A D | vulkan-tools_1.3.296.0.bb | 32 # These recipes need to be updated in lockstep with each other:
|
| H A D | vulkan-loader_1.3.296.0.bb | 38 # These recipes need to be updated in lockstep with each other:
|
| H A D | vulkan-validation-layers_1.3.296.0.bb | 43 # These recipes need to be updated in lockstep with each other:
|
| /openbmc/openbmc/poky/meta/recipes-graphics/glslang/ |
| H A D | glslang_1.3.296.0.bb | 16 # These recipes need to be updated in lockstep with each other:
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A D | firmware-usage-guidelines.rst | 35 * If a security fix needs lockstep firmware and kernel fixes in order to
|
| /openbmc/linux/Documentation/driver-api/ |
| H A 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
|
| /openbmc/u-boot/tools/ |
| H A D | zynqmpimage.h | 94 "r5-lockstep", "pmu", "unknown", "unknown", "unknown", "unknown",
|
| /openbmc/intel-ipmi-oem/src/ |
| H A D | ipmi_to_redfish_hooks.cpp | 106 messageArgs.push_back("Lockstep"); in biosMessageHook()
224 messageArgs.push_back("Lockstep"); in biosMessageHook()
242 messageArgs.push_back("Lockstep"); in biosMessageHook()
|
| /openbmc/qemu/docs/about/ |
| H A D | emulation.rst | 563 Lockstep Execution
566 ``contrib/plugins/lockstep.c``
583 -plugin ./contrib/plugins/liblockstep.so,sockpath=lockstep-sparc.sock \
|
| /openbmc/linux/drivers/firmware/xilinx/ |
| H A D | zynqmp.c | 1282 * either split or lockstep
1307 * @rpu_mode: Argument 1 to requested IOCTL call. either split or lockstep
1310 * lockstep
|
| /openbmc/linux/drivers/edac/ |
| H A 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()
|
| /openbmc/linux/arch/x86/kernel/cpu/mtrr/ |
| H A D | mtrr.c | 168 * the rendezvous handler is started on each CPU. And in lockstep they
|