Lines Matching full:trbe
767 bool "Cortex-A710/X2: 2119858: workaround TRBE overwriting trace data in FILL mode"
785 bool "Neoverse-N2: 2139208: workaround TRBE overwriting trace data in FILL mode"
839 bool "Neoverse-N2: 2253138: workaround TRBE writing to address out-of-range"
847 for TRBE. Under some conditions, the TRBE might generate a write to the next
848 virtually addressed page following the last page of the TRBE address space
852 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
857 bool "Cortex-A710/X2: 2224489: workaround TRBE writing to address out-of-range"
865 for TRBE. Under some conditions, the TRBE might generate a write to the next
866 virtually addressed page following the last page of the TRBE address space
870 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
892 bool "Cortex-A510: 2064142: workaround TRBE register writes while disabled"
899 TRBE has been disabled. Under some conditions after the TRBE has been disabled
900 writes into TRBE registers TRBLIMITR_EL1, TRBPTR_EL1, TRBBASER_EL1, TRBSR_EL1,
910 bool "Cortex-A510: 2038923: workaround TRBE corruption with enable"
918 might be corrupted. This happens after TRBE buffer has been enabled by setting
933 bool "Cortex-A510: 1902691: workaround TRBE trace corruption"
940 into the memory. Effectively TRBE is broken and hence cannot be used to capture
943 Work around this problem in the driver by just preventing TRBE initialization on
944 affected cpus. The firmware must have disabled the access to TRBE for the kernel