michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/include/linker/common-ram.ld

167 lines
4.7 KiB
Text
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 09:08:09 -04:00
/* SPDX-License-Identifier: Apache-2.0 */
isr_tables: Support hardware interrupt vector table-only configuration. The existing isr_tables implementation does not allow enabling only hardware interrupt vector table without software isr table. This commit ensures that CONFIG_GEN_IRQ_VECTOR_TABLE can be used without setting CONFIG_GEN_SW_ISR_TABLE. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2019-10-14 13:47:17 +09:00
#if defined(CONFIG_GEN_SW_ISR_TABLE) && defined(CONFIG_DYNAMIC_INTERRUPTS)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(sw_isr_table,,)
interrupts: simplify position of sw ISR table We now place the linker directives for the SW ISR table in the common linker scripts, instead of repeating it everywhere. The table will be placed in RAM if dynamic interrupts are enabled. A dedicated section is used, as this data must not move in between build phases. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-11-08 14:44:31 -08:00
{
linker: Make alignment size for sw_isr_table configurable sw_isr_table has two entries, an argument and an ISR function. The comment on struct _isr_table_entry in include/sw_isr_table.h says that "This allows a table entry to be loaded [...] with one ldmia instruction, on ARM [...]". Some arch, e.g. SPARC, also has a double word load instruction, "ldd", but the instruct must have address align to double word or 8 bytes. This commit makes the table alignment configurable. It allows each architecture to specify it, if needed. The default value is 0 for no alignment. Signed-off-by: Yasushi SHOJI <y-shoji@ispace-inc.com>
2019-06-20 18:28:37 +09:00
/*
* Some arch requires an entry to be aligned to arch
* specific boundary for using double word load
* instruction. See include/sw_isr_table.h.
*/
. = ALIGN(CONFIG_ARCH_SW_ISR_TABLE_ALIGN);
linker: Clean up section name definitions This commit cleans up the section name definitions in the linker sections header file (`include/linker/sections.h`) to have the uniform format of `_(SECTION)_SECTION_NAME`. In addition, the scope of the short section reference aliases (e.g. `TEXT`, `DATA`, `BSS`) are now limited to the ASM code, as they are currently used (and intended to be used) only by the ASM code to specify the target section for functions and variables, and these short names can cause name conflicts with the symbols used in the C code. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-04-28 00:43:03 +09:00
*(_SW_ISR_TABLE_SECTION_NAME)
interrupts: simplify position of sw ISR table We now place the linker directives for the SW ISR table in the common linker scripts, instead of repeating it everywhere. The table will be placed in RAM if dynamic interrupts are enabled. A dedicated section is used, as this data must not move in between build phases. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-11-08 14:44:31 -08:00
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
#endif
linker: un-abstract some definitions These made sense before we had the common-rom/common-ram files, as the same boilerplate was repeated for every arch's linker script, but this is no longer necessary. Move these inline for simplicity. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-23 15:08:07 -07:00
/*
* Space for storing per device busy bitmap. Since we do not know beforehand
* the number of devices, we go through the below mechanism to allocate the
* required space.
*/
#ifdef CONFIG_DEVICE_POWER_MANAGEMENT
#define DEVICE_COUNT \
((__device_end - __device_start) / _DEVICE_STRUCT_SIZEOF)
#define DEV_BUSY_SZ (((DEVICE_COUNT + 31) / 32) * 4)
#define DEVICE_BUSY_BITFIELD() \
FILL(0x00) ; \
__device_busy_start = .; \
. = . + DEV_BUSY_SZ; \
__device_busy_end = .;
#else
#define DEVICE_BUSY_BITFIELD()
#endif
device: Refactor device structures When the device driver model got introduced, there were no concept of SYS_INIT() which can be seen as software service. These were introduced afterwards and reusing the device infrastructure for simplicity. However, it meant to allocate a bit too much for something that only required an initialization function to be called at right time. Thus refactoring the devices structures relevantly: - introducing struct init_entry which is a generic init end-point - struct deviceconfig is removed and struct device owns everything now. - SYS_INIT() generates only a struct init_entry via calling INIT_ENTRY_DEFINE() - DEVICE_AND_API_INIT() generates a struct device and calls INIT_ENTRY_DEFINE() - init objects sections are in ROM - device objects sections are in RAM (but will end up in ROM once they will be 'constified') It also generate a tiny memory gain on both ROM and RAM, which is nice. Perhaps kernel/device.c could be renamed to something more relevant. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2020-03-09 11:02:20 +01:00
SECTION_DATA_PROLOGUE(devices,,)
build: consolidate some common parts of linker scripts There are a number of data sections that are repeated across all the linker scripts for various architecture. In practice these don't always get updated and we have had problems with bit-rot. Consolidate these to make maintenance easier. x86 linker scripts now follow the same naming convention and we get rid of a linker-epilog.h that wasn't necessary and whose purpose has been lost to the mists of time. If applications want to define their own sections they should be allowed to. Linker scripts for x86 do not end with .h any more, they are not C header files even though we use C's preprocessor. Issue: ZEP-688 Change-Id: I893eb4619969695c1f980efd7c2ec9fa5dad136d Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 08:09:32 -07:00
{
linker: un-abstract some definitions These made sense before we had the common-rom/common-ram files, as the same boilerplate was repeated for every arch's linker script, but this is no longer necessary. Move these inline for simplicity. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-23 15:08:07 -07:00
/* link in devices objects, which are tied to the init ones;
* the objects are thus sorted the same way as their init
* object parent see include/device.h
*/
__device_start = .;
CREATE_OBJ_LEVEL(device, PRE_KERNEL_1)
CREATE_OBJ_LEVEL(device, PRE_KERNEL_2)
CREATE_OBJ_LEVEL(device, POST_KERNEL)
CREATE_OBJ_LEVEL(device, APPLICATION)
CREATE_OBJ_LEVEL(device, SMP)
__device_end = .;
DEVICE_BUSY_BITFIELD()
device: Refactor device structures When the device driver model got introduced, there were no concept of SYS_INIT() which can be seen as software service. These were introduced afterwards and reusing the device infrastructure for simplicity. However, it meant to allocate a bit too much for something that only required an initialization function to be called at right time. Thus refactoring the devices structures relevantly: - introducing struct init_entry which is a generic init end-point - struct deviceconfig is removed and struct device owns everything now. - SYS_INIT() generates only a struct init_entry via calling INIT_ENTRY_DEFINE() - DEVICE_AND_API_INIT() generates a struct device and calls INIT_ENTRY_DEFINE() - init objects sections are in ROM - device objects sections are in RAM (but will end up in ROM once they will be 'constified') It also generate a tiny memory gain on both ROM and RAM, which is nice. Perhaps kernel/device.c could be renamed to something more relevant. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2020-03-09 11:02:20 +01:00
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
build: consolidate some common parts of linker scripts There are a number of data sections that are repeated across all the linker scripts for various architecture. In practice these don't always get updated and we have had problems with bit-rot. Consolidate these to make maintenance easier. x86 linker scripts now follow the same naming convention and we get rid of a linker-epilog.h that wasn't necessary and whose purpose has been lost to the mists of time. If applications want to define their own sections they should be allowed to. Linker scripts for x86 do not end with .h any more, they are not C header files even though we use C's preprocessor. Issue: ZEP-688 Change-Id: I893eb4619969695c1f980efd7c2ec9fa5dad136d Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 08:09:32 -07:00
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(initshell,,)
console: shell: Support multiple modules Ability to use Zephyr shell by multiple modules simultaneously, each module for its own usage. Old shell implementation enabled the user to call only one module commands, not all of the modules simultaneously. Change-Id: I0ef8fa2fd190b7490c44fe91d1016363258302c9 Signed-off-by: Yael Avramovich <yael.avramovich@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-07-31 16:16:29 +03:00
{
linker: un-abstract some definitions These made sense before we had the common-rom/common-ram files, as the same boilerplate was repeated for every arch's linker script, but this is no longer necessary. Move these inline for simplicity. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-23 15:08:07 -07:00
/* link in shell initialization objects for all modules that
* use shell and their shell commands are automatically
* initialized by the kernel.
*/
__shell_module_start = .;
KEEP(*(".shell_module_*"));
__shell_module_end = .;
__shell_cmd_start = .;
KEEP(*(".shell_cmd_*"));
__shell_cmd_end = .;
console: shell: Support multiple modules Ability to use Zephyr shell by multiple modules simultaneously, each module for its own usage. Old shell implementation enabled the user to call only one module commands, not all of the modules simultaneously. Change-Id: I0ef8fa2fd190b7490c44fe91d1016363258302c9 Signed-off-by: Yael Avramovich <yael.avramovich@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-07-31 16:16:29 +03:00
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(log_dynamic_sections,,)
logging: subsystem major redesign Adding new implementation of logging subsystem. New features includes: support for multiple backends, improving performance by deferring log processing to the known context, adding timestamps and logs filtering options (compile time, runtime, module level, instance level). Console backend added as the example backend. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2018-05-16 08:50:33 +02:00
{
__log_dynamic_start = .;
KEEP(*(SORT(.log_dynamic_*)));
__log_dynamic_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: add iterable section macros For iterable areas defined with Z_STRUCT_SECTION_ITERABLE(), the corresponding output section in the linker script is just boilerplate. Add macros to make these definitions simpler. Unfortunately, we have a fair number of iterable sections not defined with Z_STRUCT_SECTION_ITERABLE(), this patch does not address this. The output sections are all named <struct name>_area, update sanitylib.py with this. sys_sem with no userspace, and k_lifo/k_fifo are special cases where different data types that are all equivalent need to be put in the same iterable area. Add Z_STRUCT_SECTION_ITERABLE_ALTERNATE() for this special case. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-23 14:38:39 -07:00
Z_ITERABLE_SECTION_RAM(_static_thread_data, 4)
unified: Add linker script support for all kernel object types Enhance the linker script so that all statically-defined kernel objects of a given type are co-located. Note 1: This capability is needed so that static kernel objects can be added to the associated object tracing list. (Some kernel object types are already co-located to permit the kernel to do other initialzation on statically-defined objects.) Note 2: A follow-up commit is needed to ensure statically- defined kernel objects are placed in the sections referenced in the linker script. Note 3: The legacy script info remains for now to allow applications using the microkernel or nanokernel to continue to build. Change-Id: I40d831f9e183fb121c950e30fa8298b6d529375b Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2016-11-01 14:37:15 -05:00
kernel: introduce object validation mechanism All system calls made from userspace which involve pointers to kernel objects (including device drivers) will need to have those pointers validated; userspace should never be able to crash the kernel by passing it garbage. The actual validation with _k_object_validate() will be in the system call receiver code, which doesn't exist yet. - CONFIG_USERSPACE introduced. We are somewhat far away from having an end-to-end implementation, but at least need a Kconfig symbol to guard the incoming code with. Formal documentation doesn't exist yet either, but will appear later down the road once the implementation is mostly finalized. - In the memory region for RAM, the data section has been moved last, past bss and noinit. This ensures that inserting generated tables with addresses of kernel objects does not change the addresses of those objects (which would make the table invalid) - The DWARF debug information in the generated ELF binary is parsed to fetch the locations of all kernel objects and pass this to gperf to create a perfect hash table of their memory addresses. - The generated gperf code doesn't know that we are exclusively working with memory addresses and uses memory inefficently. A post-processing script process_gperf.py adjusts the generated code before it is compiled to work with pointer values directly and not strings containing them. - _k_object_init() calls inserted into the init functions for the set of kernel object types we are going to support so far Issue: ZEP-2187 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-08-22 13:15:23 -07:00
#ifdef CONFIG_USERSPACE
/* All kernel objects within are assumed to be either completely
* initialized at build time, or initialized automatically at runtime
* via iteration before the POST_KERNEL phase.
*
* These two symbols only used by gen_kobject_list.py
*/
_static_kernel_objects_begin = .;
#endif /* CONFIG_USERSPACE */
linker: add iterable section macros For iterable areas defined with Z_STRUCT_SECTION_ITERABLE(), the corresponding output section in the linker script is just boilerplate. Add macros to make these definitions simpler. Unfortunately, we have a fair number of iterable sections not defined with Z_STRUCT_SECTION_ITERABLE(), this patch does not address this. The output sections are all named <struct name>_area, update sanitylib.py with this. sys_sem with no userspace, and k_lifo/k_fifo are special cases where different data types that are all equivalent need to be put in the same iterable area. Add Z_STRUCT_SECTION_ITERABLE_ALTERNATE() for this special case. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-05-23 14:38:39 -07:00
Z_ITERABLE_SECTION_RAM(k_timer, 4)
Z_ITERABLE_SECTION_RAM(k_mem_slab, 4)
Z_ITERABLE_SECTION_RAM(k_mem_pool, 4)
Z_ITERABLE_SECTION_RAM(k_heap, 4)
Z_ITERABLE_SECTION_RAM(k_mutex, 4)
Z_ITERABLE_SECTION_RAM(k_stack, 4)
Z_ITERABLE_SECTION_RAM(k_msgq, 4)
Z_ITERABLE_SECTION_RAM(k_mbox, 4)
Z_ITERABLE_SECTION_RAM(k_pipe, 4)
Z_ITERABLE_SECTION_RAM(k_sem, 4)
Z_ITERABLE_SECTION_RAM(k_queue, 4)
unified: Add linker script support for all kernel object types Enhance the linker script so that all statically-defined kernel objects of a given type are co-located. Note 1: This capability is needed so that static kernel objects can be added to the associated object tracing list. (Some kernel object types are already co-located to permit the kernel to do other initialzation on statically-defined objects.) Note 2: A follow-up commit is needed to ensure statically- defined kernel objects are placed in the sections referenced in the linker script. Note 3: The legacy script info remains for now to allow applications using the microkernel or nanokernel to continue to build. Change-Id: I40d831f9e183fb121c950e30fa8298b6d529375b Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2016-11-01 14:37:15 -05:00
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(_net_buf_pool_area,,SUBALIGN(4))
net: buf: Move net_buf_pool objects to dedicated linker area Moving the net_buf_pool objects to a dedicated area lets us access them by array offset into this area instead of directly by pointer. This helps reduce the size of net_buf objects by 4 bytes. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-03 19:20:27 +03:00
{
_net_buf_pool_list = .;
KEEP(*(SORT_BY_NAME("._net_buf_pool.static.*")))
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(net_if,,SUBALIGN(4))
net: Add generic network interface header This will be used by the new network stack to relate a device to actual network context, and used in the different layers (mac, ip ...). Change-Id: I30c08fa975314544c36b71636fd9653d562891b3 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-05-02 09:02:04 +02:00
{
__net_if_start = .;
*(".net_if.*")
net: Switch from per-iface tx thread to a unique k_poll triggered one Now that k_poll landed in the kernel, it's worth using it to save memory and reduce the number of threads at runtime. Such switch has been first done in bluetooth (see hci_core.c and conn.c in subsys/bluetooth/host). Since network interfaces kind of follows the same design for sending data, it was then easy to copy the same change as in bluetooth. Change-Id: I7f9734b88ac818284bbabaedc946b4765b905ebb Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-03-08 09:30:03 +01:00
KEEP(*(SORT_BY_NAME(".net_if.*")))
net: Add generic network interface header This will be used by the new network stack to relate a device to actual network context, and used in the different layers (mac, ip ...). Change-Id: I30c08fa975314544c36b71636fd9653d562891b3 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-05-02 09:02:04 +02:00
__net_if_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
net: Add a neighbor cache needed in IPv6 This is the framework that neighbor discovery uses. The ND is coming in later commits. Change-Id: Iaaa67c80c0b6b8a3adb9217413b906e0a22d3920 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-06-01 15:25:22 +03:00
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(net_if_dev,,SUBALIGN(4))
net: if: Separate IP address configuration from net_if Move IP address settings from net_if to separate structs. This is needed for VLAN support. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-01-11 16:06:53 +02:00
{
__net_if_dev_start = .;
*(".net_if_dev.*")
KEEP(*(SORT_BY_NAME(".net_if_dev.*")))
__net_if_dev_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(net_l2_data,,SUBALIGN(4))
net: L2 might need private data per-interface Allocate the right amount of space for L2's context. Change-Id: Ia2f4f4162334e9e9c26dc95230abdfde5986e052 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-06-16 13:50:38 +02:00
{
__net_l2_data_start = .;
*(".net_l2.data")
KEEP(*(SORT_BY_NAME(".net_l2.data*")))
__net_l2_data_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
kernel: introduce object validation mechanism All system calls made from userspace which involve pointers to kernel objects (including device drivers) will need to have those pointers validated; userspace should never be able to crash the kernel by passing it garbage. The actual validation with _k_object_validate() will be in the system call receiver code, which doesn't exist yet. - CONFIG_USERSPACE introduced. We are somewhat far away from having an end-to-end implementation, but at least need a Kconfig symbol to guard the incoming code with. Formal documentation doesn't exist yet either, but will appear later down the road once the implementation is mostly finalized. - In the memory region for RAM, the data section has been moved last, past bss and noinit. This ensures that inserting generated tables with addresses of kernel objects does not change the addresses of those objects (which would make the table invalid) - The DWARF debug information in the generated ELF binary is parsed to fetch the locations of all kernel objects and pass this to gperf to create a perfect hash table of their memory addresses. - The generated gperf code doesn't know that we are exclusively working with memory addresses and uses memory inefficently. A post-processing script process_gperf.py adjusts the generated code before it is compiled to work with pointer values directly and not strings containing them. - _k_object_init() calls inserted into the init functions for the set of kernel object types we are going to support so far Issue: ZEP-2187 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-08-22 13:15:23 -07:00
drivers: console: uart_mux: Initial UART muxing support Create support for muxed UARTs which are attached to a real UART and which use GSM 07.10 muxing protocol to create virtual channels that can be run on top of the real UART. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2020-04-01 12:47:53 +03:00
#if defined(CONFIG_UART_MUX)
SECTION_DATA_PROLOGUE(uart_mux,,SUBALIGN(4))
{
__uart_mux_start = .;
*(".uart_mux.*")
KEEP(*(SORT_BY_NAME(".uart_mux.*")))
__uart_mux_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
#endif
include: linker: add sections for USB device stack This patch adds a RAM section for the USB descriptors and USB interfaces data. The parts of USB descriptor can be declared independently in different USB class drivers or functions. These must then be placed in a predefined order one after the other without gaps in a RAM section. There may also be several device descriptors in the section such as for USB DFU. Since at runtime the number of interfaces and endpoints in the composite device descriptor is unknown, they must be corrected. The class drivers or functions use the usb_cfg_data struct to store the callbacks, interface and endpoints data. This struct must also be corrected and needs to be placed in the data section. The descriptor section and data section must be processed by the USB Device Stack before the enumeration. Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2017-10-30 12:27:35 +01:00
#if defined(CONFIG_USB_DEVICE_STACK)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(usb_descriptor,,SUBALIGN(1))
include: linker: add sections for USB device stack This patch adds a RAM section for the USB descriptors and USB interfaces data. The parts of USB descriptor can be declared independently in different USB class drivers or functions. These must then be placed in a predefined order one after the other without gaps in a RAM section. There may also be several device descriptors in the section such as for USB DFU. Since at runtime the number of interfaces and endpoints in the composite device descriptor is unknown, they must be corrected. The class drivers or functions use the usb_cfg_data struct to store the callbacks, interface and endpoints data. This struct must also be corrected and needs to be placed in the data section. The descriptor section and data section must be processed by the USB Device Stack before the enumeration. Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2017-10-30 12:27:35 +01:00
{
__usb_descriptor_start = .;
*(".usb.descriptor")
KEEP(*(SORT_BY_NAME(".usb.descriptor*")))
__usb_descriptor_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(usb_data,,SUBALIGN(1))
include: linker: add sections for USB device stack This patch adds a RAM section for the USB descriptors and USB interfaces data. The parts of USB descriptor can be declared independently in different USB class drivers or functions. These must then be placed in a predefined order one after the other without gaps in a RAM section. There may also be several device descriptors in the section such as for USB DFU. Since at runtime the number of interfaces and endpoints in the composite device descriptor is unknown, they must be corrected. The class drivers or functions use the usb_cfg_data struct to store the callbacks, interface and endpoints data. This struct must also be corrected and needs to be placed in the data section. The descriptor section and data section must be processed by the USB Device Stack before the enumeration. Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2017-10-30 12:27:35 +01:00
{
__usb_data_start = .;
*(".usb.data")
KEEP(*(SORT_BY_NAME(".usb.data*")))
__usb_data_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
#endif /* CONFIG_USB_DEVICE_STACK */
usb: bos: Add linker sections for USB BOS descriptor Since USB Binary Device Object Store (BOS) descriptor might be defined in several places create usb_bos_desc section. Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2018-05-31 15:26:30 +03:00
#if defined(CONFIG_USB_DEVICE_BOS)
linker: Remove unused (OPTIONAL) from linker scripts (OPTIONAL) was a vestiage from the initial import of the Zephyr code base and we dont utilize it with the GNU linker. Additionally, the way (OPTIONAL) gets defined to nothing creates a linker script that lld (from llvm) doesn't like. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-03-14 18:39:36 -05:00
SECTION_DATA_PROLOGUE(usb_bos_desc,,SUBALIGN(1))
usb: bos: Add linker sections for USB BOS descriptor Since USB Binary Device Object Store (BOS) descriptor might be defined in several places create usb_bos_desc section. Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2018-05-31 15:26:30 +03:00
{
__usb_bos_desc_start = .;
*(".usb.bos_desc")
KEEP(*(SORT_BY_NAME(".usb.bos_desc*")))
__usb_bos_desc_end = .;
} GROUP_DATA_LINK_IN(RAMABLE_REGION, ROMABLE_REGION)
#endif /* CONFIG_USB_DEVICE_BOS */
kernel: introduce object validation mechanism All system calls made from userspace which involve pointers to kernel objects (including device drivers) will need to have those pointers validated; userspace should never be able to crash the kernel by passing it garbage. The actual validation with _k_object_validate() will be in the system call receiver code, which doesn't exist yet. - CONFIG_USERSPACE introduced. We are somewhat far away from having an end-to-end implementation, but at least need a Kconfig symbol to guard the incoming code with. Formal documentation doesn't exist yet either, but will appear later down the road once the implementation is mostly finalized. - In the memory region for RAM, the data section has been moved last, past bss and noinit. This ensures that inserting generated tables with addresses of kernel objects does not change the addresses of those objects (which would make the table invalid) - The DWARF debug information in the generated ELF binary is parsed to fetch the locations of all kernel objects and pass this to gperf to create a perfect hash table of their memory addresses. - The generated gperf code doesn't know that we are exclusively working with memory addresses and uses memory inefficently. A post-processing script process_gperf.py adjusts the generated code before it is compiled to work with pointer values directly and not strings containing them. - _k_object_init() calls inserted into the init functions for the set of kernel object types we are going to support so far Issue: ZEP-2187 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-08-22 13:15:23 -07:00
#ifdef CONFIG_USERSPACE
_static_kernel_objects_end = .;
#endif
Copy permalink