Lines Matching full:trbe
848 bool "Cortex-A710/X2: 2119858: workaround TRBE overwriting trace data in FILL mode"
866 bool "Neoverse-N2: 2139208: workaround TRBE overwriting trace data in FILL mode"
920 bool "Neoverse-N2: 2253138: workaround TRBE writing to address out-of-range"
928 for TRBE. Under some conditions, the TRBE might generate a write to the next
929 virtually addressed page following the last page of the TRBE address space
933 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
938 bool "Cortex-A710/X2: 2224489: workaround TRBE writing to address out-of-range"
946 for TRBE. Under some conditions, the TRBE might generate a write to the next
947 virtually addressed page following the last page of the TRBE address space
951 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
972 bool "Cortex-A510: 2064142: workaround TRBE register writes while disabled"
979 TRBE has been disabled. Under some conditions after the TRBE has been disabled
980 writes into TRBE registers TRBLIMITR_EL1, TRBPTR_EL1, TRBBASER_EL1, TRBSR_EL1,
990 bool "Cortex-A510: 2038923: workaround TRBE corruption with enable"
998 might be corrupted. This happens after TRBE buffer has been enabled by setting
1013 bool "Cortex-A510: 1902691: workaround TRBE trace corruption"
1020 into the memory. Effectively TRBE is broken and hence cannot be used to capture
1023 Work around this problem in the driver by just preventing TRBE initialization on
1024 affected cpus. The firmware must have disabled the access to TRBE for the kernel