Searched refs:prepare (Results 1 – 19 of 19) sorted by relevance
| /trusted-firmware-a-3.7.0/plat/intel/soc/common/drivers/sdmmc/ |
| D | sdmmc.c | 161 ret = ops->prepare(0, (uintptr_t)&scr, sizeof(scr)); in sdmmc_mmc_sd_switch()
251 ret = ops->prepare(0, (uintptr_t)&mmc_ext_csd, in sdmmc_fill_device_info()
356 ret = ops->prepare(0, (uintptr_t)&sd_switch_func_status, in sdmmc_sd_switch()
587 ret = ops->prepare(lba, buf, size); in sdmmc_read_blocks()
655 ret = ops->prepare(lba, buf, size); in sdmmc_write_blocks()
719 (ops_ptr->prepare != NULL) && in sd_or_mmc_init()
|
| /trusted-firmware-a-3.7.0/drivers/mmc/ |
| D | mmc.c | 172 ret = ops->prepare(0, (uintptr_t)&scr, sizeof(scr)); in mmc_sd_switch()
269 ret = ops->prepare(0, (uintptr_t)&mmc_ext_csd, in mmc_fill_device_info()
374 ret = ops->prepare(0, (uintptr_t)&sd_switch_func_status, in sd_switch()
600 ret = ops->prepare(lba, buf, size); in mmc_read_blocks()
668 ret = ops->prepare(lba, buf, size); in mmc_write_blocks()
835 (ops_ptr->prepare != NULL) && in mmc_init()
|
| /trusted-firmware-a-3.7.0/docs/resources/diagrams/plantuml/ |
| D | fconf_bl1_load_config.puml | 76 == load & auth, prepare and jump to BL2 ==
|
| /trusted-firmware-a-3.7.0/docs/plat/ |
| D | imx9.rst | 52 Details on how to prepare, generate & deploy the boot image be found in following documents:
|
| /trusted-firmware-a-3.7.0/include/drivers/ |
| D | mmc.h | 138 int (*prepare)(int lba, uintptr_t buf, size_t size); member
|
| /trusted-firmware-a-3.7.0/drivers/imx/usdhc/ |
| D | imx_usdhc.c | 31 .prepare = imx_usdhc_prepare,
|
| /trusted-firmware-a-3.7.0/docs/design/ |
| D | alt-boot-flows.rst | 75 without a BL33 and prepare to jump to a BL33 image loaded at address
|
| D | firmware-design.rst | 1058 the TSP to prepare for or respond to the power state change
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/juno/ |
| D | index.rst | 15 To run TF-A on Juno, you need to first prepare an SD card with Juno software
19 `Juno platform software user guide`_. Once you prepare the software stack
|
| /trusted-firmware-a-3.7.0/drivers/synopsys/emmc/ |
| D | dw_mmc.c | 134 .prepare = dw_prepare,
|
| /trusted-firmware-a-3.7.0/drivers/rpi3/sdhost/ |
| D | rpi3_sdhost.c | 31 .prepare = rpi3_sdhost_prepare,
|
| /trusted-firmware-a-3.7.0/docs/plat/marvell/armada/ |
| D | porting.rst | 135 The easiest way to prepare the PHY porting layer for custom board is to copy
|
| /trusted-firmware-a-3.7.0/drivers/st/mmc/ |
| D | stm32_sdmmc2.c | 152 .prepare = stm32_sdmmc2_prepare,
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/ |
| D | arm-build-options.rst | 23 platform setup hook at BL1 and disabled in the BL1 prepare exit hook. The
|
| /trusted-firmware-a-3.7.0/drivers/cadence/emmc/ |
| D | cdns_sdmmc.c | 61 .prepare = cdns_prepare,
|
| /trusted-firmware-a-3.7.0/docs/design_documents/ |
| D | context_mgmt_rework.rst | 54 EL3 can do the bare minimal EL2 init and init EL1 to prepare for EL3 exit.
|
| /trusted-firmware-a-3.7.0/docs/components/ |
| D | firmware-update.rst | 169 call to ``bl1_plat_get_image_desc()``. The same ID is also used to prepare the
|
| /trusted-firmware-a-3.7.0/docs/ |
| D | porting-guide.rst | 2691 Perform the platform specific actions to prepare to power off the calling CPU
2736 Perform the platform specific actions to prepare to suspend the calling
|
| D | change-log.md | 2509 …- prepare DLME data for DLME launch ([d42119c](https://review.trustedfirmware.org/plugins/gitiles/…
2510 …- prepare EL state during dynamic launch ([d1747e1](https://review.trustedfirmware.org/plugins/git…
6515 UNIPHIER_ROM_REGION_SIZE, prepare uniphier_soc_info() for next SoC, extend
|
