Searched full:v2 (Results 1 – 25 of 556) sorted by relevance
12345678910>>...23
| /Zephyr-latest/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 5 bool "CMSIS RTOS v2 API"
13 This enables CMSIS RTOS v2 API support. This is an OS-integration
14 layer which allows applications using CMSIS RTOS V2 APIs to build
19 int "Maximum thread count in CMSIS RTOS V2 application"
23 Mention max number of threads in CMSIS RTOS V2 compliant application.
28 int "Maximum dynamic thread count in CMSIS RTOS V2 application"
32 Mention max number of dynamic threads in CMSIS RTOS V2 compliant
38 int "Max stack size threads can be allocated in CMSIS RTOS V2 application"
42 Mention max stack size threads can be allocated in CMSIS RTOS V2 application.
45 int "Dynamic stack size threads are allocated in CMSIS RTOS V2 application"
[all …]
|
| /Zephyr-latest/scripts/ci/ |
| D | Kconfig.board.v2 | 1 # Kconfig top-level ci for compliance testing Kconfig tree for boards / SoC v2 scheme.
7 mainmenu "Zephyr board / SoC v2 Configuration"
12 source "boards/Kconfig.v2"
13 source "soc/Kconfig.v2"
|
| /Zephyr-latest/tests/drivers/sensor/adltc2990/boards/ |
| D | native_sim.overlay | 11 pins-v1-v2-current-resistor = <0>;
14 pin-v2-voltage-divider-resistors = <110000 100000>;
25 pins-v1-v2-current-resistor = <1000000>;
28 pin-v2-voltage-divider-resistors = <0 1>;
37 pins-v1-v2-current-resistor = <1000000>;
40 pin-v2-voltage-divider-resistors = <0 1>;
51 pins-v1-v2-current-resistor = <1000000>;
54 pin-v2-voltage-divider-resistors = <0 1>;
65 pins-v1-v2-current-resistor = <10000>;
68 pin-v2-voltage-divider-resistors = <110000 100000>;
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/interrupt_controller/ |
| D | gic.h | 33 * v2/v3 GICD_CTLR
40 * v2/v3 GICD_TYPER
47 * v2/v3 GICD_IIDR
54 * v2/v3 GICD_IGROUPRn
61 * v2/v3 GICD_ISENABLERn
68 * v2/v3 GICD_ICENABLERn
75 * v2/v3 GICD_ISPENDRn
82 * v2/v3 GICD_ICPENDRn
89 * v2/v3 GICD_ISACTIVERn
96 * v2/v3 GICD_ICACTIVERn
[all …]
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 6 The Makerbase MKS CANable V2.0 board features an ARM Cortex-M4 based STM32G431C8 MCU
8 Here are some highlights of the MKS CANable V2.0 board:
21 More information about the board can be found at the `MKS CANable V2.0 website`_.
22 It is very advisable to take a look in on user manual `MKS CANable V2.0 User Manual`_ and
23 schematic `MKS CANable V2.0 schematic`_ before start.
73 For more details please refer to `MKS CANable V2.0 schematic`_.
78 The MKS CANable V2.0 system clock is driven by internal high speed oscillator.
87 MKS CANable V2.0 board includes an SWDIO debug connector header J4.
102 Flashing an application to MKS CANable V2.0
105 The debugger shall be wired to MKS CANable V2.0 board's J4 connector
[all …]
|
| /Zephyr-latest/drivers/virtualization/ |
| D | Kconfig | 33 based ivshmem. For ivshmem-v2 INTx interrupts are also supported.
63 bool "Inter-VM shared memory v2 (ivshmem-v2)"
66 Enable ivshmem-v2 support.
67 ivshmem-v2 is primarily used for IPC in the Jailhouse hypervisor.
70 int "Maximum number of ivshmem-v2 peers"
|
| /Zephyr-latest/dts/bindings/virtualization/ |
| D | qemu,ivshmem.yaml | 12 ivshmem-v2:
15 Use ivshmem-v2.
17 ivshmem-v2 is not compatible with v1.
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
| D | README.rst | 1 .. zephyr:code-sample:: cmsis-rtos-v2
2 :name: Dining Philosophers (CMSIS RTOS V2 APIs)
4 Implement a solution to the Dining Philosophers problem using CMSIS RTOS V2.
10 multi-thread synchronization problem) using CMSIS RTOS V2 APIs. This particular
13 which uses CMSIS RTOS V2 API implementation in Zephyr.
54 CMSIS RTOS V2 APIs. This particular implementation demonstrates the
|
| /Zephyr-latest/boards/starfive/visionfive2/ |
| D | visionfive2.dts | 9 #include "starfive/jh7110-visionfive-v2.dtsi"
12 model = "StarFive VisionFive V2";
13 compatible = "starfive,visionfive-v2";
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | adi,adltc2990.yaml | 43 0 | 0 0 0 | V1, V2, TR2 (Default)
44 1 | 0 0 1 | V1 – V2, TR2
45 2 | 0 1 0 | V1 – V2, V3, V4
49 6 | 1 1 0 | V1 – V2, V3 – V4
50 7 | 1 1 1 | V1, V2, V3, V4
58 1 | 0 1 | TR1, V1 or V1 – V2 Only per Mode [2:0]
64 pins-v1-v2-current-resistor:
72 pin-v2-voltage-divider-resistors:
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.stm32 | 17 Driver for STM32 DMA V1, V2, V2bis and BDMA types.
42 Enable DMA V2 or DMA V2bis support. With the versions V2 of DMA, the
44 With the versions V2 bis of DMA, the peripheral request (slot) is not
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 83 - `PR18659 fix for v2.0.0
95 This has been fixed in releases v1.14.2, v2.2.0, and v2.1.1.
119 This has been fixed in releases v1.14.2, and v2.2.0.
127 - `PR23456 fix for the v2.1 branch
130 - `PR23240 fix for v2.2.0
146 v2.1.0, and branch from v2.2.0.
154 - `PR24065 fix for branch from v2.1.0
157 - `PR24066 fix for branch from v2.2.0
173 This has been fixed in releases v1.14.2, v2.2.0, and in a branch from
174 v2.1.0,
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 3 Fixing and backporting fixes to Zephyr v2.7 MCUmgr
27 …* The fix, done directly to the Zephyr held code of the MCUmgr library, is backported to the ``v2.…
28 …* The fix, ported to the Zephyr held code from the upstream repository, is backported to the ``v2.…
30 to the ``v2.7-branch``.
32 directly applied to the ``v2.7-branch``.
56 You must also apply the ``backport v2.7-branch`` label to the bug report.
84 #. Create the pull request selecting ``v2.7-branch`` as the merge target.
95 1. Create the pull request selecting ``v2.7-branch`` as the merge target.
144 For example, a branch named ``backport-upstream-137-to-v2.7-branch`` indicates a backport of pull
148 to ``v2.7-branch``.
[all …]
|
| /Zephyr-latest/dts/bindings/interrupt-controller/ |
| D | arm,gic-v2.yaml | 3 description: ARM Generic Interrupt Controller v2
5 compatible: arm,gic-v2
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/ |
| D | README.rst | 1 .. zephyr:code-sample:: cmsis-rtos-v2-sync
2 :name: Synchronization using CMSIS RTOS V2 APIs
4 Use timers and message queues from CMSIS RTOS v2 API to synchronize threads.
9 CMSIS RTOS V2 APIs.
|
| /Zephyr-latest/dts/bindings/cpu/ |
| D | wch,qingke-v2.yaml | 4 description: WCH QingKe V2 RISC-V MCU
6 compatible: "wch,qingke-v2"
|
| /Zephyr-latest/dts/bindings/crypto/ |
| D | ite,it8xxx2-sha-v2.yaml | 4 description: ITE IT8XXX2 Crypto SHA accelerator V2.
6 compatible: "ite,it8xxx2-sha-v2"
|
| /Zephyr-latest/soc/ |
| D | Kconfig.v2 | 6 # SoCs that has transitioned to SoC scheme v2 are promptless, and thus
10 # they offer board maintainers the possibility to use board scheme v2.
16 SoC for hw model v2.
|
| /Zephyr-latest/dts/bindings/ethernet/ |
| D | siemens,ivshmem-eth.yaml | 12 ivshmem-v2:
15 description: ivshmem-v2 driver node
|
| /Zephyr-latest/samples/boards/st/i2c_timing/ |
| D | sample.yaml | 2 name: STM32 I2C V2 timing
9 filter: dt_compat_enabled("st,stm32-i2c-v2")
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.xec | 14 bool "XEC Microchip GPIO driver V2"
18 Enable the Microchip XEC gpio V2 driver.
|
| /Zephyr-latest/dts/bindings/bluetooth/ |
| D | st,hci-spi-v2.yaml | 4 description: STMicroelectronics SPI protocol V2 compatible with BlueNRG-1 and successor devices
6 compatible: "st,hci-spi-v2"
|
| /Zephyr-latest/doc/services/virtualization/ |
| D | ivshmem.rst | 41 ivshmem-v2
44 Zephyr also supports ivshmem-v2:
46 https://github.com/siemens/jailhouse/blob/master/Documentation/ivshmem-v2-specification.md
49 (e.g. :zephyr:code-sample:`eth-ivshmem`). It is also possible to use ivshmem-v2 without
|
| /Zephyr-latest/dts/bindings/arm/ |
| D | nordic,nrf-uicr-v2.yaml | 4 description: Nordic UICR v2 (User Information Configuration Registers)
6 compatible: "nordic,nrf-uicr-v2"
|
| /Zephyr-latest/soc/snps/qemu_arc/ |
| D | Kconfig.defconfig | 21 # Technically ARC HS supports MPUv3, but not v2. But given MPUv3
22 # is the same as v2 but with minimal region size of 32 bytes, we
|
12345678910>>...23
