Lines Matching full:trbe

868 	bool "Cortex-A710/X2: 2119858: workaround TRBE overwriting trace data in FILL mode"
886 	bool "Neoverse-N2: 2139208: workaround TRBE overwriting trace data in FILL mode"
940 	bool "Neoverse-N2: 2253138: workaround TRBE writing to address out-of-range"
948 	  for TRBE. Under some conditions, the TRBE might generate a write to the next
949 	  virtually addressed page following the last page of the TRBE address space
953 	  page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
958 	bool "Cortex-A710/X2: 2224489: workaround TRBE writing to address out-of-range"
966 	  for TRBE. Under some conditions, the TRBE might generate a write to the next
967 	  virtually addressed page following the last page of the TRBE address space
971 	  page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
992 	bool "Cortex-A510: 2064142: workaround TRBE register writes while disabled"
999 	  TRBE has been disabled. Under some conditions after the TRBE has been disabled
1000 	  writes into TRBE registers TRBLIMITR_EL1, TRBPTR_EL1, TRBBASER_EL1, TRBSR_EL1,
1010 	bool "Cortex-A510: 2038923: workaround TRBE corruption with enable"
1018 	  might be corrupted. This happens after TRBE buffer has been enabled by setting
1033 	bool "Cortex-A510: 1902691: workaround TRBE trace corruption"
1040 	  into the memory. Effectively TRBE is broken and hence cannot be used to capture
1043 	  Work around this problem in the driver by just preventing TRBE initialization on
1044 	  affected cpus. The firmware must have disabled the access to TRBE for the kernel