Searched refs:initialized (Results 1 – 25 of 27) sorted by relevance
12
| /trusted-firmware-a-3.4.0/include/lib/xlat_tables/ |
| D | xlat_tables_v2_helpers.h | 106 bool initialized; member
174 .initialized = false, \
|
| /trusted-firmware-a-3.4.0/lib/xlat_mpu/ |
| D | xlat_mpu_core.c | 262 assert(!ctx->initialized); in mmap_add_region_ctx()
323 assert(!ctx->initialized); in init_xlat_tables_ctx()
364 ctx->initialized = true; in init_xlat_tables_ctx()
|
| /trusted-firmware-a-3.4.0/lib/xlat_tables_v2/ |
| D | xlat_tables_core.c | 788 assert(!ctx->initialized); in mmap_add_region_ctx()
1003 if (ctx->initialized) { in mmap_add_dynamic_region_ctx()
1118 if (ctx->initialized) { in mmap_remove_dynamic_region_ctx()
1183 ctx->initialized = 0; in xlat_setup_dynamic_ctx()
1191 assert(!ctx->initialized); in init_xlat_tables_ctx()
1241 ctx->initialized = true; in init_xlat_tables_ctx()
|
| D | xlat_tables_context.c | 142 assert(tf_xlat_ctx.initialized == true); in xlat_make_tables_readonly()
|
| D | xlat_tables_utils.c | 358 assert(ctx->initialized); in xlat_get_mem_attributes_internal()
453 assert(ctx->initialized); in xlat_change_mem_attributes_ctx()
|
| /trusted-firmware-a-3.4.0/plat/brcm/board/stingray/driver/ |
| D | usb_phy.c | 482 if (phy_info->initialized != 0U) { in usb_info_fill()
533 phy_info->initialized = !status; in usb_phy_init()
544 phy_info->initialized = 0U; in usb_phy_shutdown()
|
| /trusted-firmware-a-3.4.0/plat/brcm/board/stingray/include/ |
| D | usb_phy.h | 224 uint32_t initialized; member
|
| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | intel-agilex.rst | 81 INFO: ARM GICv2 driver initialized
|
| D | intel-stratix10.rst | 88 INFO: ARM GICv2 driver initialized
|
| D | qti-msm8916.rst | 93 INFO: ARM GICv2 driver initialized
|
| D | rz-g2.rst | 175 INFO: ARM GICv2 driver initialized
|
| /trusted-firmware-a-3.4.0/docs/security_advisories/ |
| D | security-advisory-tfv-5.rst | 44 bits with an architecturally UNKNOWN reset value should be initialized to
|
| /trusted-firmware-a-3.4.0/docs/components/fconf/ |
| D | index.rst | 95 after the io layer is initialized, as the |DTB| is stored on an external
|
| /trusted-firmware-a-3.4.0/docs/design_documents/ |
| D | context_mgmt_rework.rst | 69 is maintained in the CPU Context. Once the context is initialized the
104 initialized by invoking context management library APIs which then initialize
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | rt-svc-writers-guide.rst | 152 Runtime services are initialized once, during cold boot, by the primary CPU
173 If the service uses per-CPU data this must either be initialized for all CPUs
|
| D | psci-lib-integration-guide.rst | 163 - The C runtime environment must be setup and stack initialized
280 initialized and enabled. The major actions performed by this function are:
|
| D | porting-guide.rst | 829 be invoked by BL31 after the power domain topology is initialized and can
1094 environment is initialized.
1871 that EL3 architectural and platform state is completely initialized. It
3185 abstraction layer. These drivers then need to be initialized by bootloader
|
| D | build-options.rst | 854 :ref:`Firmware Design`). It can take the value 0 (BL32 is initialized using
855 synchronous method) or 1 (BL32 is initialized using asynchronous method).
|
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | xlat-tables-lib-v2-design.rst | 135 may be explicitly allocated and initialized using the
171 The default translation context is internally initialized using information
422 initialized its corresponding translation table entry to an invalid
|
| D | arm-sip-service.rst | 396 w0 == DEBUGFS_E_INVALID_PARAMS if already initialized,
|
| D | granule-protection-tables-design.rst | 149 are then added to the L1 PAS regions to be initialized in the next step and
|
| D | secure-partition-manager.rst | 686 - The first SP has initialized all its ECs in response to primary core boot up
689 - Other SPs have their first execution context initialized as a result of secure
962 When the SPMC boots, all secure partitions are initialized on their primary
1365 S-EL0 partitions are presented, loaded and initialized the same as S-EL1 VMs by
|
| D | rmm-el3-comms-spec.rst | 135 At warm boot, RMM is already initialized and only some per-CPU initialization
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/fvp/ |
| D | index.rst | 137 details on HW_CONFIG. By default, this is initialized to a sensible DTS
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | firmware-design.rst | 446 for entry into BL32 is not determined by BL2, it is initialized by the
609 once the runtime services are fully initialized. BL31 invokes such a
949 uses per-CPU data this must either be initialized for all CPUs during this call,
1531 corresponding sections need to be allocated and initialized at run-time.
|
12
