Searched hist:c48d0aef377385a3afd3fa41610c90dcc51d2d88 (Results 1 – 5 of 5) sorted by relevance
| /rk3399_ARM-atf/plat/qti/common/src/aarch64/ |
| H A D | qti_bl2_helpers.S | c48d0aef377385a3afd3fa41610c90dcc51d2d88 Thu Sep 25 07:30:06 UTC 2025 Sumit Garg <sumit.garg@oss.qualcomm.com> feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage
bootloader. Lets enable support for TF-A BL2 as the common reference
second stage bootloader which is able to support a variety of normal
world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI
platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS
|
--> BL32
As of now XBL is performing DRAM initialization and loads two set of
images for BL2 and FIP into DRAM from flash after performing secure boot
checks if enabled. Then BL2 does the FIP parsing from DRAM and loads
payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which
by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
|
| /rk3399_ARM-atf/plat/qti/common/src/ |
| H A D | qti_image_desc.c | c48d0aef377385a3afd3fa41610c90dcc51d2d88 Thu Sep 25 07:30:06 UTC 2025 Sumit Garg <sumit.garg@oss.qualcomm.com> feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage
bootloader. Lets enable support for TF-A BL2 as the common reference
second stage bootloader which is able to support a variety of normal
world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI
platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS
|
--> BL32
As of now XBL is performing DRAM initialization and loads two set of
images for BL2 and FIP into DRAM from flash after performing secure boot
checks if enabled. Then BL2 does the FIP parsing from DRAM and loads
payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which
by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
|
| H A D | qti_io_storage.c | c48d0aef377385a3afd3fa41610c90dcc51d2d88 Thu Sep 25 07:30:06 UTC 2025 Sumit Garg <sumit.garg@oss.qualcomm.com> feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage
bootloader. Lets enable support for TF-A BL2 as the common reference
second stage bootloader which is able to support a variety of normal
world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI
platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS
|
--> BL32
As of now XBL is performing DRAM initialization and loads two set of
images for BL2 and FIP into DRAM from flash after performing secure boot
checks if enabled. Then BL2 does the FIP parsing from DRAM and loads
payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which
by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
|
| H A D | qti_bl2_setup.c | c48d0aef377385a3afd3fa41610c90dcc51d2d88 Thu Sep 25 07:30:06 UTC 2025 Sumit Garg <sumit.garg@oss.qualcomm.com> feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage
bootloader. Lets enable support for TF-A BL2 as the common reference
second stage bootloader which is able to support a variety of normal
world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI
platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS
|
--> BL32
As of now XBL is performing DRAM initialization and loads two set of
images for BL2 and FIP into DRAM from flash after performing secure boot
checks if enabled. Then BL2 does the FIP parsing from DRAM and loads
payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which
by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
|
| /rk3399_ARM-atf/plat/qti/common/inc/ |
| H A D | qti_plat.h | c48d0aef377385a3afd3fa41610c90dcc51d2d88 Thu Sep 25 07:30:06 UTC 2025 Sumit Garg <sumit.garg@oss.qualcomm.com> feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage
bootloader. Lets enable support for TF-A BL2 as the common reference
second stage bootloader which is able to support a variety of normal
world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI
platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS
|
--> BL32
As of now XBL is performing DRAM initialization and loads two set of
images for BL2 and FIP into DRAM from flash after performing secure boot
checks if enabled. Then BL2 does the FIP parsing from DRAM and loads
payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which
by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
|