Home
last modified time | relevance | path

Searched refs:initialized (Results 1 – 25 of 28) sorted by relevance

12

/arm-trusted-firmware-2.8.0/include/lib/xlat_tables/
A Dxlat_tables_v2_helpers.h106 bool initialized; member
174 .initialized = false, \
/arm-trusted-firmware-2.8.0/lib/xlat_mpu/
A Dxlat_mpu_core.c262 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()
/arm-trusted-firmware-2.8.0/lib/xlat_tables_v2/
A Dxlat_tables_core.c788 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()
A Dxlat_tables_context.c142 assert(tf_xlat_ctx.initialized == true); in xlat_make_tables_readonly()
A Dxlat_tables_utils.c358 assert(ctx->initialized); in xlat_get_mem_attributes_internal()
453 assert(ctx->initialized); in xlat_change_mem_attributes_ctx()
/arm-trusted-firmware-2.8.0/plat/brcm/board/stingray/driver/
A Dusb_phy.c482 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()
/arm-trusted-firmware-2.8.0/plat/brcm/board/stingray/include/
A Dusb_phy.h224 uint32_t initialized; member
/arm-trusted-firmware-2.8.0/docs/plat/
A Dintel-agilex.rst81 INFO: ARM GICv2 driver initialized
A Dintel-stratix10.rst88 INFO: ARM GICv2 driver initialized
A Dqti-msm8916.rst93 INFO: ARM GICv2 driver initialized
A Drz-g2.rst175 INFO: ARM GICv2 driver initialized
/arm-trusted-firmware-2.8.0/docs/security_advisories/
A Dsecurity-advisory-tfv-5.rst44 bits with an architecturally UNKNOWN reset value should be initialized to
/arm-trusted-firmware-2.8.0/docs/components/fconf/
A Dindex.rst95 after the io layer is initialized, as the |DTB| is stored on an external
/arm-trusted-firmware-2.8.0/docs/design_documents/
A Dcontext_mgmt_rework.rst69 is maintained in the CPU Context. Once the context is initialized the
104 initialized by invoking context management library APIs which then initialize
/arm-trusted-firmware-2.8.0/docs/getting_started/
A Drt-svc-writers-guide.rst152 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
A Dpsci-lib-integration-guide.rst163 - The C runtime environment must be setup and stack initialized
280 initialized and enabled. The major actions performed by this function are:
A Dporting-guide.rst1057 be invoked by BL31 after the power domain topology is initialized and can
1322 environment is initialized.
2129 that EL3 architectural and platform state is completely initialized. It
3472 abstraction layer. These drivers then need to be initialized by bootloader
/arm-trusted-firmware-2.8.0/docs/components/
A Dxlat-tables-lib-v2-design.rst135 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
A Darm-sip-service.rst396 w0 == DEBUGFS_E_INVALID_PARAMS if already initialized,
A Dgranule-protection-tables-design.rst149 are then added to the L1 PAS regions to be initialized in the next step and
A Dsecure-partition-manager.rst686 - 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
968 When the SPMC boots, all secure partitions are initialized on their primary
1503 S-EL0 partitions are presented, loaded and initialized the same as S-EL1 VMs by
A Del3-spmc.rst393 When the SPMC boots, secure partition is initialized on its primary
A Drmm-el3-comms-spec.rst135 At warm boot, RMM is already initialized and only some per-CPU initialization
/arm-trusted-firmware-2.8.0/docs/plat/arm/fvp/
A Dindex.rst135 details on HW_CONFIG. By default, this is initialized to a sensible DTS
/arm-trusted-firmware-2.8.0/docs/design/
A Dfirmware-design.rst446 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,
1532 corresponding sections need to be allocated and initialized at run-time.

Completed in 41 milliseconds

12