| /trusted-firmware-a-3.7.0/plat/mediatek/mt8183/drivers/spm/ |
| D | spm_pmic_wrap.c | 50 } _[NR_PMIC_WRAP_CMD]; member
59 ._[CMD_0] = {BUCK_VCORE_ELR0, VOLT_TO_PMIC_VAL(70000),},
60 ._[CMD_1] = {BUCK_VCORE_ELR0, VOLT_TO_PMIC_VAL(80000),},
61 ._[CMD_2] = {BUCK_VPROC12_CON0, 0x3,},
62 ._[CMD_3] = {BUCK_VPROC12_CON0, 0x1,},
63 ._[CMD_4] = {BUCK_VPROC11_CON0, 0x3,},
64 ._[CMD_5] = {BUCK_VPROC11_CON0, 0x1,},
65 ._[CMD_6] = {TOP_SPI_CON0, 0x1,},
66 ._[CMD_7] = {TOP_SPI_CON0, 0x0,},
67 ._[CMD_8] = {BUCK_VPROC12_CON0, 0x0,},
[all …]
|
| /trusted-firmware-a-3.7.0/plat/mediatek/mt8192/drivers/spm/ |
| D | mt_spm_pmic_wrap.c | 47 } _[NR_PMIC_WRAP_CMD]; member
56 ._[CMD_0] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(72500),},
57 ._[CMD_1] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(65000),},
58 ._[CMD_2] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(60000),},
59 ._[CMD_3] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(57500),},
60 ._[CMD_4] = {TOP_SPI_CON0, 0x1,},
61 ._[CMD_5] = {TOP_SPI_CON0, 0x0,},
62 ._[CMD_6] = {BUCK_TOP_CON1, 0x0,},
63 ._[CMD_7] = {BUCK_TOP_CON1, 0xf,},
64 ._[CMD_8] = {TOP_CON, 0x3,},
[all …]
|
| /trusted-firmware-a-3.7.0/plat/mediatek/drivers/spm/mt8188/ |
| D | mt_spm_pmic_wrap.c | 52 } _[NR_PMIC_WRAP_CMD]; member
61 ._[CMD_0] = {BUCK_VGPU11_ELR0, _BITS_(6, 0, VOLT_TO_PMIC_VAL(75000)),},
62 ._[CMD_1] = {BUCK_VGPU11_ELR0, _BITS_(6, 0, VOLT_TO_PMIC_VAL(65000)),},
63 ._[CMD_2] = {BUCK_VGPU11_ELR0, _BITS_(6, 0, VOLT_TO_PMIC_VAL(60000)),},
64 ._[CMD_3] = {BUCK_VGPU11_ELR0, _BITS_(6, 0, VOLT_TO_PMIC_VAL(55000)),},
65 ._[CMD_4] = {TOP_SPI_CON0, _BITS_(0, 0, 1),},
66 ._[CMD_5] = {TOP_SPI_CON0, _BITS_(0, 0, 0),},
67 ._[CMD_6] = {BUCK_TOP_CON1, 0x0,}, /* MT6315-3: VMD NO LP */
68 ._[CMD_7] = {BUCK_TOP_CON1, 0xF,}, /* MT6315-3: VMD LP */
69 ._[CMD_8] = {TOP_CON, 0x3,}, /* MT6315-3: PMIC NO LP */
[all …]
|
| /trusted-firmware-a-3.7.0/plat/mediatek/mt8195/drivers/spm/ |
| D | mt_spm_pmic_wrap.c | 47 } _[NR_PMIC_WRAP_CMD]; member
56 ._[CMD_0] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(75000),},
57 ._[CMD_1] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(65000),},
58 ._[CMD_2] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(60000),},
59 ._[CMD_3] = {BUCK_VGPU11_ELR0, VOLT_TO_PMIC_VAL(55000),},
60 ._[CMD_4] = {TOP_SPI_CON0, 0x1,},
61 ._[CMD_5] = {TOP_SPI_CON0, 0x0,},
62 ._[CMD_6] = {BUCK_TOP_CON1, 0x0,},
63 ._[CMD_7] = {BUCK_TOP_CON1, 0xf,},
64 ._[CMD_8] = {TOP_CON, 0x3,},
[all …]
|
| /trusted-firmware-a-3.7.0/plat/mediatek/mt8186/drivers/spm/ |
| D | mt_spm_pmic_wrap.c | 34 } _[NR_PMIC_WRAP_CMD]; member
53 ._[CMD_0] = { BUCK_VCORE_ELR0_66, VOLT_TO_PMIC_VAL_66(80000), },
54 ._[CMD_1] = { BUCK_VCORE_ELR0_66, VOLT_TO_PMIC_VAL_66(80000), },
55 ._[CMD_2] = { BUCK_VCORE_ELR0_66, VOLT_TO_PMIC_VAL_66(80000), },
56 ._[CMD_3] = { BUCK_VCORE_ELR0_66, VOLT_TO_PMIC_VAL_66(80000), },
57 ._[CMD_4] = { BUCK_VCORE_ELR0_66, VOLT_TO_PMIC_VAL_66(80000), },
58 ._[CMD_5] = { TOP_SPI_CON0_66, 0x1, },
59 ._[CMD_6] = { TOP_SPI_CON0_66, 0x0, },
73 ._[CMD_0] = { BUCK_VCORE_ELR0_57, VOLT_TO_PMIC_VAL_57(80000), },
74 ._[CMD_1] = { BUCK_VCORE_ELR0_57, VOLT_TO_PMIC_VAL_57(75000), },
[all …]
|
| /trusted-firmware-a-3.7.0/docs/about/ |
| D | maintainers.rst | 25 :|G|: `danh-arm`_
27 :|G|: `soby-mathew`_
29 :|G|: `sandrine-bailleux-arm`_
31 :|G|: `AlexeiFedorov`_
33 :|G|: `manish-pandey-arm`_
35 :|G|: `mardyk01`_
37 :|G|: `odeprez`_
39 :|G|: `bipinravi-arm`_
41 :|G|: `joannafarley-arm`_
43 :|G|: `jwerner-chromium`_
[all …]
|
| D | contact.rst | 22 - `TF-A development`_
23 - `TF-A-Tests development`_
25 You can see a `summary of all the lists`_ on the TrustedFirmware.org website.
32 topic within the community. More details can be found `here`_.
39 Bug reports may be filed on the `issue tracker`_ on the TrustedFirmware.org
49 .. _`issue tracker`: https://developer.trustedfirmware.org
50 .. _`TF-A development`: https://lists.trustedfirmware.org/mailman3/lists/tf-a.lists.trustedfirmware…
51 .. _`TF-A-Tests development`: https://lists.trustedfirmware.org/mailman3/lists/tf-a-tests.lists.tru…
52 .. _`summary of all the lists`: https://lists.trustedfirmware.org/mailman3/lists/
|
| /trusted-firmware-a-3.7.0/include/lib/cpus/aarch64/ |
| D | cpu_macros.S | 287 .quad erratum_\_cpu\()_\_id\()_wa
294 .quad check_erratum_\_cpu\()_\_id
308 func erratum_\_cpu\()_\_id\()_wa
314 bl check_erratum_\_cpu\()_\_id
315 cbz x0, erratum_\_cpu\()_\_id\()_skip
319 erratum_\_cpu\()_\_id\()_skip:
321 endfunc erratum_\_cpu\()_\_id\()_wa
369 b erratum_\_cpu\()_\_id\()_skip
492 bl erratum_\_cpu\()_\_id\()_wa
519 func check_erratum_\_cpu\()_\_id
[all …]
|
| /trusted-firmware-a-3.7.0/ |
| D | readme.rst | 5 for `Arm A-Profile architectures`_ (Armv8-A and Armv7-A), including an Exception
6 Level 3 (EL3) `Secure Monitor`_. It provides a suitable starting point for
12 - `Power State Coordination Interface (PSCI)`_
13 - `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)`_
14 - `SMC Calling Convention`_
15 - `System Control and Management Interface (SCMI)`_
16 - `Software Delegated Exception Interface (SDEI)`_
31 To find out more about Trusted Firmware-A, please `view the full documentation`_
32 that is available through `trustedfirmware.org`_.
|
| /trusted-firmware-a-3.7.0/docs/security_advisories/ |
| D | security-advisory-tfv-11.rst | 7 | CVE ID | `CVE-2023-49100`_ |
19 | Fix Version | `a7eff3477`_ "fix(sdei): ensure that interrupt ID is valid" |
21 | Credit | Christian Lindenmeier `@_chli_`_ |
22 | | Marcel Busch `@0ddc0de`_ |
23 | | `IT Security Infrastructures Lab`_ |
33 Refer to SDEI_INTERRUPT_BIND in the `SDEI Specification`_ for further details.
85 .. _@_chli_: https://twitter.com/_chli_
86 .. _@0ddc0de: https://twitter.com/0ddc0de
|
| D | security-advisory-tfv-6.rst | 8 | CVE ID | `CVE-2017-5753`_ / `CVE-2017-5715`_ / `CVE-2017-5754`_ |
21 | Fix Version | `Pull Request #1214`_, `Pull Request #1228`_, |
22 | | `Pull Request #1240`_ and `Pull Request #1405`_ |
29 `Google Project Zero`_. To understand the background and wider impact of these
31 Update`_.
33 Variant 1 (`CVE-2017-5753`_)
39 Variant 2 (`CVE-2017-5715`_)
65 `Pull Request #1240`_ and `Pull Request #1405`_ optimise the earlier fixes by
66 implementing a specified `CVE-2017-5715`_ workaround SMC
70 mitigation specification`_. The specification and implementation also enable
[all …]
|
| D | security-advisory-tfv-7.rst | 8 | CVE ID | `CVE-2018-3639`_ |
20 | Fix Version | `Pull Request #1392`_, `Pull Request #1397`_ |
27 identified by `Google Project Zero`_. To understand the background and wider
29 Processor Security Update`_.
37 (SDEI)`_. Also, the TF-A project does not have visibility of all
44 approaches in `Pull Request #1392`_ and `Pull Request #1397`_. Both approaches
82 interfaces for mitigating cache speculation vulnerabilities`_.
|
| D | security-advisory-tfv-9.rst | 8 | CVE ID | `CVE-2022-23960`_ |
24 | Fix Version | `Gerrit topic #spectre_bhb`_ |
33 systems, please refer to the `Arm Processor Security Update`_. The whitepaper
38 `CVE-2022-23960`_
99 Convention specification`_ for more details.
101 `Gerrit topic #spectre_bhb`_ This patchset implements the Spectre-BHB loop
107 `CVE-2022-23960`_ workaround SMC(``SMCCC_ARCH_WORKAROUND_3``) for use by normal
109 in the `SMCCC Calling Convention specification`_. The specification and
|
| D | security-advisory-tfv-2.rst | 8 | CVE ID | `CVE-2017-7564`_ |
20 | Fix Version | 15 Feb 2017 `Pull Request #841`_ |
29 be seen in the implementation of the ``el3_arch_init_common`` `AArch64 macro`_ .
37 Earlier versions of TF (prior to `commit 495f3d3`_) did not assign this bit.
53 image or integrate the `AArch32 equivalent`_ of the ``el3_arch_init_common``
|
| D | security-advisory-tfv-5.rst | 8 | CVE ID | `CVE-2017-15031`_ |
20 | Fix Version | `Pull Request #1127`_ (merged on 18 October 2017) |
22 | | `Commit e290a8fcbc`_ (merged on 23 August 2019) |
24 | | `Commit c3e8b0be9b`_ (merged on 27 September 2019) |
|
| D | security-advisory-tfv-10.rst | 8 | CVE ID | `CVE-2022-47630`_ |
21 | Fix Version | - `fd37982a19a4a291`_ "fix(auth): forbid junk after |
24 | | - `72460f50e2437a85`_ "fix(auth): require at least one |
27 | | - `f5c51855d36e399e`_ "fix(auth): properly validate X.509 |
30 | | - `abb8f936fd0ad085`_ "fix(auth): avoid out-of-bounds read |
33 | | Note that `72460f50e2437a85`_ is not fixing any |
35 | | `f5c51855d36e399e`_ to apply cleanly. |
52 - `RFC 5280`_, *Internet X.509 Public Key Infrastructure Certificate and
55 - `ITU-T X.690`_, *ASN.1 encoding rules: Specification of Basic Encoding Rules
|
| D | security-advisory-tfv-3.rst | 7 | CVE ID | `CVE-2017-7563`_ |
11 | Versions | v1.3 (since `Pull Request #662`_) |
19 | Fix Version | `Pull Request #924`_ |
45 The vulnerability primarily manifests itself after `Pull Request #662`_. Before
48 were implicitly executable. Before `Pull Request #662`_. the vulnerability
|
| /trusted-firmware-a-3.7.0/docs/ |
| D | index.rst | 26 software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
30 - The `Power State Coordination Interface (PSCI)`_
31 - `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)`_
32 - `SMC Calling Convention`_
33 - `System Control and Management Interface (SCMI)`_
34 - `Software Delegated Exception Interface (SDEI)`_
35 - `PSA FW update specification`_
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/morello/ |
| D | index.rst | 5 The platform port present at `site <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`_
8 …ility architecture specific changes will be added `here <https://git.morello-project.org/morello>`_
10 …s available at `info <https://developer.arm.com/architectures/cpu-architecture/a-profile/morello>`_
32 …r.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads>`_.
|
| /trusted-firmware-a-3.7.0/plat/nxp/common/plat_make_helper/ |
| D | plat_build_macros.mk | 10 $2_$1 := yes
|
| /trusted-firmware-a-3.7.0/docs/components/ |
| D | realm-management-extension.rst | 6 `Arm Confidential Compute Architecture (Arm CCA)`_. TF-A supports RME starting
16 Root world. In the realm world, a Realm Management Monitor firmware (`RMM`_)
47 Realm-world firmware (`RMM`_) is loaded by BL2 in the Realm physical address
73 world. It initializes the `RMM`_ and handles Realm Management Interface (RMI)
76 There is a contract between `RMM`_ and RMMD that defines the arguments that the
78 This contract is defined in the `RMM`_ Boot Interface, which can be found at
82 to `RMM`_. This can be found at :ref:`runtime_services_and_interface`.
107 - R-EL2 (`RMM`_ or TRP)
115 - R-EL2 (`RMM`_ or TRP)
128 Please refer to the `RMM Getting Started`_ on how to setup
[all …]
|
| /trusted-firmware-a-3.7.0/docs/plat/ |
| D | meson-g12a.rst | 23 instructions in the `gxlimg repository`_ or `U-Boot repository`_, replacing the
|
| D | meson-gxl.rst | 23 instructions in the `gxlimg repository`_ or `U-Boot repository`_, replacing the
|
| /trusted-firmware-a-3.7.0/docs/getting_started/ |
| D | docs-build.rst | 5 `Sphinx`_ tool to build and package the plain-text documents into HTML-formatted
24 - `Poetry`_ (Python dependency manager)
25 - Optionally, the `Dia`_ application can be installed if you need to edit
114 other use cases, please see the official `Poetry`_ documentation.
122 to check if `docker`_ is installed in your host, otherwise check main docker
135 hub`_, launches the container, installs documentation requirements and finally
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/fvp_r/ |
| D | index.rst | 14 …ion on v8-R64 FVP is available at `info <https://developer.arm.com/documentation/ddi0600/latest/>`_
27 …r.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads>`_.
|
