Searched refs:running (Results 1 – 25 of 40) sorted by relevance
12
13 bool "TI K3 based AM625 EVM running on A53"19 bool "TI K3 based AM625 EVM running on R5"30 bool "PHYTEC phyCORE-AM62x running on A53"37 bool "PHYTEC phyCORE-AM62x running on R5"49 bool "Toradex Verdin AM62 running on A53"56 bool "Toradex Verdin AM62 running on R5"
13 bool "TI K3 based J784S4 EVM running on A72"20 bool "TI K3 based J784S4 EVM running on R5"31 bool "TI K3 based J742S2 EVM running on A72"38 bool "TI K3 based J742S2 EVM running on R5"
13 bool "TI K3 based J722S EVM running on A53"19 bool "TI K3 based J722S EVM running on R5"30 bool "BeagleBoard.org BeagleY-AI running on A53"36 bool "BeagleBoard.org BeagleY-AI running on R5"
13 bool "TI K3 based AM642 EVM running on A53"21 bool "TI K3 based AM642 EVM running on R5"33 bool "PHYTEC phyCORE-AM64x running on A53"41 bool "PHYTEC phyCORE-AM64x running on R5"
13 bool "TI K3 based AM62A7 EVM running on A53"22 bool "TI K3 based AM62A7 EVM running on R5"34 bool "PHYTEC phyCORE-AM62Ax running on A53"43 bool "PHYTEC phyCORE-AM62Ax running on R5"
13 bool "TI K3 based AM654 EVM running on A53"22 bool "TI K3 based AM654 EVM running on R5"32 bool "IOT2050 running on A53"
7 /* When running as a first-stage bootloader this isn't filled in automatically */14 * When running as a first-stage bootloader, we need to re-configure the UART pins
4 /* When running as a first-stage bootloader this isn't filled in automatically */
60 * operations will fail as SYSFW is not yet up and running.106 * have the firmware running at this point. Delete the120 * have the firmware running at this point. Delete the
5 * After building u-boot, can generate the SPKG output by running:
6 /* When running as the primary bootloader there is no prior
46 adi,phy-output-clock = "125mhz-free-running";
18 * FIXME: Currently only the SPL running on the R5 has a clock
89 * operations will fail as SYSFW is not yet up and running.
84 * operations will fail as SYSFW is not yet up and running.
13 bool "TI K3 based AM62P5 EVM running on A53"19 bool "TI K3 based AM62P5 EVM running on R5"
13 bool "TI K3 based J7200 EVM running on A72"21 bool "TI K3 based J7200 EVM running on R5"
13 bool "TI K3 based J721S2 EVM running on A72"21 bool "TI K3 based J721S2 EVM running on R5"
13 bool "TI K3 based J721E EVM running on A72"21 bool "TI K3 based J721E EVM running on R5"
64 bool running; member523 sdl.running = false; in sandbox_sdl_sound_init()552 if (!sdl.running) { in sandbox_sdl_sound_play()554 sdl.running = true; in sandbox_sdl_sound_play()563 if (sdl.running) { in sandbox_sdl_sound_stop()568 sdl.running = 0; in sandbox_sdl_sound_stop()
20 The value, in Hz, that the CPU clock is running at.
3 * Other devicetree file for running sandbox tests
44 bool running; member
14 Say N here if you are running out of code space in the image32 precise, by default (if there is EL2/EL3 firmware running)39 bool "Enable switching to running in EL1"41 In some circumstances we need to switch to running in EL1.
70 when running test suites like the UEFI self certification test which
Completed in 35 milliseconds