Home
last modified time | relevance | path

Searched refs:remain (Results 1 – 8 of 8) sorted by relevance

/arm-trusted-firmware-2.8.0/drivers/renesas/common/emmc/
A Demmc_read.c90 uint32_t remain; in emmc_read_sector() local
113 remain = count; in emmc_read_sector()
114 while (remain != 0) { in emmc_read_sector()
115 trans_count = MIN_EMMC(remain, EMMC_RW_SECTOR_COUNT_MAX); in emmc_read_sector()
126 remain -= trans_count; in emmc_read_sector()
/arm-trusted-firmware-2.8.0/docs/process/
A Dcode-review-guidelines.rst60 explain why. Please remain courteous and do not abuse this.
/arm-trusted-firmware-2.8.0/docs/design/
A Dpsci-pd-tree.rst152 a core index should remain unchanged. Both Juno and FVP use a simple collision
A Dfirmware-design.rst518 In the last 2 cases, no part of BL2 needs to remain resident at
1716 remain valid only until execution reaches the EL3 Runtime Software entry
/arm-trusted-firmware-2.8.0/docs/components/
A Drmm-el3-comms-spec.rst69 images in the boot sequence and remain agnostic of any particular format used
/arm-trusted-firmware-2.8.0/docs/threat_model/
A Dthreat_model.rst675 | | remain enabled in release builds. See |
/arm-trusted-firmware-2.8.0/docs/getting_started/
A Dporting-guide.rst2760 = 1, data caches remain enabled throughout, and so there is no advantage to
/arm-trusted-firmware-2.8.0/docs/
A Dchange-log.md6652 fixed, some remain at the time of writing. These mainly seem to relate to a
6781 fixed, some remain at the time of writing. These mainly seem to relate to a

Completed in 27 milliseconds