| /Zephyr-latest/arch/riscv/ |
| D | Kconfig.isa | 28 (M) - Standard Extension for Integer Multiplication and Division
30 Standard integer multiplication and division instruction extension,
37 (A) - Standard Extension for Atomic Instructions
39 The standard atomic instruction extension is denoted by instruction
47 (F) - Standard Extension for Single-Precision Floating-Point
49 Standard instruction-set extension for single-precision
58 (D) - Standard Extension for Double-Precision Floating-Point
60 Standard double-precision floating-point instruction-set extension,
82 (Q) - Standard Extension for Quad-Precision Floating-Point
84 Standard extension for 128-bit binary floating-point instructions
[all …]
|
| /Zephyr-latest/tests/misc/llext-edk/pytest/ |
| D | test_edk.py | 51 # Copy the extension to another temporary directory to test out of tree builds
53 logger.debug(f"Copying extension to {tempdir_extension}")
54 ext_dir = Path(os.environ["ZEPHYR_BASE"]) / "tests/misc/llext-edk/extension"
57 # Also copy file2hex.py to the extension directory, so that it's possible
58 # to generate a hex file from the extension binary
63 # Set the LLEXT_EDK_INSTALL_DIR environment variable so that the extension
69 # Build the extension using the edk
70 logger.debug(f"Building extension in {tempdir_extension} - cmake")
75 logger.debug(f"Building extension in {tempdir_extension} - make")
80 # Check if the extension was built
[all …]
|
| /Zephyr-latest/doc/develop/tools/ |
| D | vscode.rst | 21 Search for the `C/C++ Extension Pack`_ and install it.
47 generate the :file:`compile_commands.json` file that will provide the C/C++ extension with the
56 Configure the C/C++ extension
79 - `Checkpatch Extension`_
80 - `EditorConfig Extension`_
85 - `reStructuredText Extension Pack`_
90 - `CMake Extension documentation`_
91 - `nRF Kconfig Extension`_
92 - `nRF DeviceTree Extension`_
93 - `GNU Linker Map files Extension`_
[all …]
|
| /Zephyr-latest/include/zephyr/llext/ |
| D | llext.h | 72 * @brief Structure describing a linkable loadable extension
74 * This structure holds the data for a loaded extension. It is created by the
104 * Table of all global symbols in the extension; used internally as
105 * part of the linking process. E.g. if the extension is built out of
114 * extension.
118 /** Extension use counter, prevents unloading while in use */
121 /** Array of extensions, whose symbols this extension accesses */
152 * means, that the application will take care to place the extension at
179 * Calls a provided callback function for each registered extension or until the
190 * @brief Load and link an extension
[all …]
|
| D | symbol.h | 21 * @brief Linkable loadable extension symbol definitions
92 /* Extension build: add exported symbols to llext table */
100 /* No-op when not building an extension */
106 * @brief Exports a symbol from an extension to the base image
109 * to the extension's exported symbol table, so that it may be referenced by
112 * When not building an extension, this macro is a no-op.
114 * @param x Extension symbol to export to the base image
120 /* Extension build: EXPORT_SYMBOL maps to LL_EXTENSION_SYMBOL */
139 /* No extension support in this build */
|
| D | loader.h | 36 * @brief Linkable loadable extension loader context
39 * while an extension is being loaded by the LLEXT subsystem. Once the
40 * extension is loaded, this object is no longer needed.
44 * @brief Optional function to prepare the loader for loading extension.
92 * @brief Optional function to clean after the extension has been loaded or error occurred.
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 4 Once an extension is built and the ELF file is available, it can be loaded into
6 extension into memory, access its symbols and call its functions.
8 Loading an extension
11 An extension may be loaded using any implementation of a :c:struct:`llext_loader`
19 passing in the extension name and the configured loader. Once that completes
20 successfully, the extension is loaded into memory and is ready to be used.
23 When :ref:`User Mode <usermode_api>` is enabled, the extension will not be
27 Initializing and cleaning up the extension
30 The extension may define a number of initialization functions that must be
34 extension.
[all …]
|
| D | build.rst | 9 The easiest path to achieve this is to build the extension as part of the
12 main Zephyr application and the extension(s), which will all automatically be
16 convenient; maybe the extension is built using a different compiler suite or as
17 part of a different project altogether. In this case, the extension developer
19 application. This can be done using the `LLEXT Extension Development Kit
31 Building the extension
34 An extension can be defined in the app's ``CMakeLists.txt`` by invoking the
52 packaged extension;
54 create the extension.
56 The exact steps of the extension building process depend on the currently
[all …]
|
| D | config.rst | 11 The LLEXT subsystem needs a static heap to be allocated for extension related
21 large enough to allow the extension sections to be allocated with the
60 and copies all data into allocated memory; this is done to allow the extension
67 Allow the extension to be loaded by directly referencing section data
75 extension remains allocated until the extension is unloaded.
80 phase. Once the extension is unloaded, the buffer must be reloaded
94 When an extension is loaded, the LLEXT subsystem must find the address of all
95 the symbols residing in the main application that the extension references.
99 LLEXT linker at extension load time. This process is pretty slow due to the
126 forbidden to load an extension that was compiled with
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 5 Enable linkable loadable extension development outside the Zephyr tree using
6 LLEXT EDK (Extension Development Kit).
11 This sample demonstrates how to use the Zephyr LLEXT EDK (Extension Development
22 subscribing to events. Extension ``kext1`` runs in a kernel thread, albeit similar
25 The application also creates different memory domains for each extension, thus
29 Note that the kernel extension is only available when the EDK is built with
117 [app]Loading extension [kext1].
118 [app]Thread 0x20840 created to run extension [kext1], at privileged mode.
122 [app]Loading extension [ext1].
123 [app]Thread 0x20a30 created to run extension [ext1], at userspace.
[all …]
|
| /Zephyr-latest/include/zephyr/bluetooth/ |
| D | direction.h | 12 /** Constant Tone Extension (CTE) types. */
57 /** @brief Constant Tone Extension parameters for connectionless
82 * @brief Constant Tone Extension parameters for connectionless reception.
111 /** Reported IQ samples have 16 bits signed integer format. Vendor specific extension. */
194 /** Constant Tone Extension parameters for CTE transmission in connected mode. */
227 * @brief Set or update the Constant Tone Extension parameters for periodic advertising set.
230 * @param[in] params Constant Tone Extension parameters.
238 * @brief Enable transmission of Constant Tone Extension for the given advertising set.
240 * Transmission of Constant Tone Extension may be enabled only after setting periodic advertising
241 * parameters (@ref bt_le_per_adv_set_param) and Constant Tone Extension parameters
[all …]
|
| D | hci_raw.h | 74 /** Helper macro to define a command extension
108 /** @brief Register Bluetooth RAW command extension table
110 * Register Bluetooth RAW channel command extension table, opcodes in this
113 * @param cmds Pointer to the command extension table.
114 * @param size Size of the command extension table.
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 7 source code. These are called **west extension commands**, or just "extensions"
10 information on west extension commands, and has a tutorial for writing your
33 Disabling Extension Commands
36 To disable support for extension commands, set the ``commands.allow_extensions``
51 Note that the files containing extension commands are not imported by west
54 Adding a West Extension
57 There are three steps to adding your own extension:
64 Note that west ignores extension commands whose names are the same as a
75 this class will be instantiated and used when your extension is run.
85 Basic example of a west extension.'''
[all …]
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.df | 47 bool "Transmission of Constant Tone Extension"
51 Enable support for transmission of Constant Tone Extension in
59 Enable reception of Constant Tone Extension. Process IQ sampling
92 bool "Reception of Constant Tone Extension feature"
97 Enable support for reception of Constant Tone Extension in controller.
135 Enable transmission of Constant Tone Extension in
143 Enable reception and sampling of Constant Tone Extension in direction
182 int "Maximum number of transmitted PDUs with Constant Tone Extension in connectionless mode"
187 Maximum supported number of PDUs, that have Constant Tone Extension, transmitted in single
192 int "Maximum number of received PDUs with Constant Tone Extension in connectionless mode"
[all …]
|
| /Zephyr-latest/subsys/llext/ |
| D | shell.c | 26 "Unload an extension by name. Syntax:\n" \
30 "List extension symbols. Syntax:\n" \
34 "Call extension function with prototype void fn(void). Syntax:\n" \
53 shell_print(sh, "Extension: %s symbols", m->name); in cmd_llext_list_symbols()
136 shell_print(sh, "Extension %d bytes too large to load, max %d bytes\n", hex_len/2, in cmd_llext_load_hex()
156 shell_print(sh, "Successfully loaded extension %s, addr %p\n", ext->name, ext); in cmd_llext_load_hex()
158 shell_print(sh, "Failed to load extension %s, return code %d\n", name, res); in cmd_llext_load_hex()
169 shell_print(sh, "No such extension %s", argv[1]); in cmd_llext_unload()
174 shell_print(sh, "Unloaded extension %s\n", argv[1]); in cmd_llext_unload()
184 shell_print(sh, "No such extension %s", argv[1]); in cmd_llext_call_fn()
[all …]
|
| /Zephyr-latest/soc/neorv32/ |
| D | Kconfig | 19 # NEORV32 RISC-V ISA A extension implements only LR/SC, not AMO
31 bool "RISC-V ISA Extension \"C\""
35 "C" extension (Compressed Instructions).
|
| /Zephyr-latest/arch/arm/core/cortex_m/ |
| D | Kconfig | 153 MCUs that implement the ARMv8-M Main Extension (Mainline).
155 In an ARMv8-M Mainline implementation with the Security Extension
157 In an ARMv8-M Baseline implementation with the Security Extension
191 - A Processing Element (PE) without the Main Extension
221 Extension.
224 - A Processing Element (PE) with the Main Extension is also
226 - ARMv7-M compatibility requires the Main Extension.
229 The Main Extension provides backwards compatibility
239 implementation, supporting the Main Extension.
241 ARMv8-M Main Extension includes additional features
[all …]
|
| /Zephyr-latest/soc/andestech/ae350/ |
| D | Kconfig | 75 bool "Andes V5 PowerBrake extension"
79 The PowerBrake extension throttles performance by reducing instruction
83 bool "Andes V5 EXEC.IT extension"
88 The EXEC.IT extension (Execution on Instruction Table) generate
|
| /Zephyr-latest/tests/misc/llext-edk/src/ |
| D | main.c | 16 #include <extension.inc>
38 printk("Calling extension from %s\n", in thread_entry()
61 llext_load(loader, "extension", ext, &ldr_parm); in load_and_run_extension()
96 printk("Extension not loaded\n"); in main()
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 39 llext - Loadable extension commands
45 unload :Unload an extension by name. Syntax:
47 list_symbols :List extension symbols. Syntax:
49 call_fn :Call extension function with prototype void fn(void). Syntax:
133 The resulting hex string can be used to load the extension.
139 This extension can then be seen in the list of loaded extensions (``list``), its symbols printed
140 (``list_symbols``), and the hello_world function which the extension exports can be called and
|
| /Zephyr-latest/soc/ite/ec/common/ |
| D | soc_dt.h | 31 * @brief For it8xxx2, construct wuc map structure in LISTIFY extension
33 * @param idx index in LISTIFY extension
67 * @brief Macro function to construct it8xxx2 GPIO IRQ in LISTIFY extension.
69 * @param idx index in LISTIFY extension.
|
| /Zephyr-latest/include/zephyr/dt-bindings/gpio/ |
| D | numicro-gpio.h | 12 * The debounce flag is a Zephyr specific extension of the standard GPIO flags
20 * The Schmitt trigger flag is a Zephyr specific extension of the standard GPIO flags
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.clic | 24 The selective hardware vectoring extension gives users the flexibility
34 Enables legacy clic, where smclicshv extension is not supported and
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | CMakeLists.txt | 48 # generate extension targets foreach extension given by 'ext_names'
71 # Manually fix the pre_located extension's text address at a multiple of 4
|
| /Zephyr-latest/doc/_extensions/zephyr/doxytooltip/ |
| D | __init__.py | 2 Doxygen Tooltip Extension
8 A simple Sphinx extension that adds JS and CSS resources to the app
|
