Home
last modified time | relevance | path

Searched refs:function (Results 1701 – 1725 of 2253) sorted by relevance

1...<<61626364656667686970>>...91

/ThreadX-v6.4.1/ports/cortex_m85/gnu/src/
Dtx_timer_interrupt.S77 .type _tx_timer_interrupt, function
/ThreadX-v6.4.1/ports/cortex_a8/ac5/src/
Dtx_thread_system_return.s120 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports_module/cortex_m33/ac6/module_manager/src/
Dtx_timer_interrupt.S72 .type _tx_timer_interrupt, function
/ThreadX-v6.4.1/ports_module/cortex_m33/gnu/module_manager/src/
Dtx_timer_interrupt.s72 .type _tx_timer_interrupt, function
/ThreadX-v6.4.1/ports/cortex_a9/ac5/src/
Dtx_thread_system_return.s120 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports/cortex_a7/ac5/src/
Dtx_thread_system_return.s120 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports/cortex_a5/iar/src/
Dtx_thread_system_return.s128 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports/cortex_a5/ac5/src/
Dtx_thread_system_return.s120 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports/cortex_a7/iar/src/
Dtx_thread_system_return.s126 BL _tx_execution_thread_exit ; Call the thread exit function
/ThreadX-v6.4.1/ports_module/cortex_m23/ac6/module_manager/src/
Dtx_timer_interrupt.S72 .type _tx_timer_interrupt, function
/ThreadX-v6.4.1/ports_module/cortex_m23/gnu/module_manager/src/
Dtx_timer_interrupt.S72 .type _tx_timer_interrupt, function
/ThreadX-v6.4.1/ports_arch/ARMv7-M/threadx/ghs/
Dreadme_threadx.txt34 observe the main function of sample_threadx.c.
57 After the Green Hills startup function returns, ThreadX initialization is
58 called. The main initialization function is _tx_initialize_low_level and
59 is located in the file tx_initialize_low_level.arm. This function is responsible
/ThreadX-v6.4.1/ports/cortex_a9/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/arm9/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_r5/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/arm11/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_a15/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_a8/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_a5/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_a7/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/cortex_r4/gnu/
Dreadme_threadx.txt47 to your application definition function, tx_application_define.
140 … timers in-line instead of using a function call. This
224 registers for each function. All other registers used by a C function must
225 be preserved by the function. ThreadX takes advantage of this in situations
227 (which is itself a C function). In such cases, the saved context of a thread
306 @ save function. */
334 @ save function. */
348 These function should be called between the IRQ context save and restore
429 These function should be called between the FIQ context save and restore
/ThreadX-v6.4.1/ports/arc_hs/metaware/src/
Dtx_thread_context_fast_restore.s74 .type _tx_thread_context_fast_restore, @function
85 bl.d _tx_execution_isr_exit ; Call the ISR exit function
/ThreadX-v6.4.1/ports_smp/arc_hs_smp/metaware/example_build/sample_threadx/
Dcrt1cl.s24 .type _start, @function
119 .type _exit_halt, @function
/ThreadX-v6.4.1/ports/cortex_a9/gnu/src/
Dtx_thread_context_restore.S101 .type _tx_thread_context_restore,function
/ThreadX-v6.4.1/ports_smp/cortex_a34_smp/ac6/src/
Dtx_thread_system_return.S71 .type _tx_thread_system_return, @function

1...<<61626364656667686970>>...91