Home
last modified time | relevance | path

Searched +full:eirq +full:- +full:line (Results 1 – 4 of 4) sorted by relevance

/Zephyr-Core-3.7.0/dts/bindings/gpio/
Dnxp,s32-gpio.yaml1 # Copyright 2022-2023 NXP
2 # SPDX-License-Identifier: Apache-2.0
8 to either the SIUL2 EIRQ interrupt controller or, when available on the SoC,
10 SIUL2 EIRQ interrupt controller.
17 #include <zephyr/dt-bindings/gpio/nxp-s32-gpio.h>
25 priorities according to application-specific requirements. This is owing to
29 designated for the data-ready interrupt originating from a sensor. This
35 despite being named WKPU, the flag is not meant to configure GPIOs as wake-up
38 compatible: "nxp,s32-gpio"
40 include: [gpio-controller.yaml, base.yaml]
[all …]
/Zephyr-Core-3.7.0/dts/bindings/interrupt-controller/
Dnxp,s32-siul2-eirq.yaml1 # Copyright 2022-2024 NXP
3 # SPDX-License-Identifier: Apache-2.0
7 compatible: "nxp,s32-siul2-eirq"
9 include: [interrupt-controller.yaml, pinctrl-device.yaml, base.yaml]
15 pinctrl-0:
18 pinctrl-names:
21 filter-prescaler:
33 child-binding:
37 controller, labeled `irq_<interrupt-number>`. For example:
40 max-filter-counter = <5>;
[all …]
/Zephyr-Core-3.7.0/boards/nxp/mr_canhubk3/doc/
Dindex.rst3 NXP MR-CANHUBK3
9 `NXP MR-CANHUBK3`_ is an evaluation board for mobile robotics applications such
11 features an `NXP S32K344`_ general-purpose automotive microcontroller based on
12 an Arm Cortex-M7 core (Lock-Step).
16 :alt: NXP MR-CANHUBK3 (TOP)
21 - NXP S32K344
22 - Arm Cortex-M7 (Lock-Step), 160 MHz (Max.)
23 - 4 MB of program flash, with ECC
24 - 320 KB RAM, with ECC
25 - Ethernet 100 Mbps, CAN FD, FlexIO, QSPI
[all …]
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-3.3.rst14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
129 This may cause out-of-tree scripts or commands to fail if they have relied
[all …]