Searched +full:is +full:- +full:advanced (Results 1 – 25 of 251) sorted by relevance
1234567891011
/Zephyr-latest/dts/bindings/counter/ |
D | gd,gd32-timer.yaml | 2 # SPDX-License-Identifier: Apache-2.0 6 compatible: "gd,gd32-timer" 8 include: [reset-device.yaml, base.yaml] 30 is-32bit: 32 description: Indicates if timer has a 32-bit counter. 34 is-advanced: 37 Indicates if timer has advanced features. Such features include break 38 inputs, dead-time insertion, etc.
|
/Zephyr-latest/include/zephyr/sys/ |
D | hash_map_cxx.h | 4 * SPDX-License-Identifier: Apache-2.0 12 * This is a C wrapper around `std::unordered_map`. It is mainly used for 31 * @brief Declare a C++ Hashmap (advanced) 33 * Declare a C++ Hashmap with control over advanced parameters. 35 * @note The allocator @p _alloc is used for allocating internal Hashmap 36 * entries and does not interact with any user-provided keys or values. 41 * @param ... Variant-specific details for @ref sys_hashmap_config. 48 * @brief Declare a C++ Hashmap (advanced) 50 * Declare a C++ Hashmap with control over advanced parameters. 52 * @note The allocator @p _alloc is used for allocating internal Hashmap [all …]
|
D | hash_map_sc.h | 4 * SPDX-License-Identifier: Apache-2.0 31 * @brief Declare a Separate Chaining Hashmap (advanced) 33 * Declare a Separate Chaining Hashmap with control over advanced parameters. 35 * @note The allocator @p _alloc_func is used for allocating internal Hashmap 36 * entries and does not interact with any user-provided keys or values. 48 * @brief Declare a Separate Chaining Hashmap (advanced) 50 * Declare a Separate Chaining Hashmap with control over advanced parameters. 52 * @note The allocator @p _alloc is used for allocating internal Hashmap 53 * entries and does not interact with any user-provided keys or values.
|
D | hash_map_oa_lp.h | 4 * SPDX-License-Identifier: Apache-2.0 10 * @brief Open-Addressing / Linear Probe Hashmap Implementation 35 * @brief Declare a Open Addressing Linear Probe Hashmap (advanced) 37 * Declare a Open Addressing Linear Probe Hashmap with control over advanced parameters. 39 * @note The allocator @p _alloc is used for allocating internal Hashmap 40 * entries and does not interact with any user-provided keys or values. 45 * @param ... Variant-specific details for @ref sys_hashmap_config. 52 * @brief Declare a Open Addressing Linear Probe Hashmap (advanced) 54 * Declare a Open Addressing Linear Probe Hashmap with control over advanced parameters. 56 * @note The allocator @p _alloc is used for allocating internal Hashmap [all …]
|
D | hash_map.h | 4 * SPDX-License-Identifier: Apache-2.0 32 * @brief Declare a Hashmap (advanced) 34 * Declare a Hashmap with control over advanced parameters. 36 * @note The allocator @p _alloc is used for allocating internal Hashmap 37 * entries and does not interact with any user-provided keys or values. 45 * @param ... Variant-specific details for @p _config_type. 60 * @brief Declare a Hashmap statically (advanced) 62 * Declare a Hashmap statically with control over advanced parameters. 64 * @note The allocator @p _alloc is used for allocating internal Hashmap 65 * entries and does not interact with any user-provided keys or values. [all …]
|
/Zephyr-latest/doc/services/debugging/ |
D | symtab.rst | 7 stage that keep tracks of the information about the functions' name and address, for advanced appli… 8 with a lot of functions, this is expected to consume a sizable amount of ROM. 10 Currently, this is being used to look up the function names during a stack trace in supported archi… 18 function to look-up the symbol name and offset of an address. More advanced functionalities and be
|
/Zephyr-latest/dts/bindings/reset/ |
D | st,stm32-rcc-rctl.yaml | 2 # SPDX-License-Identifier: Apache-2.0 6 This node is in charge of reset control for AHB (Advanced High Performance) 7 and APB (Advanced Peripheral) bus domains. 20 include/zephyr/dts-bindings/reset/stm32{soc_family}_reset.h header files. 22 compatible: "st,stm32-rcc-rctl" 24 include: [reset-controller.yaml, base.yaml] 27 "#reset-cells": 30 set-bit-to-deassert: 36 reset-cells: 37 - id
|
/Zephyr-latest/tests/subsys/edac/ibecc/ |
D | README.rst | 11 IBECC should be enabled in BIOS. This is usually enabled in the default 12 BIOS configuration. Verify following is enabled:: 14 :menuselection:`Intel Advanced Menu --> Memory Configuration --> In-Band ECC --> Enabled` 18 :menuselection:`Intel Advanced Menu --> Memory Configuration --> In-Band ECC Operation Mode --> 2` 33 :menuselection:`Intel Advanced Menu --> Memory Configuration --> In-Band ECC Error --> Enabled` 39 and debug configuration. The main difference is that debug configuration 47 .. zephyr-app-commands:: 48 :zephyr-app: tests/subsys/edac/ibecc 56 .. code-block:: console 58 *** Booting Zephyr OS build zephyr-v3.2.0-747-gd421737f433e *** [all …]
|
/Zephyr-latest/boards/silabs/radio_boards/ |
D | index.rst | 16 Radio Boards are used together with a Wireless Mainboard, which is a 22 - Wireless Starter Kit Mainboard (board BRD4001A, available standalone as SLWMB4001A) 23 - Wireless Pro Kit Mainboard (board BRD4002A, available standalone as Si-MB4002A) 25 The Wireless Pro Kit Mainboard is a strict superset of the Wireless Starter Kit, 33 name of the standalone Radio Board is used as the board target. 40 - Advanced Energy Monitor providing real-time information about energy consumption at up to 10 ksps 41 - Packet Trace Interface 42 - Virtual COM port 43 - On-board Segger J-Link debugger with USB and Ethernet interfaces 44 - Ultra-low power 128x128 pixel memory LCD [all …]
|
/Zephyr-latest/arch/arm64/core/ |
D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0 21 # This is 10 characters long (0x12345678). We can't use a 29 zephyr_cc_option(-mcmodel=large) 40 zephyr_library_sources_ifdef(CONFIG_HAS_ARM_SMCCC smccc-call.S) 48 zephyr_cc_option_ifdef(CONFIG_USERSPACE -mno-outline-atomics) 49 zephyr_cc_option_ifdef(CONFIG_FRAME_POINTER -mno-omit-leaf-frame-pointer) 51 # GCC may generate ldp/stp instructions with the Advanced SIMD Qn registers for 52 # consecutive 32-byte loads and stores. Saving and restoring the Advanced SIMD 53 # context is very expensive, and it is preferable to keep it turned off by not 57 zephyr_cc_option(-moverride=tune=no_ldp_stp_qregs)
|
/Zephyr-latest/dts/bindings/clock/ |
D | st,stm32wba-rcc.yaml | 2 # SPDX-License-Identifier: Apache-2.0 6 This node is in charge of system clock ('SYSCLK') source selection and controlling 7 clocks for AHB (Advanced High Performance) and APB (Advanced Peripheral) bus domains. 13 Core clock frequency should also be defined, using "clock-frequency" property. 18 Here is an example of correctly configured rcc node: 21 ahb-prescaler = <2>; 22 clock-frequency = <DT_FREQ_M(40)>; /* = SYSCLK / AHB prescaler */ 23 apb1-presacler = <1>; 24 apb2-presacler = <1>; 25 apb7-presacler = <7>; [all …]
|
D | st,stm32-rcc.yaml | 2 # SPDX-License-Identifier: Apache-2.0 6 This node is in charge of system clock ('SYSCLK') source selection and controlling 7 clocks for AHB (Advanced High Performance) and APB (Advanced Peripheral) bus domains. 13 Core clock frequency should also be defined, using "clock-frequency" property. 18 Here is an example of correctly configured rcc node: 21 ahb-prescaler = <2>; 22 clock-frequency = <DT_FREQ_M(40)>; /* = SYSCLK / AHB prescaler */ 23 apb1-prescaler = <1>; 24 apb2-prescaler = <1>; 39 The gated clock is required when accessing to the peripheral controller is needed [all …]
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | auxdisplay.rst | 9 Auxiliary Displays are text-based displays that have simple interfaces for 13 advanced custom feature supported is generation of custom characters. 15 and sizes, a common display size is 16 characters by 2 lines. 17 This API is unstable and subject to change.
|
D | mspi.rst | 3 Multi-bit SPI Bus 6 The MSPI (multi-bit SPI) is provided as a generic API to accommodate 7 advanced SPI peripherals and devices that typically require command, 9 While the API supports advanced features such as :term:`XIP` and scrambling, 10 it is also compatible with generic SPI. 16 .. _mspi-controller-api: 21 Zephyr's MSPI controller API may be used when a multi-bit SPI controller 22 is present. E.g. Ambiq MSPI, QSPI, OSPI, Flexspi, etc. 23 The API supports single to hex SDR/DDR IO with variable latency and advanced 25 not limited to high-speed, high density flash/psram memory devices, displays [all …]
|
/Zephyr-latest/modules/cmsis-dsp/ |
D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0 8 bool "CMSIS-DSP Library Support" 10 This option enables the CMSIS-DSP library. 44 * Complex-by-Complex Multiplication 45 * Complex-by-Real Multiplication 62 * Sine-Cosine 75 * Fixed-Point Division 92 * Levinson-Durbin Algorithm 167 * Kullback-Leibler Divergence 176 * Vector 8-bit Integer Value Conversion [all …]
|
/Zephyr-latest/arch/arm/core/ |
D | header.S | 2 * Copyright (C) 2023, Advanced Micro Devices, Inc. 4 * SPDX-License-Identifier: Apache-2.0 15 * on the interrupt stack when CONFIG_INIT_STACKS is enabled before
|
/Zephyr-latest/samples/sensor/tdk_apex/ |
D | README.rst | 1 .. zephyr:code-sample:: tdk_apex 2 :name: TDK Advanced Pedometer and Event Detection (APEX) 3 :relevant-api: sensor_interface 10 This sample application shows how to use the APEX (Advanced Pedometer 15 of 30 degrees or more. The tilt event is generated when the 16 position is held for 4 seconds. 25 …- https://invensense.tdk.com/download-pdf/an-000271-icm-42607x-and-icm-42670x-apex-motion-function… 30 The APEX is based on accelerometer data only. The TDK Sensor driver configures 44 to be aliased as ``tdk-apex-sensorN`` where ``N`` goes from ``0`` to ``9``. For example: 46 .. code-block:: devicetree [all …]
|
/Zephyr-latest/boards/up-bridge-the-gap/up_squared/doc/ |
D | index.rst | 9 UP |sup2| (UP Squared) is an ultra compact single board computer with high 18 Up Squared (Credit: https://up-board.org) 35 ---- 39 connected to the on-board FPGA acting as level shifter. Therefore, 42 accomplished in BIOS, under menu ``Advanced``, and option 43 ``HAT Configurations``. When a corresponding pin is set to act as 44 GPIO, there is an option to set the direction of the pin. This needs 69 .. zephyr-app-commands:: 70 :zephyr-app: samples/hello_world 76 A Zephyr EFI image file named :file:`zephyr.efi` is automatically [all …]
|
/Zephyr-latest/doc/develop/west/ |
D | alias.rst | 1 .. _west-aliases: 10 Similar to how ``git`` aliases work, the alias command is replaced with the alias' 20 .. code-block:: shell 22 west config alias.mylist "list -f '{name} {revision}'" 27 building more complex but easy-to-remember commands. 29 It is possible to override an existing command, for example to pass default arguments: 31 .. code-block:: shell 33 west config alias.update "update -o=--depth=1 -n" 37 Overriding/shadowing other or built-in commands is an advanced use case, it can lead to 38 strange side-effects and should be done with great care. [all …]
|
/Zephyr-latest/.github/workflows/ |
D | scorecards.yml | 2 # by a third-party and are governed by separate terms of service, privacy 5 name: Scorecards supply-chain security 7 # For Branch-Protection check. Only the default branch is supported. See 8 # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection 10 # To guarantee Maintained check is occasionally updated. See 13 - cron: '43 7 * * 6' 16 - main 18 permissions: read-all 23 runs-on: ubuntu-latest 26 security-events: write [all …]
|
/Zephyr-latest/boards/native/native_posix/ |
D | cpu_wait.c | 4 * SPDX-License-Identifier: Apache-2.0 21 * All this function ensures is that it will return after usec_to_wait or later. 23 * This special arch_busy_wait() is necessary due to how the POSIX arch/SOC INF 28 * programming a dedicated timer which will raise a non-maskable interrupt, 31 * (*1) In reality simulated time is simply not advanced just due to the "MCU" 32 * running. Meaning, the SW running on the MCU is assumed to take 0 time. 54 * time would be spent on interrupt handling or possible switched-in tasks. 71 to_wait -= hwm_get_time() - time_start; in posix_cpu_hold()
|
/Zephyr-latest/boards/native/native_sim/ |
D | cpu_wait.c | 5 * SPDX-License-Identifier: Apache-2.0 24 * All this function ensures is that it will return after usec_to_wait or later. 26 * This special arch_busy_wait() is necessary due to how the POSIX arch/SOC INF 31 * programming a dedicated timer which will raise a non-maskable interrupt, 34 * (*1) In reality simulated time is simply not advanced just due to the "MCU" 35 * running. Meaning, the SW running on the MCU is assumed to take 0 time. 57 * time would be spent on interrupt handling or possible switched-in tasks. 74 to_wait -= nsi_hws_get_time() - time_start; in posix_cpu_hold()
|
/Zephyr-latest/doc/services/storage/disk/ |
D | nvme.rst | 6 NVMe is a standardized logical device interface on PCIe bus exposing storage devices. 14 The driver is sliced up in 3 main parts: 16 - NVMe controller: :zephyr_file:`drivers/disk/nvme/nvme_controller.c` 17 - NVMe commands: :zephyr_file:`drivers/disk/nvme/nvme_cmd.c` 18 - NVMe namespace: :zephyr_file:`drivers/disk/nvme/nvme_namespace.c` 20 Where the NVMe controller is the root of the device driver. This is the one that will get device dr… 21 Note that this is only what DTS describes: the NVMe controller, and none of its namespaces (disks). 22 The NVMe command is the generic logic used to communicate with the controller and the namespaces it… 23 Finally the NVMe namespace is the dedicated part to deal with an actual namespace which, in turn, e… 26 …more than 1 namespace (disk), it will be possible to raise the amount of built-in namespace support [all …]
|
/Zephyr-latest/boards/shields/nrf7002ek/doc/ |
D | index.rst | 9 The nRF7002 EK is a versatile evaluation kit in the form of an Arduino shield that can be used in 10 Nordic and non-Nordic host boards. 12 The nRF7002 EK unlocks low-power Wi-Fi 6 capabilities for your host device. It support dual-band Wi… 13 2.4GHz and 5GHz, and is based on the nRF7002 SoC. 14 Seamlessly connect to Wi-Fi networks and leverage Wi-Fi-based locationing, enabling advanced 15 features such as SSID sniffing of local Wi-Fi hubs 26 The nRF7002 EK board is designed to fit straight into an Arduino connector and uses SPI as the 31 ------------- 33 the nRF70 driver requires firmware binary blobs for Wi-Fi operation. Run the command 36 .. code-block:: console [all …]
|
/Zephyr-latest/boards/shields/nrf7002eb/doc/ |
D | index.rst | 9 The nRF7002 EB is a versatile evaluation kit in the form of a thumbstick shield which connects to 10 compatible Nordic host boards, like the Thingy53, using the Nordic edge-connector. 12 The nRF7002 EB unlocks low-power Wi-Fi 6 capabilities for your host device. It support dual-band Wi… 13 2.4GHz and 5GHz, and is based on the nRF7002 SoC. 14 Seamlessly connect to Wi-Fi networks and leverage Wi-Fi-based locationing, enabling advanced 15 features such as SSID sniffing of local Wi-Fi hubs 26 The nRF7002 EB board is designed to fit straight into a Nordic edge-connector and uses SPI as the 27 communication interface. Any host board that supports the Nordic edge-connector can be used with 31 ------------- 33 the nRF70 driver requires firmware binary blobs for Wi-Fi operation. Run the command [all …]
|
1234567891011