Home
last modified time | relevance | path

Searched refs:platform (Results 1 – 25 of 176) sorted by relevance

12345678

/rk3399_ARM-atf/plat/xilinx/versal/aarch64/
H A Dversal_common.c69 const char *platform; in board_name_decode() local
73 platform = "IPP"; in board_name_decode()
76 platform = "EMU"; in board_name_decode()
79 platform = "QEMU"; in board_name_decode()
82 platform = "SILICON"; in board_name_decode()
85 platform = "unknown"; in board_name_decode()
88 return platform; in board_name_decode()
/rk3399_ARM-atf/plat/amd/versal2/aarch64/
H A Dcommon.c51 const char *platform; in board_name_decode() local
55 platform = "IPP"; in board_name_decode()
58 platform = "EMU"; in board_name_decode()
61 platform = "Silicon"; in board_name_decode()
64 platform = "QEMU"; in board_name_decode()
67 platform = "Unknown"; in board_name_decode()
70 return platform; in board_name_decode()
/rk3399_ARM-atf/plat/xilinx/versal_net/aarch64/
H A Dversal_net_common.c50 const char *platform; in board_name_decode() local
54 platform = "IPP"; in board_name_decode()
57 platform = "EMU"; in board_name_decode()
60 platform = "Silicon"; in board_name_decode()
63 platform = "QEMU"; in board_name_decode()
66 platform = "Unknown"; in board_name_decode()
69 return platform; in board_name_decode()
/rk3399_ARM-atf/docs/getting_started/
H A Dinitial-build.rst33 make CC=<path-to-armclang>/bin/armclang PLAT=<platform> all
48 make CC=<path-to-clang>/bin/clang PLAT=<platform> all
56 make PLAT=<platform> all
62 make PLAT=<platform> ARCH=aarch32 AARCH32_SP=sp_min all
93 - ``build/<platform>/<build-type>/bl1.bin``
94 - ``build/<platform>/<build-type>/bl2.bin``
95 - ``build/<platform>/<build-type>/bl31.bin`` (AArch64 only)
96 - ``build/<platform>/<build-type>/bl32.bin`` (mandatory for AArch32)
98 where ``<platform>`` is the name of the chosen platform and ``<build-type>``
100 depending on the platform.
[all …]
H A Dtools-build.rst18 platform. While it is not an intrinsic part of the FIP format, a BL33 image is
24 for the specified platform using the FIP creation tool included in the TF-A
76 --tb-fw build/<platform>/<build-type>/bl2.bin \
77 --soc-fw build/<platform>/<build-type>/bl31.bin \
92 --tb-fw build/<platform>/release/bl2.bin \
93 build/<platform>/debug/fip.bin
107 --tb-fw build/<platform>/debug/fip.bin
129 make PLAT=<platform> [DEBUG=1] [V=1] certtool
133 platform must define its IDs within a ``platform_oid.h`` header file for the
138 make PLAT=<platform> USE_TBBR_DEFS=0 [DEBUG=1] [V=1] certtool
[all …]
/rk3399_ARM-atf/docs/
H A Dporting-guide.rst7 Porting Trusted Firmware-A (TF-A) to a new platform involves making some
11 - Implementing a platform-specific function or variable,
15 The platform-specific functions and variables are declared in
16 ``include/plat/common/platform.h``. The firmware provides a default
18 in order to ease the porting effort. Each platform port can use them as is or
23 TF-A historically provided default implementations of platform interfaces
24 as *weak* functions. This practice is now discouraged and new platform
30 effort. Some platform interfaces play a key role in mitigating against some of
32 guarantees offered by TF-A. These platform responsibilities are highlighted in
54 This section covers the modifications that should be made by the platform for
[all …]
/rk3399_ARM-atf/docs/design_documents/
H A Ddtpm_drivers.rst11 sensitive information, such as encryption keys and platform credentials, from
43 that use the platform bus interface to transfer commands.
44 - **Platform Layer**: The platform layer implements the details of how to
45 communicate to the TPM chip for a specific platform. The link layer uses the
46 platform layer to read and write to the TPM.
50 TF-A. The platform layer is implemented in platform specific code.
53 Pi 3 platform.
96 The TPM needs to be initialized based on the platform, the hardware interfaces
102 An example of platform specific TPM hardware initialization for the rpi3 can be
H A Dpsci_osi_mode.rst30 PSCI supports two modes of power state coordination: platform-coordinated and
39 In platform-coordinated mode, the platform is responsible for coordinating power
56 platform-coordinated mode for a platform.
61 In platform-coordinated mode, each core independently selects their own local
75 In platform-coordinated mode, the OS doesn't have visibility when the last core
79 This could result in a design smell where the platform is using
80 platform-coordinated mode when it should be using OS-initiated mode instead.
85 the OS and the platform.
101 * For their Chrome OS platforms, they're using platform-coordinated mode in
106 * They're using platform-coordinated mode in TF-A with custom driver logic to
[all …]
H A Dmeasured_boot.rst15 enforce local attestation policies (such as releasing certain platform keys or
34 on each platform. They are referred to as *critical data*.
36 Critical data for the platform can be determined using the following criteria:
61 (measure) images and critical data on a platform.
113 The following diagram outlines the call sequence for Measured Boot platform
118 These platform interfaces are used by BL1 and BL2 only, and are declared in
119 ``include/plat/common/platform.h``.
122 Responsibilities of these platform interfaces are -
131 Initialise all Measured Boot backends supported by the platform
133 the platform should deal with error management, such as logging the error
[all …]
/rk3399_ARM-atf/docs/design/
H A Dreset-design.rst5 resets in Trusted Firmware-A (TF-A). It also describes how the platform
23 guide the platform integrator by indicating which build options exclude which
24 steps, depending on the capability of the platform.
63 If the platform guarantees that only a single CPU will ever be brought up then
74 default, there are platform-specific ways to release any number of cores out of
75 reset. Therefore, both platform ports use ``COLD_BOOT_SINGLE_CPU=0``.
103 In this configuration, the platform's Trusted Boot Firmware must ensure that
106 Additionally, platform software is responsible for loading the other BL3x images
108 images might be done by the Trusted Boot Firmware or by platform code in BL31.
110 Although the Arm FVP platform does not support programming the reset base
[all …]
H A Dpsci-pd-tree.rst7 #. A platform must export the ``plat_get_aff_count()`` and
13 It would be much simpler for the platform to describe its power domain tree
18 a platform will use exactly the same MPIDRs as generated by the generic PSCI
53 To fulfill requirement 1., the existing platform APIs
55 removed. A platform must define an array of unsigned chars such that:
58 highest power level implemented in the platform. This caters for platforms
110 This tree is defined by the platform as the array described above as follows:
121 Removing assumptions about MPIDRs used in a platform
124 To fulfill requirement 2., it is assumed that the platform assigns a
132 platform API have changed since it is required to validate the passed MPIDR. It
[all …]
/rk3399_ARM-atf/plat/arm/board/n1sdp/fdts/
H A Dn1sdp_nt_fw_config.dts13 * Place holder for platform-info node with default values.
17 platform-info {
/rk3399_ARM-atf/docs/components/fconf/
H A Dindex.rst10 platform specific data, allowing a "property" to be queried and a value
14 It is used to bridge new and old ways of providing platform-specific data.
16 platform-defined tables. In the future, it may be provided as part of a device
40 then the platform has to provide a ``populate()`` function which essentially
44 Such a ``populate()`` function is usually platform specific and is associated
46 captures the hardware topology of the platform from the HW_CONFIG device tree.
119 - Properties used inside platform specific code.
132 within the platform API and are defined only inside the platform scope. The
133 namespace must contain the platform name under which the properties defined
/rk3399_ARM-atf/plat/arm/board/neoverse_rd/platform/rdv3/fdts/
H A Drdv3_nt_fw_config.dts14 * value of platform-id and config-id will be set to the
18 platform-id = <0x0>;
/rk3399_ARM-atf/docs/components/spd/
H A Dtrusty-dispatcher.rst14 Custom boot parameters can be passed to Trusty by providing a platform
22 size allocated to trusty. If the platform does not provide this
25 can be set to a platform specific parameter block, and ``args->arg2``
/rk3399_ARM-atf/docs/plat/arm/
H A Darm-build-options.rst21 BL2 calls the platform specific function `arm_bl2_el3_plat_config_load`.
29 platform setup hook at BL1 and disabled in the BL1 prepare exit hook. The
43 - ``ARM_PLAT_MT``: This flag determines whether the Arm platform layer has to
50 platform’s ``platform.mk`` to indicate that the platform supplies its own
52 in ``plat/arm/common/`` is omitted, and the platform must add its own
60 in which case the platform is configured to expect NULL in the State-ID
114 For a better understanding of these options, the Arm development platform memory
146 utilize when building for the FVP platform. This option defaults to 256 with
161 - ``NRD_CHIP_COUNT``: Configures the number of chips on a Neoverse RD platform
163 valid value greater than 1, the platform code performs required configuration
[all …]
/rk3399_ARM-atf/docs/process/
H A Dplatform-ports-policy.rst4 This document clarifies a couple of policy points around platform ports
16 platform compatibility, which means the previous interface needs to be deprecated
23 to upstream their platform code or copy the latest version of the code being
38 If a platform, driver or library interface is no longer maintained, it is best
50 platform ports (or soon to be) to this day.
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A Dporting.rst11 - The customer platform specific code shall reside under ``plat/marvell/armada/<soc family>/<soc>_c…
13 - The platform name for build purposes is called ``<soc>_cust`` (e.g. ``a7040_cust``).
15 files from the customer platform directory.
93 Each supported platform of the TF-A has its own DDR porting file called
94 dram_port.c located at ``atf/plat/marvell/armada/a8k/<platform>/board`` directory.
99 The build target directory is "build/<platform>/release/ble".
127 family>/<platform>/board/phy-porting-layer.h``. If the phy-porting-layer.h
136 existing example to a new platform:
138 …8k/a80x0/board/phy-porting-layer.h`` "plat/marvell/armada/<soc family>/<platform>/board/phy-portin…
151 If there is no PHY porting layer for new platform (missing
/rk3399_ARM-atf/docs/about/
H A Dmaintainers.rst543 Allwinner ARMv8 platform port
553 Amlogic Meson S905 (GXBB) platform port
561 Amlogic Meson S905x (GXL) platform port
568 Amlogic Meson S905X2 (G12A) platform port
575 Amlogic Meson A113D (AXG) platform port
582 Arm FPGA platform port
627 Arm Reference Design platform ports
636 :|F|: plat/arm/board/neoverse_rd/platform/rdn2/
637 :|F|: plat/arm/board/neoverse_rd/platform/rdv3/
639 Arm Total Compute platform port
[all …]
/rk3399_ARM-atf/docs/perf/
H A Dtsp.rst17 make PLAT=<platform> SPD=tspd all
23 build/<platform>/<build-type>/bl32.bin
/rk3399_ARM-atf/plat/arm/board/morello/fdts/
H A Dmorello_nt_fw_config.dts13 * Place holder for platform-info node with default values.
17 platform-info {
/rk3399_ARM-atf/plat/qti/msm8939/
H A Dplatform.mk11 include plat/qti/msm8916/platform.mk
/rk3399_ARM-atf/plat/arm/board/neoverse_rd/platform/rdn2/fdts/
H A Drdn2_nt_fw_config.dts14 * value of platform-id and config-id will be set to the
18 platform-id = <0x0>;
/rk3399_ARM-atf/docs/plat/nxp/
H A Dnxp-layerscape.rst22 The LX2160A reference design board provides a comprehensive platform
46 and development platform that supports industrial IoT applications, human
70 development platform that supports the Layerscape LS1043A architecture
111 evaluation, and development platform that supports the Layerscape LS1046A
121 and development platform that supports the LS1046A architecture processor
143 The LS1088A reference design board provides a comprehensive platform that
150 Table of supported boot-modes by each platform & platform that needs FIP-DDR:
211 …2GB belongs to DRAM1 and following banks, and size of DRAMn Bank varies for one platform to others.
266 For u-boot you can use the <platform>_tfa_defconfig for build.
268 - Copy/clone the repo "ddr-phy-binary" to the tfa directory for platform needing ddr-fip.
[all …]
/rk3399_ARM-atf/plat/qti/msm8909/
H A Dplatform.mk13 include plat/qti/msm8916/platform.mk

12345678