| /rk3399_ARM-atf/lib/libfdt/ |
| H 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
407 memmove(new + mem_rsv_off, old + fdt_off_mem_rsvmap(old), mem_rsv_size); in fdt_packblocks_()
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_()
[all …]
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | acknowledgements.rst | 8 directly into the copyright notices, this file is not relevant for new
10 use for new contributions.
|
| H A D | lts.rst | 13 | | | sections. Introduce a new section documenting a day |
30 | 2025-03-27 | Chris Palmer | Playbook for making a new release. |
45 Also, the European Cyber Resilience Act (CRA) is a new EU legislation that mandates
204 on TF-A 2.8. This means new features going in 2.8 won’t go in the LTS branch.
223 be TFTF LTS 2.8.0 in Feb 2023, 2.8.1 (if new TFTF tests need to be added for
270 Playbook for new releases
272 To make a new minor release (e.g. 2.x.y → 2.x.y+1), follow these steps.
277 lts-2.12, etc.). It contains a list of patches to be cherry-picked into a new
283 #. For the version 2.x for which you want to create a new release, open its CSV
300 #. The AllowCI+2 job runs automatically on each LTS branch once a new
|
| H A D | features.rst | 141 - Ongoing support for new architectural features, CPUs and System IP.
143 - Ongoing support for new Arm system architecture specifications.
|
| /rk3399_ARM-atf/lib/debugfs/ |
| H 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()
|
| /rk3399_ARM-atf/plat/qemu/qemu_sbsa/ |
| H A D | sbsa_platform.c | 295 fdt64_t new[2]; in set_system_memory_base() local
382 new[0] = cpu_to_fdt64(new_base); in set_system_memory_base()
383 new[1] = cpu_to_fdt64(new_size); in set_system_memory_base()
385 ret = fdt_setprop(dtb, node, "reg", new, len); in set_system_memory_base()
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | platform-ports-policy.rst | 17 and a new interface introduced to replace it. In case the migration to the new
19 effort to migrate the upstream platforms to the new interface.
|
| H A D | commit-style.rst | 60 | ``feat`` | A new feature |
103 to be deprecated, and should be avoided. If you are adding a new component that
107 greatest new platform `Bar` then you would add it to the `Platforms` changelog
122 When creating new scopes, try to keep them short and succinct, and use kebab
|
| H A D | code-review-guidelines.rst | 59 are, the more quickly new patches can be reviewed and merged. Contributing to
134 - It leverages existing interfaces rather than introducing new ones
140 increase the attack surface (e.g. new SMCs) without justification.
167 answer back if needed and review new revisions of their patch.
216 - Generally speaking, new driver code should be placed in the generic
|
| H A D | coding-style.rst | 52 prevent the addition of new ones.
137 is **not** placed on a new line.
149 style, **do** place the opening brace on a new line.
479 is discouraged for new definitions as it makes it difficult for TF to comply
483 The Linux coding standards also discourage new typedefs and checkpatch emits
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | ven-el3-service.rst | 69 - VEN_EL3_SVC_VERSION_MINOR is incremented when we add a new FID or a new sub service.
70 For example adding an new monitor service at 0x30, Debugfs starts at 0x10 and PMF
|
| H 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 can be used
71 RMMD is a new standard runtime service that handles the switch to the Realm
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | cmake_framework.rst | 13 This document presents a proposal for a new buildsystem for TF-A using CMake,
19 to maintain, there is a need for a new, more flexible solution. The proposal is
20 to use CMake language for the new buildsystem. The main reasons of this decision
42 other embedded projects too, it is beneficial to collect the new code into a
|
| /rk3399_ARM-atf/docs/plat/arm/arm_fpga/ |
| H 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
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-internals.rst | 20 in future when Secure/Realm wants to use FFH then they can introduce new macros
|
| H 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
|
| H A D | docs-build.rst | 26 existing ``.dia`` diagram files, or create new ones.
97 Type ``exit`` to deactivate the virtual environment and exit this new shell. For
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 12 As the TF-A codebase evolves and new features get added, these threat model
|
| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 4 The Arm architecture evolves through versioning, with new architectural features being introduced
483 Adding support for a new feature
494 The following is a checklist with guidance on what to do to add a new feature,
575 involvement (eg. whether a new instruction that cannot trap works).
|
| /rk3399_ARM-atf/docs/resources/diagrams/plantuml/ |
| H A D | tfa_arm_cca_dfd.puml | 77 # -- The following lines are new for Arm CCA DFD.
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | intel-agilex.rst | 22 - UEFI (to be updated with new upstreamed UEFI):
|
| H A D | intel-stratix10.rst | 22 - UEFI (to be updated with new upstreamed UEFI):
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H 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
|
| /rk3399_ARM-atf/docs/plat/arm/juno/ |
| H 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
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | console-framework.rst | 10 will need to be written for the new UART in TF-A. Current supported UARTs are:
29 already been written before writing a new one.
65 skeleton_console.S``, this skeleton sets the rules for writing a new console_driver.
266 that are registered with this new state (scope). For example, calling
|