blob: 246381a8d15ccfa2bd1b4fcf66f0dc6ac454dd55 [file] [log] [blame] [view]
Soby Mathew5541bb32014-09-22 14:13:34 +01001ARM CPU Specific Build Macros
2=============================
3
4Contents
5--------
6
71. Introduction
82. CPU Errata Workarounds
93. CPU Specific optimizations
10
111. Introduction
12----------------
13
14This document describes the various build options present in the CPU specific
15operations framework to enable errata workarounds and to enable optimizations
16for a specific CPU on a platform.
17
182. CPU Errata Workarounds
19--------------------------
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010020
Sandrine Bailleux44804252014-08-06 11:27:23 +010021ARM Trusted Firmware exports a series of build flags which control the
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010022errata workarounds that are applied to each CPU by the reset handler. The
23errata details can be found in the CPU specifc errata documents published
24by ARM. The errata workarounds are implemented for a particular revision
Soby Mathew7395a722014-09-22 12:11:36 +010025or a set of processor revisions. This is checked by reset handler at runtime.
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010026Each errata workaround is identified by its `ID` as specified in the processor's
27errata notice document. The format of the define used to enable/disable the
28errata is `ERRATA_<Processor name>_<ID>` where the `Processor name`
29is either `A57` for the `Cortex_A57` CPU or `A53` for `Cortex_A53` CPU.
30
31All workarounds are disabled by default. The platform is reponsible for
32enabling these workarounds according to its requirement by defining the
Soby Mathew7395a722014-09-22 12:11:36 +010033errata workaround build flags in the platform specific makefile. In case
34these workarounds are enabled for the wrong CPU revision then the errata
35workaround is not applied. In the DEBUG build, this is indicated by
36printing a warning to the crash console.
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010037
38In the current implementation, a platform which has more than 1 variant
39with different revisions of a processor has no runtime mechanism available
40for it to specify which errata workarounds should be enabled or not.
41
Sandrine Bailleux44804252014-08-06 11:27:23 +010042The value of the build flags are 0 by default, that is, disabled. Any other
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010043value will enable it.
44
Soby Mathew7395a722014-09-22 12:11:36 +010045For Cortex-A57, following errata build flags are defined :
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010046
Soby Mathew7395a722014-09-22 12:11:36 +010047* `ERRATA_A57_806969`: This applies errata 806969 workaround to Cortex-A57
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010048 CPU. This needs to be enabled only for revision r0p0 of the CPU.
49
Soby Mathew7395a722014-09-22 12:11:36 +010050* `ERRATA_A57_813420`: This applies errata 813420 workaround to Cortex-A57
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010051 CPU. This needs to be enabled only for revision r0p0 of the CPU.
52
Soby Mathew5541bb32014-09-22 14:13:34 +0100533. CPU Specific optimizations
54------------------------------
55
56This section describes some of the optimizations allowed by the CPU micro
57architecture that can be enabled by the platform as desired.
58
59* `SKIP_A57_L1_FLUSH_PWR_DWN`: This flag enables an optimization in the
60 Cortex-A57 cluster power down sequence by not flushing the Level 1 data
61 cache. The L1 data cache and the L2 unified cache are inclusive. A flush
62 of the L2 by set/way flushes any dirty lines from the L1 as well. This
63 is a known safe deviation from the Cortex-A57 TRM defined power down
64 sequence. Each Cortex-A57 based platform must make its own decision on
65 whether to use the optimization.
66
Soby Mathew3fd5ddf2014-08-18 16:57:56 +010067- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
68
69_Copyright (c) 2014, ARM Limited and Contributors. All rights reserved._