Searched full:lockstep (Results 1 – 21 of 21) sorted by relevance
| /Linux-v6.1/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 75 * LockStep mode : AM65x, J721E and J7200 SoCs
99 * @mode: Mode to configure the Cluster - Split or LockStep
429 * cluster in this mode. The function uses the same reset logic as LockStep
449 /* Re-use LockStep-mode reset logic for Single-CPU mode */ in k3_r5_rproc_prepare()
487 * resets on all applicable cores for the rproc device (depending on LockStep
496 * reset assert logic as LockStep mode for this mode (though the behavior is
508 /* Re-use LockStep-mode reset logic for Single-CPU mode */ in k3_r5_rproc_unprepare()
523 * The sequence is different between LockStep and Split modes. The LockStep
552 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
587 * The sequence is different between LockStep and Split modes, and the order
[all …]
|
| /Linux-v6.1/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
67 Should be either a value of 1 (LockStep mode) or 0 (Split mode) on
68 most SoCs (AM65x, J721E, J7200, J721s2), default is LockStep mode if
130 # The following properties are mandatory for R5F Core0 in both LockStep and Split
132 # R5F Core1 in LockStep mode:
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 35 * If a security fix needs lockstep firmware and kernel fixes in order to
|
| /Linux-v6.1/drivers/hid/i2c-hid/ |
| D | i2c-hid-of-goodix.c | 116 * We need to control the "reset" line in lockstep with the regulator in i2c_hid_of_goodix_probe()
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/firmware/efi/ |
| D | cper.c | 228 case 20: return "Loss of Lockstep"; in cper_mem_err_status_str()
|
| /Linux-v6.1/arch/x86/events/ |
| D | rapl.c | 635 * Divide interval by 2 to avoid lockstep (2 * 100) in rapl_check_hw_unit()
|
| /Linux-v6.1/arch/x86/kernel/cpu/mtrr/ |
| D | mtrr.c | 219 * the rendezvous handler is started on each CPU. And in lockstep they
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 124 … iMC can correct up to 4 bit errors in independent channel mode and 8 bit erros in lockstep mode.",
|
| /Linux-v6.1/drivers/gpu/drm/vc4/ |
| D | vc4_crtc.c | 147 * in active scanout the HVS and PV work in lockstep wrt. HVS in vc4_crtc_get_scanout_position()
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-memory.json | 191 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
|
| /Linux-v6.1/mm/ |
| D | memblock.c | 1040 * in lockstep and returns each intersection.
|
| D | compaction.c | 1333 * lockstep.
|
| D | slab.c | 508 * the CPUs getting into lockstep and contending for the global cache chain
|
| /Linux-v6.1/drivers/gpu/drm/i915/ |
| D | i915_request.c | 1982 * frame of the gpu. If the client is running in lockstep with the gpu, in i915_request_wait_timeout()
|
| /Linux-v6.1/drivers/dma/qcom/ |
| D | gpi.c | 1485 * STOP, RESET, or START needs to be in lockstep in gpi_terminate_all()
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-memory.json | 191 … iMC can correct up to 4 bit errors in independent channel mode and 8 bit erros in lockstep mode.",
|
| /Linux-v6.1/arch/x86/kvm/ |
| D | x86.c | 2894 * in lockstep.
|
