blob: 6b154f0ce672761b9216b1bed9060e250592f14a [file] [log] [blame]
Douglas Raillard6f625742017-06-28 15:23:03 +01001ARM CPU Specific Build Macros
2=============================
3
4
5.. section-numbering::
6 :suffix: .
7
8.. contents::
9
10This document describes the various build options present in the CPU specific
11operations framework to enable errata workarounds and to enable optimizations
12for a specific CPU on a platform.
13
14CPU Errata Workarounds
15----------------------
16
17ARM Trusted Firmware exports a series of build flags which control the
18errata workarounds that are applied to each CPU by the reset handler. The
19errata details can be found in the CPU specific errata documents published
20by ARM:
21
22- `Cortex-A53 MPCore Software Developers Errata Notice`_
23- `Cortex-A57 MPCore Software Developers Errata Notice`_
24
25The errata workarounds are implemented for a particular revision or a set of
26processor revisions. This is checked by the reset handler at runtime. Each
27errata workaround is identified by its ``ID`` as specified in the processor's
28errata notice document. The format of the define used to enable/disable the
29errata workaround is ``ERRATA_<Processor name>_<ID>``, where the ``Processor name``
30is for example ``A57`` for the ``Cortex_A57`` CPU.
31
32Refer to the section *CPU errata status reporting* in
Eleanor Bonnici45b52c22017-08-02 16:35:04 +010033`Firmware Design guide`_ for information on how to write errata workaround
34functions.
Douglas Raillard6f625742017-06-28 15:23:03 +010035
36All workarounds are disabled by default. The platform is responsible for
37enabling these workarounds according to its requirement by defining the
38errata workaround build flags in the platform specific makefile. In case
39these workarounds are enabled for the wrong CPU revision then the errata
40workaround is not applied. In the DEBUG build, this is indicated by
41printing a warning to the crash console.
42
43In the current implementation, a platform which has more than 1 variant
44with different revisions of a processor has no runtime mechanism available
45for it to specify which errata workarounds should be enabled or not.
46
47The value of the build flags are 0 by default, that is, disabled. Any other
48value will enable it.
49
50For Cortex-A53, following errata build flags are defined :
51
52- ``ERRATA_A53_826319``: This applies errata 826319 workaround to Cortex-A53
53 CPU. This needs to be enabled only for revision <= r0p2 of the CPU.
54
Douglas Raillardca6b1cb2017-07-17 14:14:52 +010055- ``ERRATA_A53_835769``: This applies erratum 835769 workaround at compile and
56 link time to Cortex-A53 CPU. This needs to be enabled for some variants of
57 revision <= r0p4. This workaround can lead the linker to create ``*.stub``
58 sections.
59
Douglas Raillard6f625742017-06-28 15:23:03 +010060- ``ERRATA_A53_836870``: This applies errata 836870 workaround to Cortex-A53
61 CPU. This needs to be enabled only for revision <= r0p3 of the CPU. From
62 r0p4 and onwards, this errata is enabled by default in hardware.
63
Douglas Raillardca6b1cb2017-07-17 14:14:52 +010064- ``ERRATA_A53_843419``: This applies erratum 843419 workaround at link time
65 to Cortex-A53 CPU. This needs to be enabled for some variants of revision
66 <= r0p4. This workaround can lead the linker to emit ``*.stub`` sections
67 which are 4kB aligned.
68
Douglas Raillard6f625742017-06-28 15:23:03 +010069- ``ERRATA_A53_855873``: This applies errata 855873 workaround to Cortex-A53
70 CPUs. Though the erratum is present in every revision of the CPU,
71 this workaround is only applied to CPUs from r0p3 onwards, which feature
72 a chicken bit in CPUACTLR\_EL1 to enable a hardware workaround.
73 Earlier revisions of the CPU have other errata which require the same
74 workaround in software, so they should be covered anyway.
75
76For Cortex-A57, following errata build flags are defined :
77
78- ``ERRATA_A57_806969``: This applies errata 806969 workaround to Cortex-A57
79 CPU. This needs to be enabled only for revision r0p0 of the CPU.
80
81- ``ERRATA_A57_813419``: This applies errata 813419 workaround to Cortex-A57
82 CPU. This needs to be enabled only for revision r0p0 of the CPU.
83
84- ``ERRATA_A57_813420``: This applies errata 813420 workaround to Cortex-A57
85 CPU. This needs to be enabled only for revision r0p0 of the CPU.
86
87- ``ERRATA_A57_826974``: This applies errata 826974 workaround to Cortex-A57
88 CPU. This needs to be enabled only for revision <= r1p1 of the CPU.
89
90- ``ERRATA_A57_826977``: This applies errata 826977 workaround to Cortex-A57
91 CPU. This needs to be enabled only for revision <= r1p1 of the CPU.
92
93- ``ERRATA_A57_828024``: This applies errata 828024 workaround to Cortex-A57
94 CPU. This needs to be enabled only for revision <= r1p1 of the CPU.
95
96- ``ERRATA_A57_829520``: This applies errata 829520 workaround to Cortex-A57
97 CPU. This needs to be enabled only for revision <= r1p2 of the CPU.
98
99- ``ERRATA_A57_833471``: This applies errata 833471 workaround to Cortex-A57
100 CPU. This needs to be enabled only for revision <= r1p2 of the CPU.
101
Eleanor Bonnici45b52c22017-08-02 16:35:04 +0100102- ``ERRATA_A57_859972``: This applies errata 859972 workaround to Cortex-A57
103 CPU. This needs to be enabled only for revision <= r1p3 of the CPU.
104
Douglas Raillard6f625742017-06-28 15:23:03 +0100105CPU Specific optimizations
106--------------------------
107
108This section describes some of the optimizations allowed by the CPU micro
109architecture that can be enabled by the platform as desired.
110
111- ``SKIP_A57_L1_FLUSH_PWR_DWN``: This flag enables an optimization in the
112 Cortex-A57 cluster power down sequence by not flushing the Level 1 data
113 cache. The L1 data cache and the L2 unified cache are inclusive. A flush
114 of the L2 by set/way flushes any dirty lines from the L1 as well. This
115 is a known safe deviation from the Cortex-A57 TRM defined power down
116 sequence. Each Cortex-A57 based platform must make its own decision on
117 whether to use the optimization.
118
119- ``A53_DISABLE_NON_TEMPORAL_HINT``: This flag disables the cache non-temporal
120 hint. The LDNP/STNP instructions as implemented on Cortex-A53 do not behave
121 in a way most programmers expect, and will most probably result in a
122 significant speed degradation to any code that employs them. The ARMv8-A
123 architecture (see ARM DDI 0487A.h, section D3.4.3) allows cores to ignore
124 the non-temporal hint and treat LDNP/STNP as LDP/STP instead. Enabling this
125 flag enforces this behaviour. This needs to be enabled only for revisions
126 <= r0p3 of the CPU and is enabled by default.
127
128- ``A57_DISABLE_NON_TEMPORAL_HINT``: This flag has the same behaviour as
129 ``A53_DISABLE_NON_TEMPORAL_HINT`` but for Cortex-A57. This needs to be
130 enabled only for revisions <= r1p2 of the CPU and is enabled by default,
131 as recommended in section "4.7 Non-Temporal Loads/Stores" of the
132 `Cortex-A57 Software Optimization Guide`_.
133
134--------------
135
136*Copyright (c) 2014-2016, ARM Limited and Contributors. All rights reserved.*
137
Eleanor Bonnici45b52c22017-08-02 16:35:04 +0100138.. _Cortex-A53 MPCore Software Developers Errata Notice: http://infocenter.arm.com/help/topic/com.arm.doc.epm048406/Cortex_A53_MPCore_Software_Developers_Errata_Notice.pdf
Douglas Raillard6f625742017-06-28 15:23:03 +0100139.. _Cortex-A57 MPCore Software Developers Errata Notice: http://infocenter.arm.com/help/topic/com.arm.doc.epm049219/cortex_a57_mpcore_software_developers_errata_notice.pdf
140.. _Firmware Design guide: firmware-design.rst
141.. _Cortex-A57 Software Optimization Guide: http://infocenter.arm.com/help/topic/com.arm.doc.uan0015b/Cortex_A57_Software_Optimization_Guide_external.pdf