OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/arch/arc/core/thread_entry_wrapper.S

36 lines
600 B
ArmAsm
Raw Normal View History

First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
/*
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
* Copyright (c) 2014-2015 Wind River Systems, Inc.
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
* SPDX-License-Identifier: Apache-2.0
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*/
Fixed file description and applied doxygen style Removed old style file description and documnetation and apply doxygen synatx. Change-Id: I3ac9f06d4f574bf3c79c6f6044cec3a7e2f6e4c8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-04 23:09:39 +08:00
/**
* @file
* @brief Wrapper for _thread_entry
*
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
* Wrapper for _thread_entry routine when called from the initial context.
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*/
#include <toolchain.h>
linker: move all linker headers to include/linker Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-06-17 23:30:47 +08:00
#include <linker/sections.h>
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
GTEXT(_thread_entry_wrapper)
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
/*
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
* @brief Wrapper for _thread_entry
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
* The routine pops parameters for the _thread_entry from stack frame, prepared
* by the _new_thread() routine.
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*
doxygen: RETURNS: -> @return Previous comment style used RETRURNS:, use @return to comply with javadoc style. Change-Id: Ib1dffd92da1d97d60063ec5309b08049828f6661 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-07-02 05:29:04 +08:00
* @return N/A
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
*/
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
SECTION_FUNC(TEXT, _thread_entry_wrapper)
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
pop_s r3
pop_s r2
pop_s r1
pop_s r0
clarify use of term 'context' The term 'context' is vague and overloaded. Its usage for 'an execution context' is now referred as such, in both comments and some APIs' names. When the execution context can only be a fiber or a task (i.e. not an ISR), it is referred to as a 'thread', again in comments and everywhere in the code. APIs that had their names changed: - nano_context_id_t is now nano_thread_id_t - context_self_get() is now sys_thread_self_get() - context_type_get() is now sys_execution_context_type_get() - context_custom_data_set/get() are now sys_thread_custom_data_set/get() The 'context' prefix namespace does not have to be reserved by the kernel anymore. The Context Control Structure (CCS) data structure is now the Thread Control Structure (TCS): - struct ccs is now struct tcs - tCCS is now tTCS Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-20 23:04:01 +08:00
j _thread_entry
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
nop