Home
last modified time | relevance | path

Searched refs:step (Results 1 – 18 of 18) sorted by relevance

/arm-trusted-firmware-2.8.0/plat/brcm/board/stingray/driver/
A Dswreg.c244 uint32_t step, programmed_step; in set_swreg() local
259 step = B0_DDR_VDDC_STEP_VALUE(micro_volts); in set_swreg()
261 step = B0_STEP_VALUE(micro_volts); in set_swreg()
263 if ((step >> 8) != (programmed_step >> 8)) { in set_swreg()
264 ret = write_swreg_config(reg_id, PHY_REGC, step); in set_swreg()
/arm-trusted-firmware-2.8.0/include/drivers/allwinner/
A Daxp.h27 uint16_t step; member
/arm-trusted-firmware-2.8.0/drivers/allwinner/axp/
A Dcommon.c87 val = (mvolt / reg->step) - (reg->min_volt / reg->step); in setup_regulator()
/arm-trusted-firmware-2.8.0/docs/components/
A Dgranule-protection-tables-design.rst47 PAS region is configured. The first step is the level 0 table, each entry in the
49 descriptor), and the entire region can belong to a single PAS when a one step
52 step mapping. The type of mapping used for each PAS is determined by the user
74 the table creation step, a data structure containing information about the
77 runtime initialization step, the runtime firmware locates the existing tables in
149 are then added to the L1 PAS regions to be initialized in the next step and
/arm-trusted-firmware-2.8.0/plat/brcm/board/stingray/src/
A Dbl2_setup.c48 #define STEP_TO_UVOLTS(step) \ argument
49 ((MVOLT_BASE + (MVOLT_PER_STEP * (step))) * 1000)
/arm-trusted-firmware-2.8.0/docs/plat/nxp/
A Dnxp-ls-fuse-prov.rst139 - Caution: Donot proceed to the next step, until you are sure that OTPMK and SRKH are correctly blo…
140 -- After the next step, there is no turning back.
A Dnxp-layerscape.rst353 -- Next step is valid for platform where FIP-DDR is needed.
387 -- Next step is valid for platform that needs FIP-DDR.
/arm-trusted-firmware-2.8.0/plat/allwinner/common/
A Darisc_off.S29 # it hangs the whole system. So we skip this step for core 0.
/arm-trusted-firmware-2.8.0/docs/plat/
A Dwarp7.rst149 A further step is to sign BL2.
205 If you have HAB events @ step 6 - do not lock your board.
A Drpi3.rst404 5. Follow the instructions in `Setup SD card`_ except for the step of renaming
/arm-trusted-firmware-2.8.0/docs/design_documents/
A Dmeasured_boot_poc.rst87 the OP-TEE toolkit. On step 3, you need to get the manifest for FVP
94 Then proceed synching the repos as stated in step 3. Continue following
95 the instructions and stop before step 5.
136 (4) Now, you should be able to continue with step 5 in "`Get and build the solution`_"
148 After this step, you should be ready to run the image.
/arm-trusted-firmware-2.8.0/docs/getting_started/
A Ddocs-build.rst84 create the documentation is through a docker container. The first step is
A Dpsci-lib-integration-guide.rst58 #. Do step 5 of the cold boot call sequence described above.
A Dporting-guide.rst2041 If ``SCP_BL2U_BASE`` is not defined then this step is not performed.
/arm-trusted-firmware-2.8.0/docs/design/
A Dtrusted-board-boot.rst184 The next step is executed for all the boot loader images.
A Dinterrupt-framework-design.rst808 the secure CPU context (see step 3 above) in case the TSP had been preempted
A Dfirmware-design.rst163 This step only applies when ``PROGRAMMABLE_RESET_ADDRESS=0``. Refer to the
/arm-trusted-firmware-2.8.0/docs/
A Dchange-log.md4437 This step in the build process is skipped when running on a Windows host. A
4752 This step in the build process is skipped when running on a Windows host. A
5149 This step in the build process is skipped when running on a Windows host. A
5188 - DTB creation not supported when building on a Windows host. This step in the
5401 - DTB creation not supported when building on a Windows host. This step in the
5659 - DTB creation not supported when building on a Windows host. This step in the
6391 first step in the Trusted Board Boot process.

Completed in 45 milliseconds