Home
last modified time | relevance | path

Searched full:lockstep (Results 1 – 22 of 22) sorted by relevance

/linux/Documentation/devicetree/bindings/remoteproc/
H A Dxlnx,zynqmp-r5fss.yaml47 If set to 1 then lockstep mode and if 0 then split mode.
48 If set to 2 then single CPU mode. When not defined, default will be lockstep mode.
51 1: lockstep mode (default)
60 1: lockstep mode
215 - description: extra ATCM memory in lockstep mode
216 - description: extra BTCM memory in lockstep mode
322 //Lockstep configuration
H A Dti,k3-r5f-rproc.yaml15 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:
/linux/drivers/remoteproc/
H A Dxlnx_r5_remoteproc.c38 LOCKSTEP_MODE = 1, /* cores execute same code in lockstep,clk-for-clk */
122 /* In lockstep mode cluster uses each 64KB TCM from second core as well */
1142 * r5 core 0 will use all of TCM banks in lockstep mode. in zynqmp_r5_get_tcm_node()
1178 * @tcm_mode: value expected by fw to configure TCM mode (lockstep or split)
1264 * In that case, default is LOCKSTEP mode. Other than that in zynqmp_r5_cluster_init()
1273 * For now driver only supports split mode and lockstep mode. in zynqmp_r5_cluster_init()
1302 * In lockstep mode if two child nodes are available, in zynqmp_r5_cluster_init()
1360 * If two child nodes are available in dts in lockstep mode, in zynqmp_r5_cluster_init()
/linux/Documentation/driver-api/firmware/
H A Dfirmware-usage-guidelines.rst35 * If a security fix needs lockstep firmware and kernel fixes in order to
/linux/Documentation/driver-api/
H A Dedac.rst45 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/drivers/edac/
H A Di7300_edac.c644 * 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()
H A Dsb_edac.c1702 /* KNL doesn't support mirroring or lockstep, in get_dimm_config()
1747 edac_dbg(0, "Lockstep is enabled\n"); in get_dimm_config()
1751 edac_dbg(0, "Lockstep is disabled\n"); in get_dimm_config()
1997 pr_warn_once("LockStep row/column decode is not supported yet!\n"); in sb_decode_ddr4()
3215 * FIXME: On some memory configurations (mirror, lockstep), the in sbridge_mce_output_error()
H A Di5400_edac.c22 * 2 channels operating in lockstep no-mirror mode. Each channel can have up to
/linux/drivers/firmware/efi/
H A Dcper.c229 case 20: return "Loss of Lockstep"; in cper_mem_err_status_str()
/linux/arch/x86/events/
H A Drapl.c644 * Divide interval by 2 to avoid lockstep (2 * 100) in rapl_check_hw_unit()
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Duncore-memory.json117 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/drivers/gpu/drm/vc4/
H A Dvc4_crtc.c175 * in active scanout the HVS and PV work in lockstep wrt. HVS in vc4_crtc_get_scanout_position()
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A Duncore-memory.json189 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/drivers/dma/qcom/
H A Dgpi.c1480 * STOP, RESET, or START needs to be in lockstep in gpi_terminate_all()
/linux/mm/
H A Dmemblock.c1109 * in lockstep and returns each intersection.
H A Dcompaction.c1480 * lockstep.
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A Duncore-memory.json226 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A Duncore-memory.json189 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A Duncore-memory.json218 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A Duncore-memory.json253 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A Duncore-memory.json231 …iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors in lockstep mode.",
/linux/arch/x86/kvm/
H A Dx86.c2967 * in lockstep.