Home
last modified time | relevance | path

Searched full:brom (Results 1 – 21 of 21) sorted by relevance

/OK3568_Linux_fs/u-boot/arch/arm/include/asm/arch-sunxi/
H A Dsys_proto.h16 /* return_to_fel() - Return to BROM from SPL
18 * This returns back into the BROM after U-Boot SPL has performed its initial
21 * @lr: BROM link register value (return address)
22 * @sp: BROM stack pointer
/OK3568_Linux_fs/u-boot/arch/arm/include/asm/arch-rockchip/
H A Dbootrom.h21 * Transfer control back to the Rockchip BROM, restoring necessary
22 * register context and passing a command/result code to the BROM
38 BROM_BOOT_ENTER_DNL, /* have BROM enter download-mode */
44 * Boot-device identifiers as used by the BROM
H A Dboot0.h37 mov r0, #0 /* return 0 to the BROM to signal 'OK' */
38 bx lr /* return control to the BROM */
/OK3568_Linux_fs/u-boot/arch/arm/mach-rockchip/
H A DKconfig730 bool "SPL requires early-return (for RK3188-style BROM) to BROM"
733 Some Rockchip BROM variants (e.g. on the RK3188) load the
736 first and entered; after returning to the BROM, the
737 remainder of the first stage is loaded, but the BROM
744 bool "TPL requires early-return (for RK3188-style BROM) to BROM"
747 Some Rockchip BROM variants (e.g. on the RK3188) load the
750 first and entered; after returning to the BROM, the
751 remainder of the first stage is loaded, but the BROM
H A Dbootrom.c65 * All Rockchip BROM implementations enter with a valid stack-pointer,
91 * To instruct the BROM to boot the next stage, we in save_boot_params()
99 * A non-zero return value will instruct the BROM enter in save_boot_params()
H A Dspl-boot-order.c129 * before us' (either a BROM or TPL stage) and map the info retrieved onto
H A Dboot_rkimg.c344 /* try rockusb download and brom download */ in setup_download_mode()
/OK3568_Linux_fs/u-boot/board/sunxi/
H A DREADME.sunxi649 code from the Boot ROM (BROM). As this has some implications on U-Boot, this
61 The on-die BROM code will try several methods to load and execute the firmware.
65 BROM finds the magic "eGON" header in the first bytes, it will execute that
71 it (using the CS0 pin). If a flash chip is found, the BROM will load the
H A DREADME.nand15 creating our images. However, the BROM will use a quite weird pattern
/OK3568_Linux_fs/u-boot/test/rockchip/
H A Dtest-download.c59 UNIT_CMD_ATTR_DEFINE(brom, 0, CMD_FLG_NORETURN),
74 " [n] rktest brom - test bootrom, enter download mode\n"
/OK3568_Linux_fs/u-boot/arch/arm/mach-sunxi/
H A Dboard.c216 /* The sunxi internal brom will try to loader external bootloader
231 * valid bootable SD card image (because the BROM would refuse to in spl_boot_device()
235 * the FEL code in the BROM to wait and receive the main u-boot in spl_boot_device()
H A Dspl_spi_sunxi.c105 * Setup 6 MHz from OSC24M (because the BROM is doing the same).
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sram/
H A Dsram.yaml251 // value is set at a specific location. If it is then the BROM will jump
265 // This is checked by BROM to determine if
/OK3568_Linux_fs/u-boot/tools/
H A Dmksunxiboot.c55 * BROM (at least on A10 and A20) requires NAND-images to be explicitly aligned
/OK3568_Linux_fs/kernel/drivers/usb/mtu3/
H A Dmtu3_plat.c206 * device ip may be powered on in firmware/BROM stage before entering in ssusb_ip_sw_reset()
/OK3568_Linux_fs/u-boot/spl/arch/arm/cpu/armv8/
H A D.start.o.cmd
/OK3568_Linux_fs/u-boot/tpl/arch/arm/cpu/armv8/
H A D.start.o.cmd
/OK3568_Linux_fs/u-boot/arch/arm/cpu/armv8/
H A D.start.o.cmd
/OK3568_Linux_fs/u-boot/tpl/arch/arm/mach-rockchip/
H A D.tpl.o.cmd
/OK3568_Linux_fs/u-boot/spl/arch/arm/mach-rockchip/
H A D.spl.o.cmd
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dsun9i-a80.dtsi313 * This is checked by BROM to determine if