| /arm-trusted-firmware-2.8.0/lib/libfdt/ |
| A D | fdt_rw.c | 131 char *new; in fdt_find_add_string_() local
143 new = strtab + fdt_size_dt_strings(fdt); in fdt_find_add_string_()
151 memcpy(new, s, len); in fdt_find_add_string_()
152 return (new - strtab); in fdt_find_add_string_()
396 static void fdt_packblocks_(const char *old, char *new, in fdt_packblocks_() argument
408 fdt_set_off_mem_rsvmap(new, mem_rsv_off); in fdt_packblocks_()
410 memmove(new + struct_off, old + fdt_off_dt_struct(old), struct_size); in fdt_packblocks_()
411 fdt_set_off_dt_struct(new, struct_off); in fdt_packblocks_()
412 fdt_set_size_dt_struct(new, struct_size); in fdt_packblocks_()
415 fdt_set_off_dt_strings(new, strings_off); in fdt_packblocks_()
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/about/ |
| A D | acknowledgements.rst | 8 directly into the copyright notices, this file is not relevant for new
10 use for new contributions.
|
| A D | features.rst | 92 new standard service.
114 - Ongoing support for new architectural features, CPUs and System IP.
116 - Ongoing support for new Arm system architecture specifications.
|
| /arm-trusted-firmware-2.8.0/lib/debugfs/ |
| A D | dev.c | 17 chan_t *new; member
201 channel = mp->new; in mount_point_to_channel()
725 static int add_mount_point(chan_t *channel, const char *new) in add_mount_point() argument
731 if (new == NULL) { in add_mount_point()
735 cn = path_to_channel(new, O_READ); in add_mount_point()
746 if (mp->new == NULL) { in add_mount_point()
755 mp->new = cn; in add_mount_point()
769 int bind(const char *old, const char *new) in bind() argument
778 if (add_mount_point(channel, new) < 0) { in bind()
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | platform-ports-policy.rst | 15 means the previous interface needs to be deprecated and a new interface
16 introduced to replace it. In case the migration to the new interface is trivial,
18 upstream platforms to the new interface.
|
| A D | commit-style.rst | 57 | ``feat`` | A new feature |
100 to be deprecated, and should be avoided. If you are adding a new component that
104 greatest new platform `Bar` then you would add it to the `Platforms` changelog
119 When creating new scopes, try to keep them short and succinct, and use kebab
|
| A D | code-review-guidelines.rst | 38 are, the more quickly new patches can be reviewed and merged. Contributing to
105 - It leverages existing interfaces rather than introducing new ones
111 increase the attack surface (e.g. new SMCs) without justification.
138 answer back if needed and review new revisions of their patch.
187 - Generally speaking, new driver code should be placed in the generic
|
| A D | coding-style.rst | 52 and to prevent the addition of new ones.
134 is **not** placed on a new line.
146 style, **do** place the opening brace on a new line.
455 is discouraged for new definitions as it makes it difficult for TF to comply
459 The Linux coding standards also discourage new typedefs and checkpatch emits
|
| A D | contributing.rst | 54 - If you are submitting new files that you intend to be the code owner for
55 (for example, a new platform port), then also update the
174 new files under your platform, they are covered under the following two sections:
184 - When you submit your patches for review containing new source files, please
188 - In this section you find the details on how to append your new build
|
| A D | security.rst | 12 at the bottom of this page. Any new ones will, additionally, be announced as
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/arm_fpga/ |
| A D | index.rst | 5 testing and bringup of new cores. With that focus, peripheral support is
16 as a template for a minimal new (and possibly DT-based) platform port.
32 internal list, but for new or experimental cores this creates a lot of
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | cmake_framework.rst | 13 This document presents a proposal for a new buildsystem for TF-A using CMake,
23 to maintain, there is a need for a new, more flexible solution. The proposal is
24 to use CMake language for the new buildsystem. The main reasons of this decision
46 other embedded projects too, it is beneficial to collect the new code into a
|
| A D | context_mgmt_rework.rst | 18 of a new Realm world and a separate Root world for EL3 firmware, it is clear
116 current functions can be retained in the lib and perhaps define new ones for
174 The new sequence for world switch including Root world context would
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | image-terminology.rst | 10 - Some of the names and abbreviated names have changed to accommodate new
26 new form is to just omit the dash and not use subscript formatting.
97 but new 3rd level images should be suffixed with an underscore followed by text
175 to load a new set of firmware images from an external interface and write them
|
| A D | docs-build.rst | 38 existing ``.dia`` diagram files, or create new ones.
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | intel-agilex.rst | 22 - UEFI (to be updated with new upstreamed UEFI):
|
| A D | intel-stratix10.rst | 22 - UEFI (to be updated with new upstreamed UEFI):
|
| A D | synquacer.rst | 44 - Secondly, create a new working directory and store the absolute path to this
|
| /arm-trusted-firmware-2.8.0/docs/components/fconf/ |
| A D | index.rst | 14 It is used to bridge new and old ways of providing platform-specific data.
114 sub-namespaces. The following concepts should be considered when adding new
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | trusted-board-boot-build.rst | 59 generation of the new hash if ``ROT_KEY`` is specified.
63 generation of the new hash if ``ROT_KEY`` is specified.
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/juno/ |
| A D | index.rst | 89 #. Build TF-A images and create a new FIP for FVP
99 #. Build TF-A images and create a new FIP for Juno
171 The new images must be programmed in flash memory by adding
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | realm-management-extension.rst | 26 RME adds Root and Realm Physical address spaces. To support this, two new
33 Only version 2 of the translation tables library supports the new memory
38 A new CPU context for the Realm world has been added. The existing
72 RMMD is a new standard runtime service that handles the switch to the Realm
|
| A D | xlat-tables-lib-v2-design.rst | 42 Therefore, it is recommended to use version 2, especially for new platform
75 might create new translation tables, update or split existing ones.
99 modified to point to this new level-3 table. This has a performance cost at
273 the new region will overlap another one in an invalid way, or if any other
389 order of all regions at all times. As each new region is mapped, existing
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | porting.rst | 136 existing example to a new platform:
151 If there is no PHY porting layer for new platform (missing
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | index.rst | 54 for porting the software to a new platform.
|