| /trusted-firmware-a-3.6.0-3.5.0/tools/conventional-changelog-tf-a/ |
| D | index.js | 56 const flattenSections = function (sections) { argument
57 return sections.flatMap(section => {
58 const subsections = flattenSections(section.sections || []);
64 const flattenedSections = flattenSections(config.sections);
71 const generateTemplateData = function (sections, notes) { argument
72 return (sections || []).flatMap(section => {
75 sections: generateTemplateData(section.sections, notes),
82 if ((templateData.sections.length == 0) && (templateData.notes.length == 0)) {
93 sections: generateTemplateData(config.sections, noteGroup.notes),
105 const generateTemplateData = function (sections, commits) { argument
[all …]
|
| /trusted-firmware-a-3.6.0-3.5.0/ |
| D | .versionrc.js | 37 function getTypes(sections) { argument
38 return sections.map(section => {
59 const types = getTypes(changelog.sections);
60 const sections = getSections(changelog.subsections);
71 "sections": sections, property in module.exports.preset
|
| D | .commitlintrc.js | 34 function getTypes(sections) { argument
35 return sections.map(section => section.type)
47 const types = getTypes(changelog.sections).sort(); /* Sort alphabetically */
|
| D | Makefile | 436 -ffunction-sections -fdata-sections \
464 TF_LDFLAGS += -Wl,--gc-sections
488 TF_LDFLAGS += --gc-sections
|
| /trusted-firmware-a-3.6.0-3.5.0/tools/conventional-changelog-tf-a/templates/ |
| D | note-section.hbs | 9 {{#if sections.length ~}}
10 {{#each sections ~}}
|
| D | commit-section.hbs | 11 {{#if sections.length ~}}
12 {{#each sections ~}}
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/rockchip/rk3399/drivers/m0/ |
| D | Makefile | 37 CFLAGS := -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common
39 LDFLAGS := -Wl,--gc-sections -Wl,--build-id=none
|
| /trusted-firmware-a-3.6.0-3.5.0/lib/romlib/ |
| D | Makefile | 34 LDFLAGS := --gc-sections -O1
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/nvidia/tegra/scat/ |
| D | bl31.scat | 81 /* Place pubsub sections for events */
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/design_documents/ |
| D | psci_osi_mode.rst | 143 See sections 5.1.14 and 5.15 of the PSCI spec (DEN0022D.b) for more details.
180 See sections 5.1.19 and 5.20 of the PSCI spec (DEN0022D.b) for more details.
215 See sections 5.1.2 and 5.4 of the PSCI spec (DEN0022D.b) for more details.
267 See sections 4.2.3.2, 6.2, and 6.3 of the PSCI spec (DEN0022D.b) for more
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/design/ |
| D | firmware-design.rst | 77 The sections below provide the following details:
160 path as described in the following sections.
659 BL31 zero-init sections (e.g. ``.bss``) should not contain valid data on entry,
848 The following sections describe the framework which facilitates the
919 call handling functions are provided in the following sections.
1526 sections;
1531 corresponding sections need to be allocated and initialized at run-time.
1532 In the ELF terminology, they are called ``NOBITS`` sections.
1534 All PROGBITS sections are grouped together at the beginning of the image,
1535 followed by all NOBITS sections. This is true for all TF-A images and it is
[all …]
|
| D | reset-design.rst | 22 configuration, some of these steps might be unnecessary. The following sections
|
| D | trusted-board-boot.rst | 201 described in the following sections.
|
| D | interrupt-framework-design.rst | 83 following sub-sections describe all the possible routing models and specify
88 sub-sections is explained below.
217 #. Interrupt management: the following sections describe how interrupts are
|
| D | cpu-specific-build-macros.rst | 116 sections.
124 <= r0p4. This workaround can lead the linker to emit ``*.stub`` sections
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/getting_started/ |
| D | build-options.rst | 69 the RW sections in RAM, while leaving the RO sections in place. This option
831 sections of BL31 (.bss, stacks, page tables, and coherent memory) to be
835 sections are placed in RAM immediately following the loaded firmware image.
838 NOLOAD sections of BL2 (.bss, stacks, page tables) to be allocated in RAM
841 flag is disabled by default and NOLOAD sections are placed in RAM immediately
|
| D | rt-svc-writers-guide.rst | 125 the following sections.
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/components/ |
| D | ras.rst | 261 As mentioned in earlier sections, RAS framework interacts with the |EHF| to
|
| D | rmm-el3-comms-spec.rst | 17 The below sections discuss these interfaces more in detail.
|
| D | secure-partition-manager.rst | 88 on sections mandated as implementation-defined in the specification.
519 Also refer to `Describing secure partitions`_ and `TF-A build options`_ sections.
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/process/ |
| D | coding-style.rst | 4 The following sections outline the |TF-A| coding style for *C* code. The style
|
| D | contributing.rst | 174 new files under your platform, they are covered under the following two sections:
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/threat_model/ |
| D | threat_model_el3_spm.rst | 74 The following sections define:
|
| D | threat_model_spm.rst | 96 The following sections define:
338 | | SPMC code/data sections. |
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/ |
| D | porting-guide.rst | 37 discusses these in detail. The subsequent sections discuss the remaining
82 page boundary (4K) for each BL stage. All sections which allocate coherent
98 The ``.coherent_ram`` section is a sum of all sections like ``.bakery_lock`` which are
541 Defines the maximum address in secure RAM that the BL31's progbits sections
546 Defines the maximum address that the TSP's progbits sections can occupy.
|
